[mythtv-users] MythSocket(ffffffffa9cd5d20:57): readStringList: Error, timed out after 7000 ms.

[Michael Rice]

On Fri, Dec 31, 2010 at 8:48 PM, Brian J. Murrell <brian at interlinx.bc.ca> wrote:
> Happy New Year to all.
>
> I want to ask, am I really the only person who is finding that the
> backend regularly deadlocks on 0.24-fixes?
>
> 2010-12-31 23:39:02.594 MythSocket(8bf7550:55): readStringList: Error, timed out after 7000 ms.
> 2010-12-31 23:39:02.594 Protocol version check failure.
>                        The response to MYTH_PROTO_VERSION was empty.
>                        This happens when the backend is too busy to respond,
>                        or has deadlocked in due to bugs or hardware failure.
> 2010-12-31 23:39:02.874 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
> 2010-12-31 23:39:09.876 MythSocket(8d51140:57): readStringList: Error, timed out after 7000 ms.
> 2010-12-31 23:39:09.876 Protocol version check failure.
>                        The response to MYTH_PROTO_VERSION was empty.
>                        This happens when the backend is too busy to respond,
>                        or has deadlocked in due to bugs or hardware failure.

Well I can verify you aren't the only one  :)  Just tonight:

2011-01-01 20:12:41.069 MythSocket(8422100:42): readStringList: Error,
timed out after 7000 ms.
2011-01-01 20:12:41.069 Protocol version check failure.
                        The response to MYTH_PROTO_VERSION was empty.
                        This happens when the backend is too busy to respond,
                        or has deadlocked in due to bugs or hardware failure.
2011-01-01 20:12:53.070 MythSocket(8886198:42): readStringList: Error,
timed out after 7000 ms.
2011-01-01 20:12:53.070 Protocol version check failure.
                        The response to MYTH_PROTO_VERSION was empty.
                        This happens when the backend is too busy to respond,
                        or has deadlocked in due to bugs or hardware failure.
2011-01-01 20:13:00.074 MythSocket(8886198:42): readStringList: Error,
timed out after 7000 ms.
2011-01-01 20:13:00.074 Protocol version check failure.
                        The response to MYTH_PROTO_VERSION was empty.
                        This happens when the backend is too busy to respond,
                        or has deadlocked in due to bugs or hardware failure.
2011-01-01 20:13:07.089 MythSocket(8aa5cb0:54): readStringList: Error,
timed out after 7000 ms.

This has happened a few times since I updated to .24 within the last
couple weeks.  For me it seems to happen after deleting a file or two
with the front end.  And the front end seems to be back to hanging for
several seconds after a delete.  That was something that was fixed in
.22 but seems to be reappearing now.  I will probably try to
investigate more when I get the chance.