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

Brian J. Murrell brian at interlinx.bc.ca
Sat Jan 1 04:48:55 UTC 2011


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.
2010-12-31 23:39:09.877 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)


2010-12-31 23:39:16.878 MythSocket(943a520:57): readStringList: Error, timed out after 7000 ms.
2010-12-31 23:39:16.878 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:16.891 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
2010-12-31 23:39:23.891 MythSocket(ffffffffa9cd5d20:57): readStringList: Error, timed out after 7000 ms.
2010-12-31 23:39:23.891 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:28.891 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
2010-12-31 23:39:35.894 MythSocket(ffffffffa9cd5d20:57): readStringList: Error, timed out after 7000 ms.
2010-12-31 23:39:35.894 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:35.894 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
2010-12-31 23:39:42.899 MythSocket(9431880:44): readStringList: Error, timed out after 7000 ms.
2010-12-31 23:39:42.899 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:47.905 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)

Only a backend restart fixes this problem.

I filed a bug (9274) about it more than a month ago (as has been
requested here repeatedly) and the only thing that has happened in it
was me being chastised for pasting (rather than attaching) stack traces
of the server when this happens and setting the priority/severity.

This is becoming a serious PITA here.  Is there really no idea as to why
this is happening?  Given that this locks up everything since it's on
the backend, I have to disagree with the reassessment of the priority
from blocker to minor and the severity from high to medium.  In what
world is the master backend locking up only a minor bug with medium
severity?

Cheers,
b.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
URL: <http://mythtv.org/pipermail/mythtv-users/attachments/20101231/81f1343b/attachment.pgp>


More information about the mythtv-users mailing list