NextPVR Kodi Addon no longer works after upgrading to Kodi 17.6

[ChaosMageX]

After upgrading the Kodi app on my Amazon Fire TV (gen 2) to version 17.6, the NextPVR PVR Client add-on no longer works. Every time I start up Kodi, I get the following message:

Add-on couldn't be loaded. An unknown error has occurred.

I have attached the logs from both Kodi and NextPVR to this thread. I started up Kodi shortly after 1:20pm CST, so around 13:20 should be where the error is in the logs. Hopefully the logs can help figure you figure out what exactly is going wrong with Kodi.

However, just to be thorough, I remember reading in another thread a while ago about how you could run NRecord.exe in the command line with an argument that allowed it to output debugging information to the command line, but I can't remember what that argument is or what thread I read it in.

So, what are the possible command line arguments for NRecord.exe?

They aren't in the pinned read-me-first thread, but they probably should be. I want to know so that I can check the command line and see if any additional data about my problem could be found there.

EDIT: Oops, I forgot there was a dedicated sub-forum for problems with Kodi. Hopefully a mod can move this thread over there if necessary.

[sub]

13:20:05.442 T:18446744072293211424 DEBUG: CurlFile::Open(0xac4fc900) http://127.0.0.1:8866/service?method=ses...evice=xbmc
13:20:05.444 T:18446744072293211424 ERROR: CCurlFile::FillBuffer - Failed: Couldn't connect to server(7)

It's trying to connect to NextPVR on the same machine (127.0.0.1), but since this is an Amazon Fire TV, you definitely wont have NextPVR running on there. You need to go into the addon settings, to set the correct IP address.

[ChaosMageX]

It's trying to connect to NextPVR on the same machine (127.0.0.1), but since this is an Amazon Fire TV, you definitely wont have NextPVR running on there. You need to go into the addon settings, to set the correct IP address.

Yeah, I decided to go back to the settings and check to make sure it wasn't the obvious. What's weird is that I could have sworn I set the IP address to the server beforehand. Maybe the setting just didn't "stick" for some reason, since I also remember enabling time-shifting and that wasn't enabled when I checked.

I restarted Kodi to make sure that the settings "stuck" this time around. However, when I started Kodi, I once again got the message that the Add-on couldn't be loaded. I went to check the settings, and my server's IP address was correct, so that wasn't the problem this time.

I have attached the log files for this error, which occurs at about 2:47:51pm, so about 14:47:51 in the logs. I read through the Kodi log and this line seems particularly interesting:

14:47:51.909 T:18446744072293191808 ERROR: CCurlFile::FillBuffer - Failed: Failure when receiving data from the peer(56)

Here are the server-side logs: https://drive.google.com/open?id=1KgRGvn...4EjDPajGxD

I couldn't attach them to my post because the ZIP file is 2.33 MB, just barely above the 2.29 MB limit on ZIP files.

EDIT: It happened again, this time at 3:16:37pm, so I have attached the log files for that instance as well.

What's really weird is that I've restarted Kodi several times, and sometimes the NextPVR PVR Client Addon loads, and sometimes it doesn't.

However, even when it does load, the Recordings listing under the TV tab never seems to load. It will either be completely blank, or it will just show the recordings that are currently recording and nothing else.

[mvallevand]

The error you posted does seem like the problem but NextPVR is processing the request immediatetly when it gets it. Are the system times on your FTV and NextPVR accurate. If so there is significant blocking going on since it is minutes later.

With your 500+ recurring recordings you look to have lots of recordings that need to be loaded by Kodi on startup. Your logs show several Kodi devices coming up around the same time too so it is possible you are stressing the server. The FTV is not that fast a machine and it could be timing out. If you power off your other Kodi boxes does it work better? Restarting the server will cause lots of extra load too because of those other devices.


Martin

[ChaosMageX]

The error you posted does seem like the problem but NextPVR is processing the request immediatetly when it gets it. Are the system times on your FTV and NextPVR accurate. If so there is significant blocking going on since it is minutes later.

With your 500+ recurring recordings you look to have lots of recordings that need to be loaded by Kodi on startup. Your logs show several Kodi devices coming up around the same time too so it is possible you are stressing the server. The FTV is not that fast a machine and it could be timing out. If you power off your other Kodi boxes does it work better? Restarting the server will cause lots of extra load too because of those other devices.


Martin

Well, I just checked and my server clock is only about 3 seconds ahead of / faster than the FTV's clock.

But yeah, it could just be getting bogged down by the shear number of recordings I have stored on my server with its now 20 terabyte capacity. I think the last time I checked, I have at least 3000 individual recordings on there. Like I said in the other thread, I basically like to use it like it's my own personal Netflix server, storing entire seasons of shows on it and binge watching them at my leisure. And I don't just store shows for myself, but the rest of my family as well, as they each have their own assortment of shows they like to binge watch.

As for multiple clients, currently I have two Amazon Fire TVs and one Acer tablet connected to it at all times, in order to let the rest of my family watch their own shows as I watch mine.