Recording Service Not Running At Recording Time

[Bluethunder]

Running into an odd problem with 3.2.9.

I was having some problems with stuttery recordings, so I went back to an old HD image I had when everything was working, and installed 3.2.9.

Now I'm getting failed recordings, with Recording service not running once and a while.

Near the end (early morning), I have a series of recordings that failed. According to the "What's new", the Through the wormhole failed, but it is completely recorded in the directory. The next following recordings (I think it was food factory), did not record.

Another post mentioned to have the "out of process recording" box checked in the settings, and it was during this time.

I included some log files, that have a couple instances.

Any ideas?

[sub]

It looks like the system might have gone into standby mode while running your PostProcessing.bat was running (or sometime after running it), and resumed five hours later. Were the missed recordings within that next 5 hours? I looks like NextPVR has asked Window's to be awake for a couple of recordings during that time. I'm not sure why Windows wouldn't have woken at the requested times:

2014-06-04 12:32:58.146 [DEBUG][8] Requesting wake up for 'RecordingOID11183' at 6/5/2014 6:57 PM
2014-06-04 12:32:58.146 [DEBUG][8] Requesting wake up for 'RecordingOID11171' at 6/5/2014 9:57 PM

[mvallevand]

There might be problem when you were recording during the EPG update

Code:

2014-06-05 02:33:08.386    [DEBUG][9]       ...scheduling episode
2014-06-05 03:02:00.069    [DEBUG][8]    Stopping recording (11190 on 20). Past end time of recording. 9

After scheduling episode, for me there are usually quite a few more lines to finish loading the new epg ,creating backup recordings xml, rescheduling wakeups and running postupdateepg.bat.

Martin

[Bluethunder]

Been ok for the last few days, I bumped up my "sleep" time on the computer, to 20 minutes instead of 5.

Went to check it this morning, and SQL Database is locked. I had to reboot, and another bunch of failed recordings. Not sure if it's the original problem, or the one because the DB was locked.

[mvallevand]

The EPG update kind of failed again this morning but oddly thread 9 finally looks like errored out much later

2014-06-07 02:15:33.972 [DEBUG][9] - Potential episode at: 6/11/2014 6:00:00 AM
2014-06-07 02:15:33.972 [DEBUG][9] ...check IsValid()
2014-06-07 02:15:33.973 [DEBUG][9] ...scheduling episode
...
2014-06-07 15:12:04.151 [DEBUG][9] ...was unable to schedule recording...marking as conflict

Martin

[Bluethunder]

The EPG update kind of failed again this morning but oddly thread 9 finally looks like errored out much later

2014-06-07 02:15:33.972 [DEBUG][9] - Potential episode at: 6/11/2014 6:00:00 AM
2014-06-07 02:15:33.972 [DEBUG][9] ...check IsValid()
2014-06-07 02:15:33.973 [DEBUG][9] ...scheduling episode
...
2014-06-07 15:12:04.151 [DEBUG][9] ...was unable to schedule recording...marking as conflict

Martin

Thanks for the help so far.

I wonder if my database has an issue. Shouldn't take to long to export the recordings and recurrings, and rebuild it.

Curious that it's still going to sleep in the middle of the EPG processing, and other times when it shouldn't be (ie post processing).