recording service stopped

[sub]

I think it's worth using the current version.

[snagglewest]

Ok, so I updated to V5.0.1.200209 last night and stress tested it with 4 concurrent recordings and some live TV with out issue.  I saw the new version today and updated to 5.0.1.200211 too.  Currently I've got 4 concurrent recordings going along with Live TV thru Kodi and a 360p stream to the cell phone thru the web UI with no issues.  Not sure what was going on before, but for now I'm gonna keep my fingers crossed and call it. closed.

On another note, the new version seems to be less CPU hungry transcoding too!  With all 4 recordings, the Kodi stream and the web UI transcoding the CPU  is running in the 35-45% range.  I haven't checked it in the last few months, but before that would have shot it up in the 70%+ range.

Thanks for the great work Sub!

[snagglewest]

I spoke too soon...

Last night I had the same thing happen again.  This time there were also 4 recordings and when I awoke this morning the service was again unresponsive, Live TV was unavailable, but the web UI was functioning just as before.  The web UI actually showed 2 recordings going (both orange) "A million little things" and a manual recording "clash-pt2" which I started about 20:40 or so.  Both recordings ran until I restarted the service at 05:39 via the CLI.  One was 39gb and the other 32gb.  Bottom line they just continued to record from their respective start times until I reset.  Here's a screen shot from 05:39 just prior to the reset.
   

Now the rest of the story which "might" have some effect on it or maybe I just found a new bug.  I was recording the Daytona clash which had a rain delay so I tried to go into the web UI scheduler page and update the stop time.  I clicked the entry and the window opened with the options as would be expected.  I tired to add 120min to the recording but upon saving it kicked an error saying "Invalid Args".  Being a slow learner I did the same thing again... actually twice more.  Yea, I was stupid expecting a different result.  The "clash-pt2" recording was done so I would get the end of the clash which I was assuming would end at it's originally set time.

   

Here's the logs.  Let me know what if anything you want me to try on my end.

  logs-20200214-0538.zip (Size: 1.62 MB / Downloads: 5)

[snagglewest]

And again just now about 21:00.  2 recordings ended at 21:02 and live TV was playing on a Kodi box.  Same deal, the web UI showed a recording in progress, but Live TV was not available.  The first indication something was amiss was when the Live TV feed on the kodi box froze.  

   

A check of the status on the CLI didn't show anything amiss.

Code:

npvr@npvr:~$ service nextpvr-server status
● nextpvr-server.service - NextPVRServer
   Loaded: loaded (/usr/lib/systemd/system/nextpvr-server.service; enabled; vendor preset: enabled)
   Active: active (running) since Fri 2020-02-14 05:39:09 EST; 15h ago
  Process: 24140 ExecStart=/opt/nextpvr/shell/server.sh start (code=exited, status=0/SUCCESS)
Main PID: 24166 (dotnet)
    Tasks: 33 (limit: 4915)
   CGroup: /system.slice/nextpvr-server.service
           └─24166 /opt/dotnet/dotnet /opt/nextpvr/system/NextPVRServer.dll

Feb 14 05:39:07 npvr systemd[1]: Starting NextPVRServer...
Feb 14 05:39:09 npvr systemd[1]: Started NextPVRServer.
npvr@npvr:~$

A restart got everything back and ended the recording which was showing in progress.   It's starting to  appear it's happening when 2 recordings end at the same time but that's a guess on my part.  Here's the logs
[attachment=712]

[snagglewest]

Any thoughts Sub?

[sub]

I've just had a really close look through your two sets of logs above. The cause isn't clear to me, but I have a theory it's something to do with recordings being scheduled while other recordings are happening, causing the recording service to reload the recording schedule and some how forget about recordings that are currently happening. I've added some logging for the next build to get some more detailed info on what's happening.

[snagglewest]

Anything you want me to try in the mean time on this end?

[sub]

I've never really tried doing patches on Linux, but you could try this updated NShared.dll.

After installing, from a web browser that is already logged into the app, open this url in the browser:

http://localhost:8866/services/service?m...em.verbose

This will enable verbose logging until the recording service is restarted. It'll logs some extra stuff even minute around status of recordings while they're active. It also logs the expected end time when starting a recording. It should give us a better insight into what's happening on your machine at the time it happens.

[snagglewest]

I stopped the service, installed the patches, restarted he service and ran the URL above. I got 2 overlapping recordings this evening, 8p-10p and another 9p-10p both with 2min pre & post padding. we'll see how things go. Do I need to flush out the old logs or just let things run?

[sub]

Restarting the service was enough