[mythtv-commits] Ticket #9704: backend deadlocks up with Protocol version check failure.

MythTV noreply at mythtv.org
Wed Apr 20 03:45:25 UTC 2011


#9704: backend deadlocks up with Protocol version check failure.
-----------------------------------+----------------------------
 Reporter:  brian@…                |          Owner:
     Type:  Bug Report - General   |         Status:  new
 Priority:  critical               |      Milestone:  unknown
Component:  MythTV - General       |        Version:  0.24-fixes
 Severity:  high                   |     Resolution:
 Keywords:                         |  Ticket locked:  0
-----------------------------------+----------------------------

Comment (by brian@…):

 And again tonight, failure to record programs and the same old errors:

 {{{
 2011-04-19 22:04:30.036 Using runtime prefix = /usr
 2011-04-19 22:04:30.037 Using configuration directory =
 /home/mythtv/.mythtv
 2011-04-19 22:04:30.039 Using localhost value of pvr
 2011-04-19 22:04:30.048 New DB connection, total: 1
 2011-04-19 22:04:30.057 Connected to database 'mythconverg' at host:
 localhost
 2011-04-19 22:04:30.066 Closing DB connection named 'DBManager0'
 2011-04-19 22:04:30.068 Connected to database 'mythconverg' at host:
 localhost
 2011-04-19 22:04:30.070 Current locale EN_US
 2011-04-19 22:04:30.071 Reading locale defaults from
 /usr/share/mythtv//locales/en_us.xml
 2011-04-19 22:04:30.146 Loading en_us translation for module mythfrontend
 2011-04-19 22:04:30.209 MythCoreContext: Connecting to backend server:
 10.75.22.2:6543 (try 1 of 5)
 2011-04-19 22:04:30.261 MythCoreContext: Connecting to backend server:
 10.75.22.2:6543 (try 1 of 5)
 2011-04-19 22:04:37.214 MythSocket(892d960:11): readStringList: Error,
 timed out after 7000 ms.
 2011-04-19 22:04:37.215 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-04-19 22:04:37.263 MythSocket(892e1e8:12): readStringList: Error,
 timed out after 7000 ms.
 2011-04-19 22:04:37.263 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-04-19 22:04:37.264 MythCoreContext: Connecting to backend server:
 10.75.22.2:6543 (try 1 of 5)
 2011-04-19 22:04:44.266 MythSocket(892e350:11): readStringList: Error,
 timed out after 7000 ms.
 2011-04-19 22:04:44.266 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-04-19 22:04:44.267 Unable to find active recorder for this recording,
 realtime flagging will not be enabled.
 2011-04-19 22:04:44.292 MythCoreContext: Connecting to backend server:
 10.75.22.2:6543 (try 1 of 5)
 2011-04-19 22:04:51.295 MythSocket(88e29a0:11): readStringList: Error,
 timed out after 7000 ms.
 2011-04-19 22:04:51.295 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-04-19 22:04:51.301 MythCoreContext: Connecting to backend server:
 10.75.22.2:6543 (try 1 of 5)
 2011-04-19 22:04:51.601 AFD Warning: ScanATSCCaptionStreams() called with
 no PMT
 2011-04-19 22:04:51.602 AFD: Opened codec 0x8949e90, id(MPEG2VIDEO)
 type(Video)
 2011-04-19 22:04:51.605 AFD: codec MP2 has 2 channels
 2011-04-19 22:04:51.609 AFD: Opened codec 0x894b760, id(MP2) type(Audio)
 2011-04-19 22:04:58.304 MythSocket(88e2b48:11): readStringList: Error,
 timed out after 7000 ms.
 2011-04-19 22:04:58.305 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-04-19 22:07:28.838 [ac3 @ 0x22d6ac0]incomplete frame
 2011-04-19 22:07:33.211 ~MythContext waiting for threads to exit.
 2011-04-19 22:07:54.693 commflag: Commercial Detection Finished: "Dancing
 With the Stars" recorded from channel 3129 at 2011-04-19T21:00:00 (6
 commercial break(s))
 2011-04-19 22:07:56.725 UPnpMedia: BuildMediaMap VIDEO scan starting in
 :/video/mythvideo:
 2011-04-19 22:07:57.034 UPnpMedia: BuildMediaMap Done. Found 118 objects
 2011-04-19 22:08:44.361 DB Error (Resolution insert):
 Query was:
 INSERT INTO recordedmarkup    (chanid, starttime, mark, type, data)
 VALUES ( ?, ?, ?, ?, ?);
 Bindings were:
 :CHANID=1040, :DATA=720, :MARK=15541, :STARTTIME=2011-04-19T22:00:00,
 :TYPE=30
 Driver error was [2/1062]:
 QMYSQL3: Unable to execute statement
 Database error was:
 Duplicate entry '1040-2011-04-19 22:00:00-30-15541' for key 'PRIMARY'

 2011-04-19 22:08:44.363 DB Error (Resolution insert):
 Query was:
 INSERT INTO recordedmarkup    (chanid, starttime, mark, type, data)
 VALUES ( ?, ?, ?, ?, ?);
 Bindings were:
 :CHANID=1040, :DATA=480, :MARK=15541, :STARTTIME=2011-04-19T22:00:00,
 :TYPE=31
 Driver error was [2/1062]:
 QMYSQL3: Unable to execute statement
 Database error was:
 Duplicate entry '1040-2011-04-19 22:00:00-31-15541' for key 'PRIMARY'

 2011-04-19 22:10:55.879 [mpeg2video @ 0x5aafac0]warning: first frame is no
 keyframe
 2011-04-19 22:10:55.883 [mpeg2video @ 0x5aafac0]warning: first frame is no
 keyframe
 2011-04-19 22:10:55.909 [mpeg2video @ 0x5aafac0]warning: first frame is no
 keyframe
 2011-04-19 22:10:55.914 [mpeg2video @ 0x5aafac0]warning: first frame is no
 keyframe
 2011-04-19 22:10:56.020 [mpeg2video @ 0x5aafac0]warning: first frame is no
 keyframe
 2011-04-19 22:10:56.112 [mpeg2video @ 0x5aafac0]warning: first frame is no
 keyframe
 2011-04-19 22:10:56.188 [mpeg2video @ 0x5aafac0]warning: first frame is no
 keyframe
 2011-04-19 22:10:56.273 [mpeg2video @ 0x5aafac0]warning: first frame is no
 keyframe
 2011-04-19 22:10:56.277 [mpeg2video @ 0x5aafac0]warning: first frame is no
 keyframe
 2011-04-19 22:10:56.342 [mpeg2video @ 0x5aafac0]warning: first frame is no
 keyframe
 }}}

 Now that I've proved that this cannot be reproduced with -v most and very
 reliably reproduced without it, what is next in terms of trying to get to
 the bottom of this?

 *Every* *single* night there is some issue with mythtv whether it be the
 backend deadlocking like this and missing recordings or front-ends locking
 up because the backend is locked up.  Sadly, it's just not so much fun
 using mythtv any more. :-(

 It's frustration trying to watch it and having problems every single night
 and frustration having to keep explaining to the family why their
 recordings are just not being recorded with any reliability any more.  :-(

-- 
Ticket URL: <http://code.mythtv.org/trac/ticket/9704#comment:4>
MythTV <http://code.mythtv.org/trac>
MythTV Media Center


More information about the mythtv-commits mailing list