recording in progress during epg update causes problems

[imilne]

Do you also get double recordings? I get a lot of recordings (recurring) with two identical entries in the "Ready Recordings" but one of them is marked as Failed. I checked that they are only scheduled once in "Pending".

I honestly haven't used it enough to say. I've been doing all my development in a tuner-less VM, with only the occasional use of a real machine to test it.

As much as I have every faith in sub, NPVR is lacking in too many features compared to GBPVR for it to make the transition to my HTPC yet. The future *is* bright though...

Iain

[johnsonx42]

Do you also get double recordings? I get a lot of recordings (recurring) with two identical entries in the "Ready Recordings" but one of them is marked as Failed. I checked that they are only scheduled once in "Pending".

I see that only for the recording that is in progress during the EPG update. The recording completes successfully on the old recording ID and gets marked "Ready" because the scheduler still "knows" about the old recording ID. During the EPG update the same recording will get re-scheduled again with a new recording ID, and whenever the recording schedule gets reloaded the second instance of the recording will get marked "Failed - Recording service not running...".

I actually had one case where I was up really late and happened to delete a recording just a few minutes after the EPG update completed, so the recording schedule got reloaded at about 3:05am; it was already recording the kids' 3:00am Zula Patrol on the old recording ID, and then started a second recording of it at 3:05am with the new recording ID. In that case I got two completed "Ready" recordings of the same show, one was just missing the first five minutes. In fact I think it was that scenario that led me on to this investigation.

If you're getting duplicate recordings other than for one in progress during the EPG update, it'd be interesting to see your NRecord logs.

[mark_lt]

As an interim solution on my part, I have set up my updateepg batch file to do a shutdown.exe /r with a time of about five minutes, which gives the DVB EPG time to update. I found that, even with avoiding the EPG update time, recordings that followed a few hours afterwards would give me errors, either through the automatic or manual epg update. (Error was also Recording Service not running)

When I get a bit of time I'll try and follow your process Johnsonx42, rather than just doing a running repair, to see if it is my fault (or if I have something new). I assume I could do something less dramatic and just stop and start the recording process, but will work on it when I have the time....

[johnsonx42]

sub, as you mentioned in one of my other threads that you've got another release coming in a couple of days, I'm wondering whether the issue in this thread will be fixed with that release as well?

If not, no worries. Now that I know the nature of the problem I've been handling it manually each morning, but if I know it's going to be another couple of weeks for a fix I'll put in a scheduled task to restart the recording service every morning at 4:30am or something like that.

[kendrak24]

I just got the problem with a recording being marked as "Failed - Recording service not running at recording time".
This recording was in progress during the epg update. Also noticed some errors in the log during the epg update.
Logs attached.

I'm using the latest beta (1.5.28)

Btw, it's mentioned that having two NextPVR.exe processes could be a possible cause for this, but I assume having two instances of NextPVR.exe would be normal when two MVP/NMT servers are configured?

[johnsonx42]

I don't think multiple NextPVR.exe's will actually cause this, as I explained in one of my later posts (nor will a recording in progress, that was also essentially a red herring except that it clued me in to the real problem). I haven't looked at your logs yet (honestly, call me a jerk if you like, but I rarely bother to look at logs in anything but .zip format unless I'm really interested), but I suspect your issue is completely different than what this thread was about. This issue has been resolved in 1.5.28.

p.s. apparently I'm the only one with an anti-7zip bias, so be it... we all have our quirks