Nextpvr getting hung up

[Jakesty]

I have a computer dedicated to Nextpvr and rarely touch it except for the occasional reboot. For some reason the application has ground to a halt and even after a reboot I launch the program but once I try to select anything from the menu I get a spinning mouse cursor. Windows 7 still working fine. I've looked in to the event logs, task manager, and nothing is helping. I have not installed or uninstalled anything for many months. Problem started sometime last week. There is plenty of storage available on the local system and remote computer I have for the recordings.

What can I do to likely fix this problem?

I can't get logs because as soon as I try to do anything it locks on me.

thanks for your help on this, Jake

[sub]

Post the logs and we'll see what it's doing at the time it locks.

In your other thread you mentioned a NAS. It could be a issue connecting to a network volume. Like long timeout, or login failure.

[ElihuRozen]

I can't get logs because as soon as I try to do anything it locks on me.

Can you get the logs by getting to settings from the tray application? Otherwise, stop the service with the item from NPVR sub-menu under the Start menu & then zip the logs manually.

[sub]

I can't get logs because as soon as I try to do anything it locks on me.

If you mean you cant get to the Settings screen to click the 'zip my logs' button, then just zip the c:\users\public\npvr\logs directory manually and post that zip file.

[Jakesty]

I had one recording for the last 5 or 6 which was successful. It wasn't the first or last recording.

I only have a couple of test files going to the NAS drive. When I click on that drive it is available from explorer.

I had turned off Ntray temporarily from MSCONFIG in an attempt to stop any kind of 3rd party apps from running. The window is still just as unresponsive. It sometimes works but maybe only 10% of the time then quickly gets stuck.

jake

[sub]

It sometimes works but maybe only 10% of the time then quickly gets stuck.

What exactly are you doing when it gets stuck? ie, is like going to the Recordings screen, or TV Guide, or maybe other places? As much as you think there isn't a pattern, there will be a pattern. Visiting either the Recordings and TV Guide screen will cause it to try loading the recording list, which will cause it to check the disk to see if files exist - it as at this point that it may have problems accessing your NAS. You could see if opening Windows Explorer, and browsing the recording path, then attempting to use NextPVR makes any difference (since Windows Explorer would have caused NAS authentication to have happened)

I see you're using the 'TV Listings' plugin, which may also load the Recording list at other times, which could trigger the issue earlier.

[Jakesty]

The locking up of the system happens almost immediately after opening NEXTPVR. I click on recordings, and I get a circular mouse cursor as if the system is busy. While it's busy though windows works fine.
Generally after about 3-5 mins the screen will come up, I can't hope to jump from "what's new" to anything else as it will just become "busy" again.

I'd be willing to kill the TVListings as I don't really seem to use it. Can that be done from SETTINGS in Ntray? I did not see a 'guide' there for the plugin for TVListings, I'm guessing there should be one?

I had no initial problems with setting up the NAS connection, and just haven't done anything more with it like migrating other programs. The problem started last week on 5/10/19 so my thought was to upgrade Nextpvr, and that didn't fix it.
I opened up the SETTINGS from ntray, found my recordings path and deleted the NAS. Rebooted, and it locked just as it has always. If I open the NEXTPVR desktop is when it locks, but if I kill it, ntray responds fine and I can export the logs easily. It doesn't seem to record with just NTRAY though.

It looks like I've only had 1 successful recording (househunters international), the rest show 0 byte files. I have not rebooted the PRIME tuner, but opening it with HDHR's interface the channels work good.
attached newest logs

thanks, Jake

[sub]

The locking up of the system happens almost immediately after opening NEXTPVR. I click on recordings, and I get a circular mouse cursor as if the system is busy. While it's busy though windows works fine.
Generally after about 3-5 mins the screen will come up, I can't hope to jump from "what's new" to anything else as it will just become "busy" again.

That is sounding exactly like what I described - when it needs to load the recording list, it's having some very long delay looking for the recordings.

2019-05-16 05:58:39.404 [DEBUG][1] LoadList@0
2019-05-16 05:58:39.404 [DEBUG][1] LoadList@1
2019-05-16 05:59:49.492 [DEBUG][1] LoadList@2
2019-05-16 05:59:49.493 [DEBUG][1] LoadList@3

The 70 second delay between "LoadList@1" and "LoadList@2" is loading the recording list.

So definitely sounding like you've got something not quite set right with your NAS stuff.

Did you try my suggestion of opening Windows Explorer to view the recording directory on your NAS (to ensure any Windows Authentication stuff has happened), then trying again in NextPVR to see if it's quicker?

[Jakesty]

I did open an explorer window, and it was good. Didn't need credentials or anything. I also removed the recording path to my NAS in SETTINGS, and the problem still happening. You had me thinking, as I have been recording to a another computer windows share, for a few years now, never this kind of problem.
So now I've removed all remote file storage, only local D: drive. Problem still persists.
New logs attached.

[sub]

You had me thinking, as I have been recording to a another computer windows share, for a few years now, never this kind of problem.
So now I've removed all remote file storage, only local D: drive. Problem still persists.
New logs attached.

Do you have any recordings in your database that would have originally been made on those network drives? If so, it's still going to look for them regardless of whether you've removed them as a recording directory.

If that info doesn't help, you'll probably need to supply your npvr.db3 file so I can take a look.

(it really is sounded exactly like what I described, and the logs look like it to, which is why I'm continuing to focus on that aspect)