[mythtv-commits] Ticket #8199: backend lockup on recording expiry

MythTV mythtv at cvs.mythtv.org
Wed Mar 17 17:29:05 UTC 2010

#8199: backend lockup on recording expiry
 Reporter:  michael_zanetti@…        |       Owner:  danielk       
     Type:  defect                   |      Status:  infoneeded_new
 Priority:  trivial                  |   Milestone:  unknown       
Component:  MythTV - Recording       |     Version:  0.22-fixes    
 Severity:  medium                   |     Mlocked:  0             

Comment(by anonymous):

 I check the backend log on nearly every lockup. So far I can tell you that
 there is nothing suspicious in there. But I ran the backend with the
 default loglevel. The backend just stops logging at some point. Sometimes
 the logs stop completely after the hangup. Sometimes there are still some
 messages logged.

 I have attached two example logs:

 mythbackend.log.1 shows the last lockup I had. It happened directly after
 exiting LiveTV.
 mythbackend.log.2 shows a somewhat older failure. It happened on an
 autoexpire event

 Please note that in mythbackend.log.2 there are still some frontend
 connect events from a frontend logged. Those entries happened _after_ the
 backend locked up. The entries are there because I started and killed the
 frontend a few times, which for obvious reasons hung too. The last entry
 while the backend was working was the autoexpire one.

 Those logs are created using the default log level. I just have
 reconfigured my backend to log "all" messages and I will post future
 lockups with hopefully more detailed informations.

Ticket URL: <http://svn.mythtv.org/trac/ticket/8199#comment:3>
MythTV <http://www.mythtv.org/>

More information about the mythtv-commits mailing list