Recorded shows no longer refreshing when selecting "Recordings" in Kodi.

[shaneypoopers]

Great in those logs it is showing that it makes the calls to update the recording about every minute. Are you sure dynamic updates aren't working (dynamic meaning there could be a one minute lag so not real time)

Martin

Hi Martin,

I actually wiped the SD card and restarted from scratch yesterday so maybe something got fixed in that process. I do think a recording popped up this morning so maybe it's all good now. I'll keep an eye on it and if I have any further problems I'll let you know.

Thanks again for looking at this for me it's much appreciated, and will keep the Mrs of my back.

Shane

[shaneypoopers]

Great in those logs it is showing that it makes the calls to update the recording about every minute. Are you sure dynamic updates aren't working (dynamic meaning there could be a one minute lag so not real time)

Martin

Hi Martin,

So after leaving it for a few days I have noticed that while it updates OK for a few hours after a restart, it stops updating after a while.

I'm wondering if the server reboot could be causing it? I have a scheduled reboot everyday at 0400. If the client can't connect does it give up?

I have just turned debugging on, last few minutes of log should have it enabled but I've uploaded the whole log in case it is needed.

http://xbmclogs.com/pkf0hr3ee

Thanks again,

Shane

[mvallevand]

From that log you were playing radio for many hours then but when you tried to play a recording at 14:26:13 there was errors on the API and the call to refresh failed at 15:33 so I don't think that is a 4am thing. That web.log at those time would have maybe offered a clue

With the 4am power off there is possibility that dynamic updates will fail too but in this case they were already off.

Martin

[shaneypoopers]

From that log you were playing radio for many hours then but when you tried to play a recording at 14:26:13 there was errors on the API and the call to refresh failed at 15:33 so I don't think that is a 4am thing. That web.log at those time would have maybe offered a clue

With the 4am power off there is possibility that dynamic updates will fail too but in this case they were already off.

Martin

Hi Martin,

So is there an error in my set up or is it with the error handling? If the dynamic update fails does it try again later or is it gone until restart?

Thanks,

Shane

[mvallevand]

Hi Martin,

So is there an error in my set up or is it with the error handling? If the dynamic update fails does it try again later or is it gone until restart?

It's the whole PVR API that is failing so something is wrong. It shows as no dynamic updates, but you likely can't set recording get updates to the guide or play recordings or live tv. If it is you or OpenElect the only thing I'd suggest is turning off MySQL and make sure your client has a fixed IP you leave it running longer than your server.

sub should probably also turn off that version check since I wrote that months before 3.4 was available.

Martin

[shaneypoopers]

It's the whole PVR API that is failing so something is wrong. It shows as no dynamic updates, but you likely can't set recording get updates to the guide or play recordings or live tv. If it is you or OpenElect the only thing I'd suggest is turning off MySQL and make sure your client has a fixed IP you leave it running longer than your server.

sub should probably also turn off that version check since I wrote that months before 3.4 was available.

Martin

Hi Martin,

Both client and server have fixed IPs. Clients are always on and server is always on apart from the 0400 reboot.

PVR works fine, guide updates, recordings and live tv play. The only part that doesn't work is the dynamic refresh for recordings.

Thanks,

Shane

[mvallevand]

PVR works fine, guide updates, recordings and live tv play. The only part that doesn't work is the dynamic refresh for recordings.

Not according to the logs you posted. Here some other examples of API failures outtside the 4am windows

14:26:34 T:1649419328 ERROR: Open - failed to open source <http://192.168.0.90:8866/service?method=recording.recurring.list&sid=bb693f40955148ba83abe1147a36b821>

20:03:41 T:1649419328 ERROR: Open - failed to open source <http://192.168.0.90:8866/service?method=recording.list&filter=pending&sid=bb693f40955148ba83abe1147a36b821>

Unless of course you have no recurring recordings or pending records, but that doesn't explain why the dynamic update call is failing which is why I would need the matching web.log

Code:

15:33:11 T:1649419328  NOTICE: Previous line repeats 34 times.
15:33:11 T:1649419328   ERROR: CCurlFile::FillBuffer - Failed: Failure when receiving data from the peer(56)
15:33:11 T:1649419328   ERROR: CCurlFile::CReadState::Connect, didn't get any data from stream.
15:33:11 T:1649419328   ERROR: Open - failed to open source <http://192.168.0.90:8866/service?method=recording.lastupdated&sid=bb693f40955148ba83abe1147a36b821>

Sorry I am pretty much done here, the call is being made and it works sometimes. I don't have what OE and Kodi and NextPVR do to make http connection work you need to find out why you are getting this timeout so often

