Messages

I would like to recompile and use MythTV_PlugIn. Is it possible to recompile this module alone without recompiling all of LinuxMCE code.

I tried to recompile MythTV_PlugIn. It complained on PlutoUtils. When I tried to recompile PlutoUtils, I got more errors.

Thanks for your help

I have a few M2TS files that mediatomb does not recognize. It associats M2TS files with application/octect-stream mime type. Consequently my upnp clients don't play these files. I updatd /etc/mediatomb/config.xml to map M2TS file extentions as video/mepg mime type. Restarted mediatom server. Restarte cored. Config.xml changes didn't take effect. According to mediatomb documenation, those files need to be reimported. I would rather reimport all of my media files. If it was sqlite.db, one way to reimport is to to delete the db and mediatomb will recreate it. However, we use mysql. Do we have to delete rows in pluto_mediatomb db ? If the whole thing I did was wrong, what is the right way to solve this problem. Thanks in advance.

I used 05-Jan-2011 dvd install for the CORE. I am trying setup an MD that worked fine under 710. Under 810 it fails with the following symptoms. 1) mysql dies prematurely with the following error message: [ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.host' doesn't exist ... mysql_safe[...] ended 2) It tries to download/install nvida packages and says it needs to reboot. Never goes beyond this point. Your help is appreciated.

For some unknown reason, MythTV changes MPEG decoder to 'Standard' (ffmpeg). This starts using the CPU instead of the GPU for rendering. That leads to slow response to remote control and high speed for CPU fan during live/playback of HD content. When I reset it to 'XVMC' things are bettter. So, I want to set MPEG decoder to XVMC whenever mythtv exits.

I found a work around using 'Application Exited' event on myth. But, still would like to know why 'deveice turned on or of' didn't work.

I need to run a script every time I exit from mythtv. So, I added a response to event. I set event = 'A device is turned on or off', 'What device' = 'MythTV Player' and 'on or off?' to 0. This is not working.

I tested the commands using 'Test Command' button and that is working. I tried the MD also for 'What device'.

Any idea what is going wrong?

Note: This is in 710

When I run background jobs (like backup), I would like to add an entry to the list of 'pending tasks'. This will allow me to track the progress better. Have any of you done that? Can you please tell me how to add new tasks, update task progress and finally remove it.

Looks like the issue was some update in ubuntu kernel packages. Check out http://www.linuxmce.org/index.php/news/developer/145-catch-up-with-ubuntu for further info.

Today (2/11/10) I tried to install 810 using internet version (no dvd). I am currently running 710 on this one. Tried to install a 810 on a new hard disk.

Kubuntu 810 was successful. Fixed the eth0 to the external network. Used the scripts at http://wiki.linuxmce.org/index.php/Installing_0810 to install 810.

After the reboot, I only saw the X cursor. Logged on to one of the consoles and looked for the error message and noticed the following symptoms.
- ifconfig showed only 'lo'
- LaunchManager log shows 'pluto_main' database is not available. I verified and it is not there.

I tried twice and it was the same error both times.

I had to revert back to 710. Earlier in December I was able to successfully test the internet install on a spare machine. Looks like something is broke now. Is there a different way to install 810 now.

[10 01/17/09 20:02:21.520 Received Message type 1 ID 84 from 20 to 36 (device: 36) resp 1 <0xb6078b90>10 01/17/09 20:02:21.520 Message 84 NOT pre-processed. <0xb6078b90>10 01/17/09 20:02:21.520 Routing Message 84 to 36... <0xb6078b90>10 01/17/09 20:02:21.520 Dispatching Message 84 to 36... <0xb6078b90>10 01/17/09 20:02:21.520 Command will be handled in Parent device. <0xb6078b90>10 01/17/09 20:02:21.520 Routing message ID=84 to device 36. <0xb6078b90>05 01/17/09 20:02:21.520 Process Queue = 1 <0xb6078b90>10 01/17/09 20:02:21.644 Routing message to Ruby Interpreter... <0xb5877b90>10 01/17/09 20:02:21.644 handleMessage directly <0xb5877b90>10 01/17/09 20:02:21.644 Command 84 not supported. <0xb5877b90>01 01/17/09 20:02:21.644 For obscure reasons could not handle the message <0xb5877b90>]

Here is the output from 36_Generic_Serial_Device.log

