Recording does not stop, recorded file truncated, automatic shutdown not working

[Klaus Kreiner <klaus_kr1@…>]

Since one or two months it sometimes happens that recordings do not stop after the endtime is reached.

Mythtv runs on Ubuntu 12.04 and I made no changes in the mythtv configuration recently. The only changes were Ubuntu updates.

If I open "previously recorded" in the frontend the recording is shown in state "recording" even after the endtime is reached. It is not possible to manually stop the recording in the frondend. All subsequent recordings are not recorded. Their state remains "Will record" in "Upcoming recordings" in the frontend even if their endtime is also passed. Also the pre-shutdown-check command is not executed after endtime of the recording is reached and the backend should be idle.

In the XML-interface the same recording is not shown any more in GetEncoderList? after its endtime is reached. Also the subsequent recordings do not show in GetUpcomingList? after their endtime is reached.

When I try to restart the backend with "stop mythtv-backend" the mythbackend processes are not killed but it is possible to kill them with "sudo killall mythbackend". In normal cases the backend terminates with "stop mythtv-backend". After restarting the backend all recordings which were shown in the frontend as "recording" or "will record" and whose endtime has already expired are now in state "missed". Calling of pre-shutdown-check command also works again.

Sometimes there is a truncated file with exactly 376 bytes in the recordings folder but sometimes there is no file at all.

Logs of myhtbackend look almost the same for working recordings and hanging recordings. The only difference I could see is that with hanging recordings the last log entry is "Changing from RecordingOnly? to None". The "Updating status for ..." and "FinishedRecording?" which follow with working recordings do not show. Also it seems that only "HouseKeeping?" log entries follow after that whereas after working recordings there are also "Scheduler" entries.

[Klaus Kreiner <klaus_kr1@…>]

output of mythbackend --version

[gigem]

This sounds like one of the recorder/scheduler deadlocks that were fixed in version 0.26. My suggestion is to upgrade to the latest 0.26/fixes version as version 0.25 is no longer supported.