Code:

12:16:24 T:1733305408   ERROR: CCurlFile::FillBuffer - Failed: Failure when receiving data from the peer(56)
12:16:24 T:1733305408  NOTICE: CCurlFile::FillBuffer - Reconnect, (re)try 1
12:16:25 T:1733305408   ERROR: CCurlFile::FillBuffer - Failed: Requested range was not delivered by the server(33)

I am no sure that is even from NextPVR, but it's a repeated likely http problem.

Martin

[shaneypoopers]

Not according to the logs you posted. Here some other examples of API failures outtside the 4am windows

14:26:34 T:1649419328 ERROR: Open - failed to open source <http://192.168.0.90:8866/service?method=recording.recurring.list&sid=bb693f40955148ba83abe1147a36b821>

20:03:41 T:1649419328 ERROR: Open - failed to open source <http://192.168.0.90:8866/service?method=recording.list&filter=pending&sid=bb693f40955148ba83abe1147a36b821>

Unless of course you have no recurring recordings or pending records, but that doesn't explain why the dynamic update call is failing which is why I would need the matching web.log

Code:

15:33:11 T:1649419328  NOTICE: Previous line repeats 34 times.
15:33:11 T:1649419328   ERROR: CCurlFile::FillBuffer - Failed: Failure when receiving data from the peer(56)
15:33:11 T:1649419328   ERROR: CCurlFile::CReadState::Connect, didn't get any data from stream.
15:33:11 T:1649419328   ERROR: Open - failed to open source <http://192.168.0.90:8866/service?method=recording.lastupdated&sid=bb693f40955148ba83abe1147a36b821>

Sorry I am pretty much done here, the call is being made and it works sometimes. I don't have what OE and Kodi and NextPVR do to make http connection work you need to find out why you are getting this timeout so often

Code:

12:16:24 T:1733305408   ERROR: CCurlFile::FillBuffer - Failed: Failure when receiving data from the peer(56)
12:16:24 T:1733305408  NOTICE: CCurlFile::FillBuffer - Reconnect, (re)try 1
12:16:25 T:1733305408   ERROR: CCurlFile::FillBuffer - Failed: Requested range was not delivered by the server(33)

I am no sure that is even from NextPVR, but it's a repeated likely http problem.

Martin

Hi Martin,

Would there not be lots of network issues that might mean an update would fail? I'm using an AC wireless network and have absolutely no other network issues. Surely NPVR/addon should be able to handle failures when they occur and try refresh at a later point, or is my set up getting so many failures it can't cope? The web.log from that time is gone I tried to get it when I posted the Kodi log.

I have linked the Kodi and NPVR logs for the last few minutes with debugging switched on. I really don't have enough of an understanding of the system to diagnose what the problem is. I'm an engineer by trade not in IT.

I understand if you can't help, maybe it is an issue outside of NPVR but I'm not getting any other problems, as I say I can play live TV and watch recordings, guide updates etc. When I delete a recording I get a recording refresh ok, I did this during the logging period so maybe this will help?

I don't think my set up is that unusual and I followed the wiki guidance when setting it up. Maybe others are having the same problem?

Kodi log - http://xbmclogs.com/pkndbdscz

NPVR logs - http://drive.google.com/folderview?id=0B...sp=sharing

Thanks again,

Shane

[mvallevand]

NextPVR is telling Kodi the last update was Mon, 22 Jun 2015 16:24:04 GMT which matches the time NRecord was launched and no recordings have been made since then. I don't know what more you expect me to tell you then it is working as designed. In an earlier post I did write should remove the current error check for 3.4

You are running on a RPi though and that I consider to have some of the worst network devices available, plus sub didn't put a lot of error checking into the code like the NextPVR client a good error free connection is assumed. I added a bit to make live tv work better on the RPi, but it could be improved.

Martin

[shaneypoopers]

NextPVR is telling Kodi the last update was Mon, 22 Jun 2015 16:24:04 GMT which matches the time NRecord was launched and no recordings have been made since then. I don't know what more you expect me to tell you then it is working as designed. In an earlier post I did write should remove the current error check for 3.4

You are running on a RPi though and that I consider to have some of the worst network devices available, plus sub didn't put a lot of error checking into the code like the NextPVR client a good error free connection is assumed. I added a bit to make live tv work better on the RPi, but it could be improved.

Martin

OK, thanks for looking at it for me. It is much appreciated.

I can just restart when I need a refresh and I'll dump all the MySQL databases to see if that helps.

Thanks again,

Shane