KODI NextPVR client calling GetRecordingsList too often

[nitram]

I am running the latest KODIbuntu on an Intel NUC and have NextPVR 3.3.8 running on a server PC.

I noticed peaks in CPU activity of 100% of a core every 12 seconds or so on the server PC. Switching on debugging in NextPVR on the server I found the CPU activity correlates with the KODI NextPVR client calling GetRecordingsList for all recordings (and there are several thousand of them) every 12 seconds or so. This happens even when KODI is at the top level of its menus, not showing any extPVR content.

Is there a way of moderating this CPU and network activity?

NB otherwise this setup is working really well. The only other problem I have found is that I had to turn off use of VAAPI acceleration in KODI as it caused occasional crashes and reboots of KODI. Luckily although this uses a lot more CPU on the NUC it still runs HD video at full frame rate.

[madas]

I noticed this happening in my web.log file as well. I have about 7 or 8 KODI clients and i think its causing some other issues. Is there a way to throttle this call?

I realise this thread is very old but I still see this.

[sub]

How often is it calling exactly? I've not seen any signs this is happening - infact, we've had a lot of complaints recently that it was only called once, and never again, and the users have been having to restart Kodi to get it to reload the recording lits.

You'll probably want to start it up with only a single Kodi client running, to keep the extra log noise to a minimum, leave it running for a few minutes, then post the logs so we can see.

[madas]

Hi Sub.

It seems ok with just a single client. Once I fire up a few then it seems to get stuck in a loop and they all update over and over. web.log seems to rotate more than once a minute. We do have a LOT of recordings in the system. I've attached some sample web.log and a kodi.log. There are some errors on the kodi side that seem to be in the log every 20-30 seconds.

18:15:35 82.478653 T:1766847552 NOTICE: Previous line repeats 4 times.
18:15:35 82.478951 T:1766847552 ERROR: CCurlFile::FillBuffer - Failed: Failure when receiving data from the peer(56)
18:15:35 82.479088 T:1766847552 NOTICE: CCurlFile::FillBuffer - Reconnect, (re)try 1
18:15:35 82.527832 T:1766847552 ERROR: CCurlFile::FillBuffer - Failed: Requested range was not delivered by the server(33)

Is it possible the database is getting locked and the requests are failing?

[madas]

I left it overnight and checked again this morning. Its still writing to web.log at an impressive rate. I tailed the file for the last 30 mins and it has never stopped. I see the same clients (all of them) coming back over and over.

[sub]

I've not seen any other reports of this behaviour.

Approximately how many recordings do you have?

I'm actually wondering if it's related to you using a NAS, a lot of recordings, and it being slower than a local drive it takes a while to build up the recording list, leading to the Kodi request timing out, and trying again?

I've attached an updated nshared.dll, which should get rid of a lot of the noise in those logs. Can you repeat the process and post the logs again? Hopefully it'll be a bit clearer what's happening in your logs.

[madas]

Sub,

There at least 300 recordings, maybe more. I think there are 7 KODI clients connecting right now. I wonder if there was something in one of the recording names that is causing it to blow up. I notice that since this is happening the listings take ages to download to the KODI clients as well (used to take 15-20 seconds, now takes 1-2 minutes).

Logs with the new NShared.dll attached.

M

[sub]

That logs show two Kodi clients getting the recording list.

Can you restart the recording service (to reset the logs), and show only a single Kodi client getting the information. This will make it easier to follow what's happening.

[mvallevand]

I am concerned about all those mp4 files, sub will those stream to Kodi using your recording ID interface? There does seem to be some spanish in there that might be marked up wrong.

Code:

<description>Discusión de todo tipo de asuntos que afectan a personas comunes.</description>

Also lastupdated doesn't seem to be getting called at all. These are old clients in Kodi when I see 15.2 and 16.1 I think it should be 16.2 minimum or a nightly with Krypton.

Martin

[madas]

Here is the web.log again with only one client..it seems to be stuck in a loop even with only one this time