10   01/17/09 19:58:47.655      handleMessage directly <0xb5877b90>
10   01/17/09 19:58:47.655      Command 350 not supported. <0xb5877b90>
10   01/17/09 19:58:47.655      Receiving buffer from 192.168.80.254 with max size 4096 and timeout 100... <0xb5877b90>
10   01/17/09 19:58:47.663      Receiving buffer from 192.168.80.254 with max size 4096 and timeout 100... <0xb5877b90>
10   01/17/09 19:58:47.663      Receiving buffer from 192.168.80.254 with max size 4096 and timeout 100... <0xb5877b90>
10   01/17/09 19:58:47.663      Closing connection to 192.168.80.254 <0xb5877b90>
10   01/17/09 19:58:47.686      Connected to 192.168.80.254 on port 80, socket 10 <0xb5877b90>
10   01/17/09 20:00:37.666      handleMessage directly <0xb5877b90>
10   01/17/09 20:00:37.666      Command 350 not supported. <0xb5877b90>
10   01/17/09 20:00:37.666      Receiving buffer from 192.168.80.254 with max size 4096 and timeout 100... <0xb5877b90>
10   01/17/09 20:00:37.674      Receiving buffer from 192.168.80.254 with max size 4096 and timeout 100... <0xb5877b90>
10   01/17/09 20:00:37.674      Receiving buffer from 192.168.80.254 with max size 4096 and timeout 100... <0xb5877b90>
10   01/17/09 20:00:37.674      Closing connection to 192.168.80.254 <0xb5877b90>
10   01/17/09 20:00:37.696      Connected to 192.168.80.254 on port 80, socket 10 <0xb5877b90>
10   01/17/09 20:02:21.520      Receive string: MESSAGE 103            <0xb6078b90>
10   01/17/09 20:02:21.520      Received MESSAGE 103            0x80abae0 device: 36 <0xb6078b90>
10   01/17/09 20:02:21.520      Received Message type 1 ID 84 from 20 to 36 (device: 36) resp 1 <0xb6078b90>
10   01/17/09 20:02:21.520      Message 84 NOT pre-processed. <0xb6078b90>
10   01/17/09 20:02:21.520      Routing Message 84 to 36... <0xb6078b90>
10   01/17/09 20:02:21.520      Dispatching Message 84 to 36... <0xb6078b90>
10   01/17/09 20:02:21.520      Command will be handled in Parent device. <0xb6078b90>
10   01/17/09 20:02:21.520      Routing message ID=84 to device 36. <0xb6078b90>
05   01/17/09 20:02:21.520      Process Queue = 1 <0xb6078b90>
10   01/17/09 20:02:21.644      Routing message to Ruby Interpreter... <0xb5877b90>
10   01/17/09 20:02:21.644      handleMessage directly <0xb5877b90>
10   01/17/09 20:02:21.644      Command 84 not supported. <0xb5877b90>
01   01/17/09 20:02:21.644      For obscure reasons could not handle the message <0xb5877b90>
10   01/17/09 20:02:27.664      handleMessage directly <0xb5877b90>
10   01/17/09 20:02:27.664      Command 350 not supported. <0xb5877b90>
10   01/17/09 20:02:27.664      Receiving buffer from 192.168.80.254 with max size 4096 and timeout 100... <0xb5877b90>
10   01/17/09 20:02:27.671      Receiving buffer from 192.168.80.254 with max size 4096 and timeout 100... <0xb5877b90>
10   01/17/09 20:02:27.671      Receiving buffer from 192.168.80.254 with max size 4096 and timeout 100... <0xb5877b90>
10   01/17/09 20:02:27.672      Closing connection to 192.168.80.254 <0xb5877b90>
10   01/17/09 20:02:27.695      Connected to 192.168.80.254 on port 80, socket 10 <0xb5877b90>
05   01/17/09 20:02:41.517      Socket::ReceiveData 0x80abae0 failed, bytes left 0 start: 3260000 1: 0 1b: 0 2: 0 2b: 0 m_Socket: 8 Command_Impl1 Dev #36 <0xb6078b90>
05   01/17/09 20:02:41.517      Socket::ReceiveString2 ReceiveData failed m_Socket: -1 Command_Impl1 Dev #36 <0xb6078b90>
01   01/17/09 20:02:41.517      Receive string failed in HandleRequestSocket 18:ReceiveData failed Command_Impl1 Dev #36 <0xb6078b90>
05   01/17/09 20:02:41.518      Dumping 1 locks <0xb6078b90>
05   01/17/09 20:02:41.518      finished check for exceptions <0xb6078b90>
05   01/17/09 20:02:41.518      OL: (0x80abc2c) (>77) MessageQueue Command_Impl.cpp l:822 time: 7:00:00p (1232240561 s) thread: 3062340496 Rel: Y Got: Y <0xb6078b90>
10   01/17/09 20:02:41.518      Requesthandler 0x80abae0 (device: 36) Closing request handler connection <0xb6078b90>
10   01/17/09 20:02:41.518      Command_Impl::OnReload 36 <0xb6078b90>
10   01/17/09 20:02:41.518      Socket m_Socket -1/0x80abae0 Command_Impl1 Dev #36 m_bQuit=1 <0xb6078b90>
10   01/17/09 20:02:41.518      ready to dump locks using logger: 0x80aa5a0
<0xb707ab90>
10   01/17/09 20:02:41.642      Closing connection to 192.168.80.254 <0xb5877b90>
10   01/17/09 20:02:41.643      Closing connection to 192.168.80.254 <0xb5877b90>
10   01/17/09 20:02:41.643      Command 356 not supported. <0xb5877b90>
10   01/17/09 20:02:41.643      Generic Serial Device RunThread ended. <0xb6078b90>
10   01/17/09 20:02:41.643      DoLogging before join. <0xb787c6c0>
10   01/17/09 20:02:41.643      DoLogging end. <0xb707ab90>
10   01/17/09 20:02:41.643      DoLogging after join. <0xb787c6c0>
10   01/17/09 20:02:41.672      Waiting for message queue thread to quit <0xb787c6c0>
10   01/17/09 20:02:41.672      Socket m_Socket -1/0x80abae0 Command_Impl1 Dev #36 m_bQuit=1 <0xb787c6c0>
10   01/17/09 20:02:41.672      Socket m_Socket -1/0x80abae0 Command_Impl1 Dev #36 m_bQuit=1 <0xb787c6c0>
10   01/17/09 20:02:41.675      Message queue thread quit <0xb787c6c0>
10   01/17/09 20:02:41.675      Message queue thread joined <0xb787c6c0>
10   01/17/09 20:02:41.675      About to call kill spawned devices <0xb787c6c0>
10   01/17/09 20:02:41.675      Need to kill 0 child devices <0xb787c6c0>
10   01/17/09 20:02:41.675      Killing completed. <0xb787c6c0>
10   01/17/09 20:02:41.676      ~Command_Impl finished <0xb787c6c0>
10   01/17/09 20:02:41.676      Device: 36 ending <0xb787c6c0>
10   01/17/09 20:02:41.676      Ruby ended. <0xb787c6c0>
Return code: 2
2   01/17/09 20:02:41   36 (spawning-device)   Device requests restart... count=1/50 dev=36
Sat Jan 17 20:02:41 EST 2009 Restart
========== NEW LOG SECTION ==========
1   01/17/09 20:02:49   36 (spawning-device)   Starting... 1
1   01/17/09 20:02:49   36 (spawning-device)   Found /usr/pluto/bin/Generic_Serial_Device
10   01/17/09 20:02:49.759      Device: 36 starting.  Connecting to: localhost <0xb77da6c0>
10   01/17/09 20:02:49.761      Setting timeout for socket 4 to 20 <0xb77da6c0>
10   01/17/09 20:02:49.807      DoLogging start. <0xb6fd8b90>
10   01/17/09 20:02:49.807      DoLogging thread is started. <0xb77da6c0>
10   01/17/09 20:02:49.807      Connect OK <0xb77da6c0>
10   01/17/09 20:02:49.807      Device 36 has commad line <Generic_Serial_Device>. <0xb5fd6b90>
10   01/17/09 20:02:49.807      Adding device: 36. <0xb5fd6b90>
10   01/17/09 20:02:49.808      Socket::SendMessage type 5 id 37 from 36 to -1000 <0xb5fd6b90>
10   01/17/09 20:02:49.849      RubyIOManager::InstantiateNode port: ERR Parameter not found <0xb5fd6b90>
10   01/17/09 20:02:49.849      Checking TCP Port 80 <0xb5fd6b90>
10   01/17/09 20:02:49.849      Fetching Ruby code from Infrared Plugin <0xb5fd6b90>
10   01/17/09 20:02:49.849      InternalSendCommand id 188 out parm conf -1 resp 0x80b2fd8 <0xb5fd6b90>
10   01/17/09 20:02:49.849      Socket::SendMessage type 1 id 188 from 36 to -2000 <0xb5fd6b90>
10   01/17/09 20:02:49.854      InternalSendCommand out done id 188 conf -1 resp 0x80b2fd8 0x80b3268 0 type 1 id 188 to -2000 <0xb5fd6b90>
10   01/17/09 20:02:49.854      InternalSendCommand out id 188 parm exiting conf -1 resp 0x80b2fd8 <0xb5fd6b90>
10   01/17/09 20:02:49.854      Fetched 0 commands... <0xb5fd6b90>
10   01/17/09 20:02:49.854      Using network device with address <192.168.80.254>, at port: <80>. <0xb5fd6b90>
10   01/17/09 20:02:49.854      Using Idle Delay: 2000. <0xb5fd6b90>
10   01/17/09 20:02:49.854      Requesthandler 0x80abae0 (device: 36) runThread now running <0xb5fd6b90>
10   01/17/09 20:02:49.854      Loading generated code... <0xb57d5b90>
10   01/17/09 20:02:49.854      Starting Ruby... <0xb57d5b90>
RCODE:
   0:require 'Ruby_Generic_Serial_Device'
   1:class Command < Ruby_Generic_Serial_Device::RubyCommandWrapper
   2:end
   3:class Device_36 < Ruby_Generic_Serial_Device::RubySerialIOWrapper
   4:#### START SETTERS ####################################################################
   5:def initialize()
   6:super
   7:@returnParamArray=Array.new
   8:end
   9:####  END  SETTERS ####################################################################
  10:end
