Author Topic: Slimserver not working after upgrade to .42  (Read 1000 times)

archived

  • Hello, I'm new here
  • Posts: 0
    • View Profile
Slimserver not working after upgrade to .42
« on: January 04, 2007, 08:47:25 pm »
Hi,

I have just upgraded to .42. After the upgrade the Slimserver is not working anymore. In the Slim_server_Streamer.log file I found a lot of these messages:
-----
10      01/04/07 20:23:53.636           Device: 63 starting.  Connecting to: localhost
13      01/04/07 20:23:53.853           Exiting MessageQueueThread_DCECI thread...
01      01/04/07 20:23:53.853           ^[[31;1mConnect() Failed^[[0m
10      01/04/07 20:23:53.853           Waiting for message queue thread to quit
10      01/04/07 20:23:53.853           Message queue thread quit
05      01/04/07 20:23:53.854           ^[[33;1mvoid ClientSocket::Disconnect() on this socket: 0x80823e0 (m_Socket: 3)^[[0m
10      01/04/07 20:23:53.854           ~Command_Impl finished
13      01/04/07 20:23:53.855           RequestSocket::Disconnect 0x807eeb0 device: 63
10      01/04/07 20:23:53.855           Device: 63 ending
Return code: 0
2       01/04/07 20:23:53       /usr/pluto/bin/Spawn_Device.sh /usr/pluto/bin/Spawn_Device.sh 63 (spawning-device)      ^[[1;33mDevice requests restart... 1 63^[[1;00m
Thu Jan  4 20:23:53 CET 2007 Restart
------
For me it looks like something is not runnig as it supposed to.

Please help.

KR Henrik

archived

  • Hello, I'm new here
  • Posts: 0
    • View Profile
Looks like it's the Slimserver plug-in which is not running.
« Reply #1 on: January 04, 2007, 09:22:38 pm »
Looking further into it the problem seems to be because the Slimserver plug-in is not started.

When looking into the errorlog of the slimserver plug-in I see messages like these:

-----
01   01/04/07 20:45:55.007      Sender: 9 sent message type: 1 ID: 67 and expected a confirmation from 1401   01/04/07 20:46:35.292      EPG file /var/lib/vdr was badly parsed01   01/04/07 20:46:36.296      EPG file /var/lib/vdr was badly parsed01   01/04/07 20:46:55.013      Sender: 9 sent message type: 1 ID: 67 and expected a confirmation from 1401   01/04/07 20:47:55.005      Sender: 9 sent message type: 1 ID: 67 and expected a confirmation from 1401   01/04/07 20:48:55.011      Sender: 9 sent message type: 1 ID: 67 and expected a confirmation from 1401   01/04/07 20:49:37.306      EPG file /var/lib/vdr was badly parsed01   01/04/07 20:49:38.310      EPG file /var/lib/vdr was badly parsed01   01/04/07 20:49:55.007      Sender: 9 sent message type: 1 ID: 67 and expected a confirmation from 1401   01/04/07 20:50:55.006      Sender: 9 sent message type: 1 ID: 67 and expected a confirmation from 1401   01/04/07 20:51:55.006      Sender: 9 sent message type: 1 ID: 67 and expected a confirmation from 1401   01/04/07 20:52:39.324      EPG file /var/lib/vdr was badly parsed01   01/04/07 20:52:40.328      EPG file /var/lib/vdr was badly parsed01   01/04/07 20:52:55.005      Sender: 9 sent message type: 1 ID: 67 and expected a confirmation from 1401   01/04/07 20:53:55.012      Sender: 9 sent message type: 1 ID: 67 and expected a confirmation from 1401   01/04/07 20:54:55.003      Sender: 9 sent message type: 1 ID: 67 and expected a confirmation from 1401   01/04/07 20:55:41.338      EPG file /var/lib/vdr was badly parsed01   01/04/07 20:55:42.342      EPG file /var/lib/vdr was badly parsed01   01/04/07 20:55:55.007      Sender: 9 sent message type: 1 ID: 67 and expected a confirmation from 1401   01/04/07 20:56:55.006      Sender: 9 sent message type: 1 ID: 67 and expected a confirmation from 1401   01/04/07 20:57:55.006      Sender: 9 sent message type: 1 ID: 67 and expected a confirmation from 1401   01/04/07 20:58:43.352      EPG file /var/lib/vdr was badly parsed01   01/04/07 20:58:44.356      EPG file /var/lib/vdr was badly parsed
-----

Which means absolutely nothing to me......

Can someone help please?

-Henrik