Recording service lock ups

[snagglewest]

Over the years I've had a few instances were I would notice a stream running in the tray icon, maybe once every 6 months or so. Not a big deal. The culprit has always been a Kodi live TV stream that had been stopped on the client, but continued to run in NextPVR. To stop it I've just stopped the service and restarted and everything was back to normal.

However, in the last week or so I've had it happen twice. Now the strange part, the last 2 times this happened I've stopped the service with the menu shortcut and when I've tried to use the shortcut to restart it it appears to restart (tray icon comes back) but the service is really not running (web interface etc not working). The only way I've been able to get it back running normally is to completely reboot the PC. I think NRecord.log.3 may have some clues, but I'm way outside my knowledge zone... There's been no changes to any of my client hardware (not even updates) or network in over a year other than updating NextPVR at the beginning of March to 4.1.0 so I'm knda at a loss.

Here's the logs, hopefully someone can give me some ideas on what's going on.

[ATTACH=CONFIG]45349[/ATTACH]

Snag

[mvallevand]

Since you were using NextEnd today you might need to kill the NextEnd task before stopping the recording service. The log 3 does show the unresolved NextPVR bug with timeshifting if is too annoying you need to turn off timeshifting. if

Martin

[snagglewest]

Thanks Martin. I've turned off time shift, we'll see if it makes a difference. I'll keep better track next time and see if nextend is running when it happens. I don't think it was running the previous time it happened, but I'll keep an eye on it.

Snag

[snagglewest]

Had the same lock up issue happen again today. Came home to find the Npvr icon in the tray red and it showing a tuner using channel 1059. Not sure exactly how long it had been running, but there was 3 "live tv" files in the buffer, might have been even as far back as last night... I tried stopping the service with the menu shortcut and then restarting it using the shortcut. Both gave me the "ok" pop up, but the service was not running. Tried it twice with the same results. I checked before I killed it off the first time and NextEnd was not running so I think that's not part of the problem.

Hopefully these logs will help

[ATTACH=CONFIG]45443[/ATTACH]

Snag

[sub]

I tried stopping the service with the menu shortcut and then restarting it using the shortcut. Both gave me the "ok" pop up, but the service was not running. Tried it twice with the same results.

I can see the last couple of times you tried to started the Recording Service, it failed because there was already a recording service running, so attempts to use various network sockets failed (since they were already in use). Unfortunately the NRecord.log.3 (which was the recording service that was still kind of running) doesn't go back quite as far as the error happening, so it's hard to guess what might have originally caused it.

[snagglewest]

Ok, I'll keep an eye on it and try and catch it sooner next time.

[snagglewest]

Found another lockup this morning, not sure how long it was going on before I found it.

Here's the logs

[ATTACH=CONFIG]45453[/ATTACH]

[Graham]

Found another lockup this morning,

The EpgCheck.log has ...

Fri 05/04/2018 2:56:58.92 Begin EPG Update process
Fri 05/04/2018 2:56:58.92 Validating Environment
Fri 05/04/2018 2:56:58.93 Check to see if any recording in progress...
RECORDING
Fri 05/04/2018 3:02:01.12 Check to see if any recording in progress...
RECORDING
Fri 05/04/2018 3:07:03.13 Check to see if any recording in progress...
RECORDING
Fri 05/04/2018 3:12:05.14 Check to see if any recording in progress...

Does your EPG update process include a restart of the NextPVR Recording Service ? ... is this restart sometimes going Pete Tong ?

[snagglewest]

Its just my updateEPG.bat which looks to see every 5 minutes if the tuners are in use before doing the epg update. All the entries for last night are because the tuner was hung open which would be as expected in this situation.

Snag

[sub]

2018-05-03 21:58:09.274 [DEBUG][38] Renew lease failed (0x1C0038)
2018-05-03 21:58:09.274 [DEBUG][38] liveHandleRenewalTime contains 1 handles:
2018-05-03 21:58:09.274 [DEBUG][38] - 0x1C003B
2018-05-03 21:58:10.274 [DEBUG][38] Renew lease failed (0x1C0038)
2018-05-03 21:58:10.274 [DEBUG][38] liveHandleRenewalTime contains 1 handles:
2018-05-03 21:58:10.274 [DEBUG][38] - 0x1C003B
2018-05-03 21:58:11.274 [DEBUG][38] Renew lease failed (0x1C0038)
2018-05-03 21:58:11.274 [DEBUG][38] liveHandleRenewalTime contains 1 handles:
2018-05-03 21:58:11.274 [DEBUG][38] - 0x1C003B
2018-05-03 21:58:12.274 [DEBUG][38] Renew lease failed (0x1C0038)
2018-05-03 21:58:12.274 [DEBUG][38] liveHandleRenewalTime contains 1 handles:
2018-05-03 21:58:12.274 [DEBUG][38] - 0x1C003B
2018-05-03 21:58:13.274 [DEBUG][38] Renew lease failed (0x1C0038)
2018-05-03 21:58:13.274 [DEBUG][38] liveHandleRenewalTime contains 1 handles:
2018-05-03 21:58:13.274 [DEBUG][38] - 0x1C003B

I've attached a patch which should correct this issue that seems to repeat over and over in your logs. We've seen it a couple of times in the past, from some Kodi Live TV users, but have never been able to reproduce it myself.