scheduled recordings think they start, but they actually don't, then Mythweb still shows them in Upcoming Recordings

[Steven Adeff <adeffs.mythtv@…>]

ever since the HDPVR patches went in on my two systems, both with a Ceton but only one with an HDPVR, have had this problem.

basically, scheduled recordings THINK they start, they even show in the logs that they THINK they do, but the file is never created, the entry in the 'recorded' table are not created, and thus the recording is never made, but if one goes into MythWeb's Upcoming Recordings list, they are listed as "Currently Recording: Edit".

The end effect of this is that Myth has become absolutely unreliable in it's scheduled recordings since this is random.

This occurs on both Ceton and HDPVR recordings, so I don't know if it is directly related to the HDPVR patches, but that is when I began noticing.

[Steven Adeff <adeffs.mythtv@…>]

This is still occurring for me, I'd love to hear how I can help troubleshoot why it's happening to get it resolved.

[philconroy@…]

I have a similar problems when scheduled records just get "missed" with some (ie not all) future recordings disappearing from the schedule on the status page in MythWeb. A restart of the backend fixes the problem but it starts to happen again in the next day or two.

I keep current with the development version and the problem started about 2 months ago.

[hakon@…]

Happens with me as well, capture card is "Multimedia controller: Philips Semiconductors SAA7131/SAA7133/SAA7135 Video Broadcast Decoder (rev d1)", gentoo linux kernel 3.3.8-gentoo, package version 0.25.2_p20120825. I am unable to find any clue in my logs. Restarting the BE gets recordings going again. Will try to get myth going under valgrind, though my rig is a bit short of breath as it is.

[philconroy@…]

Not sure if this is right the place to say this but I think I have it sorted. I just learnt that you can have virtual encoders in 0.25 and the consensus was that to get it working properly you had to delete the capture cards and re-add them. I haven't touched my tuner cards for at least 3 years so I did that and went with the default of 2 encoders per card. Of course I had to re-scan all the channels but I haven't had a problem with my recordings since I made the change 5 days ago.

My guess is that when the virtual encoders feature was added some "phantom" tuners were created and mythtv attempted to use them for recordings. Restarting the backend would then reset things until it tried to use the phantom encoders again.

[gigem]

Thanks for reporting back.

FYI, you shouldn't need to rescan. Just reconnect the newly created inputs back to the proper videosource.

[adeffs.mythtv@…]

except that my system was created after "virtual encoders" was introduced.

[ttg.goldcoast@…]

I've been having a similar problem, Upcoming recordings shows the schedule OK but when I come back to watch there is no recording & it's not listed in the previously recorded section at all. If I go to schedule recordings > guide & scroll backwards the show is highlighted & says 'will record' when selected.

I have also been having an error pop up that mythtv backend setup closed unexpectedly even though it is closed & hasn't been opened for months - I've been selecting 'leave closed' & ignore future errors but it is reoccuring at least one a week

I wonder if they are related

[gigem]

Replying to ttg.goldcoast@…:

I've been having a similar problem, Upcoming recordings shows the schedule OK but when I come back to watch there is no recording & it's not listed in the previously recorded section at all. If I go to schedule recordings > guide & scroll backwards the show is highlighted & says 'will record' when selected.

I have also been having an error pop up that mythtv backend setup closed unexpectedly even though it is closed & hasn't been opened for months - I've been selecting 'leave closed' & ignore future errors but it is reoccuring at least one a week

I wonder if they are related

Please open a new ticket and provide backend logs, a backtrace and any other relevant information. Since the backend is still running, you'll need to start it under gdb and let it run or attach to it after the fact to get the backtrace.