[mythtv-users] "Slave backend: xxxx no longer connected"

Bradley Bell bradleyb at u.washington.edu
Fri Jan 18 03:39:49 UTC 2008


I have a master backend (no encoders) and several slave backends (1 
PVR-150 on each).

Several times lately, the slave backends are all simultaneously and 
mysteriously "disconnected" from the master backend, with the message:
"Slave backend: xxxx no longer connected"
appearing in the log on the master backend. I see nothing in the logs on 
the slave backends that looks relevant.

The status page on port 6544 of the master shows:
Encoder 10 is remote on mythslave (currently not connected).

But the slave is online, and mythbackend is seemingly running fine.
The status page on port 6544 of the slave shows:
Encoder 10 is local on mythslave and is not recording.

The slave backends then remain in this disconnected state (and thus no 
recordings take place) until I restart the mythbackend process on the slave.

What is causing this, or how can I try to track the problem down?

Thanks,
Brad


Here is the beginning of the relevant portion of the master backend log 
(--verbose all)
Similar messages appear for each of the other slave backends immediately 
afterwards.

2008-01-17 18:08:25.542 MythSocket(2aaaaabd3da0:29): new socket
2008-01-17 18:08:25.552 MythSocket(2aaaaabd3da0:29): setSocket: 28
2008-01-17 18:08:25.553 MythSocket(2aaaaabd3da0:28): state change Idle 
-> Connected
2008-01-17 18:08:25.553 MythSocket(2aaaaabd3da0:28): UpRef: 1
2008-01-17 18:08:25.554 MythSocket(2aaaaabd3da0:28): socket is readable
2008-01-17 18:08:25.560 MythSocket(2aaaaabd3da0:28): cb->readyRead()
2008-01-17 18:08:25.560 MythSocket(2aaaaabd3da0:28): UpRef: 2
2008-01-17 18:08:25.561 read  <- 28 21      MYTH_PROTO_VERSION 31
2008-01-17 18:08:25.568 write -> 28 13      ACCEPT[]:[]31
2008-01-17 18:08:25.569 MythSocket(2aaaaabd3da0:28): DownRef: 1
2008-01-17 18:08:25.569 MythSocket(2aaaaabd3da0:28): socket is readable
2008-01-17 18:08:25.576 MythSocket(2aaaaabd3da0:28): cb->readyRead()
2008-01-17 18:08:25.577 MythSocket(2aaaaabd3da0:28): UpRef: 2
2008-01-17 18:08:25.577 read  <- 28 18      ANN Monitor mythmaster 0
2008-01-17 18:08:25.584 MainServer::HandleAnnounce Monitor
2008-01-17 18:08:25.585 adding: mythmaster as a client (events: 0)
2008-01-17 18:08:25.586 write -> 28 2       OK
2008-01-17 18:08:25.586 MythSocket(2aaaaabd3da0:28): DownRef: 1
2008-01-17 18:08:25.591 MythSocket(790a90:21): UpRef: 2
2008-01-17 18:08:25.597 write -> 21 36      QUERY_REMOTEENCODER 
10[]:[]GET_STATE
2008-01-17 18:08:25.598 MythSocket(790a90:21): readStringList: 
Connection died (select).
2008-01-17 18:08:25.598 MythSocket(790a90:21): socket is readable
2008-01-17 18:08:25.598 MythSocket(790a90:21): DownRef: 1
2008-01-17 18:08:25.601 MythSocket(790a90:21): socket closed
2008-01-17 18:08:25.605 MythSocket(790a90:21): UpRef: 2
2008-01-17 18:08:25.609 MythSocket(790a90:21): state change Connected -> 
Idle
2008-01-17 18:08:25.613 write -> 21 36      QUERY_REMOTEENCODER 
10[]:[]GET_STATE
2008-01-17 18:08:25.617 MythSocket(790a90:-1): cb->connectionClosed()
2008-01-17 18:08:25.621 MythSocket(790a90:-1): writeStringList: Error, 
socket went unconnected.
2008-01-17 18:08:25.626 Slave backend: mythslave no longer connected
2008-01-17 18:08:25.630 MythSocket(790a90:-1): readStringList: Error, 
called with unconnected socket.
2008-01-17 18:08:25.634 Reschedule requested for id 0.
2008-01-17 18:08:25.642 MythSocket(790a90:-1): DownRef: 1
2008-01-17 18:08:25.648 Encoder card 10 free space 5846048


More information about the mythtv-users mailing list