NPVRTray Problem?

[mvallevand]

No the issue is for sub clearly NextPVR is seeing

2020-06-05 10:08:32.819 [DEBUG][1] HDHOMERUN_TAG_TUNER_COUNT: 3

but only identifying two of them.

Martin

[jcole998]

Thanks, Martin. It's not affecting functionality and all three tuners are used. I'll be patient.

[jcole998]

Just installed the latest build and noticed that NPVRTray still does not show all my devices.

Was this problem missed?

[sub]

There wasn't any further updates to NPVRTray since the last build I supplied you.

Can you supply a current set of logs when it's not listing all the tuners?

[jcole998]

Will do.

[jcole998]

Well...this has taken awhile but after a restart this morning, NPVRTray shows only three devices and is missing two of the three DCR-3250 tuners.

As suggested, I entered the following URL: http://localhost:8867/services/service?m...ormat=json and got the following results:

{"stat": "ok", "status": [{"oid": 23,"identifier": "HDHomeRun Device 20200EC0","streams": []},{"oid": 32,"identifier": "Hauppauge HD-PVR","streams": []},{"oid": 33,"identifier": "EXTRA Recorder (extra-nasa.xml)","streams": []}]}

Restarting the service again shows all tuners and that same URL now returns:

{"stat": "ok", "status": [{"oid": 21,"identifier": "HDHomeRun Device 20200EC0","streams": []},{"oid": 22,"identifier": "HDHomeRun Device 20200EC0","streams": []},{"oid": 23,"identifier": "HDHomeRun Device 20200EC0","streams": []},{"oid": 32,"identifier": "Hauppauge HD-PVR","streams": []},{"oid": 33,"identifier": "EXTRA Recorder (extra-nasa.xml)","streams": []}]}

Logs before and after the restart are attached. Hope you find something.

[mvallevand]

You had a problem in the start on the 15th

2020-07-15 11:01:35.594 [ERROR][4] Microsoft.Data.Sqlite.SqliteException (0x80004005): SQLite Error 5: 'database is locked'.

which blocked NextPVR from reading the tuners properly.

I'd start by making sure that it isn't one of your custom utilities causing this.

Martin

[jcole998]

Hmmmm...I'll look around. Every day at 11am, I access the DB with Powershell for scheduled recordings. Might be something there.

Thanks.

[jcole998]

Was looking through the logs showing the locked errors and noticed the following:

2020-07-15 11:00:47.630 [DEBUG][6] Doing database vacuum
[other entries including the two databased locked errors]
2020-07-15 11:02:06.572 [DEBUG][6] vacuuming done

Could this 89-second operation be interfering with the EPG Update where the locked errors occurred?

Also, I tried to create a Windows Event Viewer custom log and could not find the name of the V5 service "NextPVR Service." The V4 service is shown but not V5. Is it possible to log V5 service events?

[jcole998]

Bump