[mythtv-commits] Ticket #9792: Deadlocked scheduler

MythTV noreply at mythtv.org
Wed Jun 29 08:05:11 UTC 2011


#9792: Deadlocked scheduler
-----------------------------------+----------------------------
 Reporter:  warped <warpme@…>      |          Owner:
     Type:  Bug Report - General   |         Status:  new
 Priority:  minor                  |      Milestone:  unknown
Component:  MythTV - General       |        Version:  Trunk Head
 Severity:  medium                 |     Resolution:
 Keywords:                         |  Ticket locked:  0
-----------------------------------+----------------------------

Comment (by warpme@…):

 Hi,

 Since my last post into this ticket I do following:

 -build fresh mysql 5.1.57 (most recent from 5.1 mainline) & rebuild all
 dependent pkg (qt, perl/python, etc)

 -reinstall DB from full scratch (also with deleting DB dir). Also I
 disable query_cache as described in my previous post.

 -restore myth BD via mythconverg_restore.pl

 -turn off all other apps using mysql. Now there is only mythtv.

 It was 3 weeks ago. Since that time I had 2 times situation when:



 -myth is still recording via already defined recording rules.

 -no any new rule can be added (mythweb, UI; I can add it normally but rule
 simply is not appearing in recording rules).

 -after few hours of such state some events causes unblocking scheduler and
 all missed records are queued and triggered to record at once. This
 produces series of 0B recordings. I however still can't add new rules into
 recording rules list.

 -be restart helps.

 From usage point of view - scheduler is programmed by me & wife.
 I entered sometimes ago many custom advanced rules.
 My wife is using myth exactly like VCR - she is going into EPG and
 manually program their shows usually with "record once". She is doing this
 really quickly and usually 5-10 shows during programming session.

 History of last deadlock: wife ended programing 3 shows approx at 11PM.
 Next myth finished recording at 11:05PM. Next be log for 6h entries are
 only about eutoexpiring. BE misses 6 recordings in this period. At 6:50AM
 there is DB related entry log. Exactly after this BE kicks all queued
 delayed recordings to record. All them are 0B.

 I'm attaching BE debug log and trace from BE when it was in "no accepting
 new rules" state.
 There is NO any entry in any system log saying anything about mysql error,
 restart, whatever.

 Hope log/trace helps.
 (I don't want to mention about v.hard time with WAF. This is bad luck.
 Lastly I spent considerable time bisecting FE issues but in reality wife
 sees her missed recordings. Oh...)

 br

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


More information about the mythtv-commits mailing list