[mythtv-users] mythcommflag crashed mythbackend

[Thomas Börkel]

HI!

mythbackend was alive and just started a recording.

Then I started mythcommflag manually like this on an older recording:

mythcommflag -f /video/recordings/13003_20101014220500.mpg

And the output was this:

2010-10-15 19:36:16.399 Using runtime prefix = /usr
2010-10-15 19:36:16.400 Using configuration directory = /home/mythtv/.mythtv
2010-10-15 19:36:16.423 Empty LocalHostName.
2010-10-15 19:36:16.523 New DB connection, total: 1
2010-10-15 19:36:16.550 Closing DB connection named 'DBManager0'
2010-10-15 19:36:16.554 mythcommflag version: 0.23.1.201000710-1
www.mythtv.org
2010-10-15 19:36:16.554 Enabled verbose msgs: important

MythTV Commercial Flagger, started at Fri Oct 15 19:36:16 2010
Flagging commercial breaks for:
ChanID  Start Time      Title                                      Breaks
------  --------------  -----------------------------------------  ------
2010-10-15 19:36:16.579 ProgramInfo(): Updated pathname '':'' ->
'13003_20101014220500.mpg'
13003  20101014220500 CSI: Den Tätern auf der Spur
2010-10-15 19:36:24.215 MythSocket(81948a8:11): readStringList: Error,
timed out after 7000 ms.
2010-10-15 19:36:24.216 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-10-15 19:36:25.515 RingBuf(13003_20101014220500.mpg): Waited 1.0
seconds for data to become available...
2010-10-15 19:36:26.555 RingBuf(13003_20101014220500.mpg): Waited 2.0
seconds for data to become available...
Finding Logo2010-10-15 19:36:31.224 MythSocket(8194d80:11):
readStringList: Error, timed out after 7000 ms.
2010-10-15 19:36:31.224 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.




After that, mythbackend did not respond anymore and I had to kill it.


Using 0.23.1 fixes svn 26437.

Any hints would be greatly appreciated.

Thanks!

Thomas