Opened 13 years ago

Closed 13 years ago

Last modified 13 years ago

#10233 closed Bug Report - General (Invalid)

mythbackend restarted 3-4 times a minute for two hours generating 600+ recordings

Reported by: jcube00@… Owned by:
Priority: minor Milestone: unknown
Component: MythTV - General Version: 0.24.1
Severity: low Keywords:
Cc: Ticket locked: no

Description

I switched to my recordings list to find at least 600 new recordings in just under two hours. The mythbackend log revels this was cause was some sort of restart loop where the backend would restart three to four times a minute causing recordings in progress at the time to restart too (hence the 600 recordings and 600 jobs)

I was unaware this was occurring and the issue appears to have resolved itself without any restart of the backend.

Any ideas on what triggered this and what broke the loop?

Attachments (4)

mythbackendloop1.log.gz (142.6 KB) - added by jcube00@… 13 years ago.
mythbackend log (1/4)
mythbackendloop2.log.gz (116.3 KB) - added by jcube00@… 13 years ago.
mythbackend log (2/4)
mythbackendloop3.log.gz (60.0 KB) - added by jcube00@… 13 years ago.
mythbackend log (3/4)
mythbackendloop4.log.gz (191.0 KB) - added by jcube00@… 13 years ago.
mythbackend log (4/4)

Download all attachments as: .zip

Change History (6)

Changed 13 years ago by jcube00@…

Attachment: mythbackendloop1.log.gz added

mythbackend log (1/4)

Changed 13 years ago by jcube00@…

Attachment: mythbackendloop2.log.gz added

mythbackend log (2/4)

Changed 13 years ago by jcube00@…

Attachment: mythbackendloop3.log.gz added

mythbackend log (3/4)

Changed 13 years ago by jcube00@…

Attachment: mythbackendloop4.log.gz added

mythbackend log (4/4)

comment:1 Changed 13 years ago by robertm

Resolution: Invalid
Status: newclosed

Please seek user support on the users mailing list.

comment:2 Changed 13 years ago by stuartm

Just to explain why Robert has closed this ticket. There is no indication in those logs as to why mythbackend exited so we cannot accept it as a useful bug report. The backend didn't exit normally and so it seems likely to have been aborted by an external process. mythbackend would abort itself in this way and it's incapable of restarting itself too, so this looks very much like a broken distro init script and not a MythTV bug.

Note: See TracTickets for help on using tickets.