[mythtv-commits] Ticket #9704: backend deadlocks up with Protocol version check failure.
MythTV
noreply at mythtv.org
Fri Apr 1 17:04:07 UTC 2011
#9704: backend deadlocks up with Protocol version check failure.
-----------------------------------+--------------------------------------
Reporter: brian@… | Type: Bug Report - General
Status: new | Priority: critical
Milestone: unknown | Component: MythTV - General
Version: 0.24-fixes | Severity: high
Keywords: | Ticket locked: 0
-----------------------------------+--------------------------------------
I have been experiencing for many months now backend deadlocks that
sometimes means recordings don't happen but always mean frontends fail to
connect to the backend.
When this happens the following messages appear in the backend log:
2011-03-30 20:00:20.502 MythCoreContext: Connecting to backend server:
10.75.22.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
respond,
or has deadlocked in due to bugs or hardware
failure.
2011-03-30 20:00:27.554 MythSocket(9c16ba0:12): readStringList: Error,
timed out after 7000 ms.
and these repeat on and on and the situation can only be resolved by a
backend restart, which annoying in the least means interrupted recordings
if some where ongoing or as I mentioned recordings not even starting.
I realize this is not much to go on yet. The next time I see this (and I
could probably pretty safely hold my breath waiting, so it likely won't be
long) I will get a threaded backtrace of the backend and attach it to this
bug along with a log snippit.
--
Ticket URL: <http://code.mythtv.org/trac/ticket/9704>
MythTV <http://code.mythtv.org/trac>
MythTV Media Center
More information about the mythtv-commits
mailing list