12:10   01/17/09 20:02:49.860      Generated code loaded. <0xb57d5b90>
10   01/17/09 20:02:49.860      Class: Device_36 instantiated. <0xb57d5b90>
10   01/17/09 20:02:49.860      Added 7 data params to device 36. <0xb57d5b90>
10   01/17/09 20:02:49.860      Added 0 wrapped child devices to device 36. <0xb57d5b90>
10   01/17/09 20:02:49.862      Connected to 192.168.80.254 on port 80, socket 9 <0xb57d5b90>
10   01/17/09 20:02:49.867      Connected to 192.168.80.254 on port 80, socket 10 <0xb57d5b90>
10   01/17/09 20:02:49.867      Command 355 not supported. <0xb57d5b90>

Last night, downloaded the ISO image, installed LMCE with a clean slate. It still failed for the same reason.

When I added the camera, it displayed it was downloading 'Generic Serial Device'. I am not sure, it is downloading latest and greatest version from linuxmce.org or somewhere. If so, it is definitely broken now.

No, I didn't do any sqlCVS update.

When it didn't work, all I did was get linuxmce source code using svn.

I am not sure what is the relationship with sqlCVS. How do I find out if any sqlCVS has been issued or what was changed ?

When I tried to find what is wrong, I issued 'ConfirmDependencies' a few times. But, that command didn't give me any useful result.

