[mythtv-users] Entering Watch Recordings causes slave backend to disconnect
james.orr7 at gmail.com
Tue Nov 24 17:45:56 UTC 2009
On Tue, Nov 24, 2009 at 9:33 AM, James Orr <james.orr7 at gmail.com> wrote:
> On Tue, Nov 24, 2009 at 12:36 AM, James Orr <james.orr7 at gmail.com> wrote:
>> My slave backend appears to be disconnecting as I enter the Watch
>> Recordings screen.
>> Here is the message I get on the master backend log ...
>> 2009-11-24 00:31:25.582 MainServer::ANN Monitor
>> 2009-11-24 00:31:25.596 adding: frontend1 as a client (events: 0)
>> 2009-11-24 00:31:25.633 MythSocket(8282430:39): readStringList: Error,
>> timed out after 30000 ms.
>> 2009-11-24 00:31:25.657 Slave backend: james-computer no longer connected
>> 2009-11-24 00:31:25.667 Reschedule requested for id 0.
>> 2009-11-24 00:31:25.668 PlaybackSock::SendReceiveStringList(): No
>> 2009-11-24 00:31:25.717 MainServer::HandleQueryRecordings()
>> Could not fill program info from backend
>> 2009-11-24 00:31:25.741 MainServer, Warning: Unknown socket closing
>> 2009-11-24 00:31:25.758 MythSocket(8230150:-1): writeStringList: Error,
>> socket went unconnected.
>> We wrote 0 of 96216 bytes with 1 errors
>> I am running 0.22 build 22824 (gentoo ebuild 0.22_p22824-r1.ebuild).
> Anybody have any ideas? It does record stuff, as long as I don't go into
> the Watch Recordings screen which causes the above timeout and disconnect.
Well, no idea what the problem was but rebooting the slave backend fixed
it. I will get much scorn from the wife because of this as I always tell
her the first thing to do when things aren't working right is reboot and I
didn't do it here ....
During the reboot process it did hang at the "Killing ALSA processes" stage,
so maybe it was something to do with that???
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the mythtv-users