[mythtv-users] everyday i have to make sure myth worked the day before
Michael T. Dean
mtdean at thirdcontact.com
Sun Apr 3 12:58:13 UTC 2011
On 04/01/2011 11:43 PM, Christopher X. Candreva wrote:
> On Fri, 1 Apr 2011, Brian J. Murrell wrote:
>> In one example the backend log reports:
>> 2011-03-30 20:00:20.502 MythCoreContext: Connecting to backend server:
>> 2:6543 (try 1 of 5)
>> 2011-03-30 20:00:20.553 MythCoreContext: Connecting to backend server:
>> 10.75.22.2:6543 (try 1 of 5)
>> 2011-03-30 20:00:27.503 MythSocket(9c167a8:11): readStringList: Error,
>> timed out after 7000 ms.
>> 2011-03-30 20:00:27.504 Protocol version check failure.
>> The response to MYTH_PROTO_VERSION was empty.
>> This happens when the backend is too busy to
>> or has deadlocked in due to bugs or hardware
>> and so on and so on until the backend is restarted. Meanwhile frontends
>> cannot connect and in this particular instance, recordings failed to start.
> . . . and my system just did the same thing. At the end of watching a
> program, the frontend suddenly reported it couldn't connect to the back end.
> Mythweb was now timing out, and running mythfrontend from a command line
> gave similar errors.
> What can we do to help debug ?
First, make sure you all are using current 0.24-fixes. There have been
some fixes for networking/socket issues.
Also note that it seems that the above problem only happens with
specific configurations (either differences in hardware (such as chipset
and/or network devices) or kernel, library, ... version). I've never
seen the problem on any of my systems, with any of my distro versions,
so without a sufficiently specific bug report, I can't debug it, let
alone fix it.
More information about the mythtv-users