[mythtv] ticket 9704: backend thread deadlocks, nearly every night now

Brian J. Murrell brian at interlinx.bc.ca
Wed Jun 1 11:27:46 UTC 2011


It was suggested a little bit ago that I bring this problem to the dev
list rather than the users list.

Essentially my problem is ticket 9704 -- my backend deadlocks during
recordings with the following type of messages:

2011-05-31 20:30:35.043 MythCoreContext: Connecting to backend server:
10.75.22.
2011-05-31 20:30:35.079 MythCoreContext: Connecting to backend server:
10.75.22.
2011-05-31 20:30:42.048 MythSocket(919d418:11): readStringList: Error,
timed out
2011-05-31 20:30:42.049 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-05-31 20:30:42.083 MythSocket(91ecfa0:12): readStringList: Error,
timed out
2011-05-31 20:30:42.084 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-05-31 20:30:42.085 MythCoreContext: Connecting to backend server:
10.75.22.
2011-05-31 20:30:49.088 MythSocket(91ece68:11): readStringList: Error,
timed out
2011-05-31 20:30:49.088 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-05-31 20:30:49.090 Unable to find active recorder for this
recording, realt
2011-05-31 20:30:49.148 MythCoreContext: Connecting to backend server:
10.75.22.
2011-05-31 20:30:56.153 MythSocket(919dfc0:11): readStringList: Error,
timed out
2011-05-31 20:30:56.154 Protocol version check failure.
                        The response to MYTH_PROTO_VERSION was empty.

and so on.  Typically when then happens, frontends are unable to connect
until I restart the backend.  In some cases, when this happens no more
recordings will happen but in other cases, they will.

This is happening almost nightly (when we do most of our recording) now
and even several times a night most recently.

Interestingly, it doesn't seem to happen during the few recordings that
happen during the day, but those are typically situations where there is
only one recording happening at a time.

mythbackend version: fixes/0.24 [v0.24-235-g80192ec]
Hardware: 1 HVR-950Q (which does the lionshare of the recording)
          1 PVR 500
          1 PVR [12]50 (I don't recall whether it's a 150 or a 250)

I am most willing to do whatever it takes to help resolve this as it's
quite seriously starting to impact WAF -- and my own AF.  I just tired
of missing shows because mythtv has gone off on a vacation.

Many thanks in advance.

b.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 262 bytes
Desc: OpenPGP digital signature
Url : http://www.mythtv.org/pipermail/mythtv-dev/attachments/20110601/e7a81428/attachment.bin 


More information about the mythtv-dev mailing list