[Command 84 not supported.]

I enabled 'STATUS' logs and the following diagnostic information was logged

           Received Message type 1 ID 84 from 20 to 57 (device: 57) resp 1 <0xb606cb90>
           Message 84 NOT pre-processed. <0xb606cb90>
           Routing Message 84 to 57... <0xb606cb90>
           Dispatching Message 84 to 57... <0xb606cb90>
           Command will be handled in Parent device. <0xb606cb90>
           Routing message ID=84 to device 57. <0xb606cb90>
           ^[[33;1mProcess Queue = 1^[[0m <0xb606cb90>
           Routing message to Ruby Interpreter... <0xb586bb90>
           handleMessage directly <0xb586bb90>
           Command 84 not supported. <0xb586bb90>
           ^[[31;1mFor obscure reasons could not handle the message^[[0m <0xb586bb90>
           ^[[33;1mSocket::ReceiveData 0x80abac0 failed, bytes left 0 start: 180000 1: 0 1b

Command 84 is 'Get Video Frame'. Wiered.

I tried your suggestion, it didn't work.
I prayed but the gods refused to answer (:-(

Now, I am using 'Generic Motion IP Camera'. The light on the camera is blinking constantly. I guess its due to Motion grabbing snapshots.

I have a Panasonic IP Camera that was working fine. I recently reinstalled LMCE 710. After re-installation, LMCE recognized the camera.
    - It created a device under 'Surveillance Cameras'
    - It created a device (with the same id) under Generic Serial Devices
I reloaded router and regenerated screens. New camera appears under UI2 on the MD.

However, any time I try to view the camera,
    - All the buttons appear but there is no image on the MD
   - After a few seconds, DCE router is reloaded automagically

I viewed the error log and I found the following lines within xx_Generic_Serical_Device.log that corresponds to the camera.
     For obscure reasons could not handle the message <0xb5885b90>
     Receive string failed in HandleRequestSocket 18:ReceiveData failed Command_Impl1 Dev #47 <0xb6086b90>

I have tried it several times, and the results are the same. Sometimes, I got the following error message when the device status is '**RUN_GET_IR**'
    Connect() failed, Error Code 111

Any idea what is broken here ?

Thom, thanks for confirming lack of choice in the 'Device' list.

I achieved the same by wrapping the following command in a shell script and invoking 'App Server' device with 'Spawn Application' command

               /usr/pluto/bin/MessageSend dcerouter -targetType category -bl 5 1 5 1 809 251 0 9 "Driveway Motion detected" 182 15 70 "motion"

I realize that what I want to get done is similar to 'Anouncement' available from 'Active Sensors' page. But, instead of audio I need text display. Text display is a non-invasive. Perhaps, this is a good enhancement.