Page 4 of 4 FirstFirst ... 234
Results 31 to 37 of 37

Thread: New recordings not updating

  1. #31
    Join Date
    Nov 2003
    Location
    NextPVR HQ, Wellington, New Zealand
    Posts
    87,311
    Quote Originally Posted by mvallevand View Post
    That is what I figured but based on the last set of logs that won't fix it, since the logs show that all the calls to lastupdated were failing with length 0 even though the web server was returning the correct time.
    I'm no expert at reading kodi logs, but what log messages makes you think that?

  2. #32
    Join Date
    May 2006
    Location
    Canada
    Posts
    26,448
    14:41:32.385 T:1449128704 DEBUG: CurlFile::Open(0x64a5e388) http://192.168.2.4:8866/service?meth...4c0387e5e5fa2c
    14:41:32.597 T:1440740096 DEBUG: Thread FileCache start, auto delete: false
    14:41:32.597 T:1440740096 INFO: CFileCache::Process - Source read didn't return any data! Hit eof(?)
    14:41:32.647 T:1440740096 DEBUG: Thread FileCache 1440740096 terminating

    The fact that the disabling only occurs on the 30 second timeout shows the network is the source of the problem not the web server so it doesn't really fix the problem Getting rid of it just means that it might update some time. The live tv playback shows the EAGAIN issue that the http call doesn't handle at all.

    Martin

  3. #33
    Join Date
    Nov 2003
    Location
    NextPVR HQ, Wellington, New Zealand
    Posts
    87,311
    I'm pretty sure the "CFileCache::Process - Source read didn't return any data! Hit eof(?)" isn't saying it returned no data. It's just saying it's read until the end of the response. Likely means the last loop to read more data from the socket got no more data. ie, you'll see the same thing on the successful calls, like session.login

    14:37:01.080 T:1905259264 DEBUG: CurlFile::Open(0x71048bb0) http://192.168.2.4:8866/service?meth...E6CCC6E2FB065B
    14:37:01.096 T:1549792000 DEBUG: Thread FileCache start, auto delete: false
    14:37:01.096 T:1549792000 INFO: CFileCache::Process - Source read didn't return any data! Hit eof(?)
    14:37:01.146 T:1549792000 DEBUG: Thread FileCache 1549792000 terminating

  4. #34
    Join Date
    Sep 2004
    Location
    Winsford, UK
    Posts
    584
    Just to add a bit of input. The network is hardwired Gigabit and this test was done on the latest RPi 3B+ hardware which is supposed to have better ethernet than the older models.
    I assume the blocking being referred to is in the software handling the ethernet connectivity for Kodi on the RPi and not specifically the hardware.
    From a bit of further testing, it looks like this update stop can consistently be triggered after watching live tv on the RPi.
    NPVR Version= 4.2.2
    Intel i7 Quad Core 3200 + 16GB DDR2 Gigabyte Motherboard
    Windows 10 Pro 64bit
    BlackGold dual DVB T & S tuner
    60Gb SSD System Disk (Raid 1)
    60Gb SSD Recording Cache
    4Tb Media Store (WD Red 4Tb x 2 in Raid 1)

    Raspberry 2 x Pi2 running OSMC (Kodi v17.6)
    Raspberry Pi3 B+ running OSMC (Kodi v17.6)

  5. #35
    Join Date
    Sep 2004
    Location
    Winsford, UK
    Posts
    584
    Sub. If you get to know when the change has been included in the v18 beta I'll happily test on one of my RPs's
    NPVR Version= 4.2.2
    Intel i7 Quad Core 3200 + 16GB DDR2 Gigabyte Motherboard
    Windows 10 Pro 64bit
    BlackGold dual DVB T & S tuner
    60Gb SSD System Disk (Raid 1)
    60Gb SSD Recording Cache
    4Tb Media Store (WD Red 4Tb x 2 in Raid 1)

    Raspberry 2 x Pi2 running OSMC (Kodi v17.6)
    Raspberry Pi3 B+ running OSMC (Kodi v17.6)

  6. #36
    Join Date
    May 2006
    Location
    Canada
    Posts
    26,448
    The problem is not Kodi it is the network stack it does not handle things as gracefully as any other device I have seen and quickly returns no data warnings which originally the pvr adon wasn't handling for steaming. And your logs are full of these retries. This was fixed but the same problem was not fixed for API calls. Subs fix will mask the problem because it will continue to retry in the minutes and hours ahead.

    There is no reason that things should get disabled now though. Thirty seconds is much too long for that call and if it isn't your RPI you need to get check your network.

    Martin

  7. #37
    Join Date
    Sep 2004
    Location
    Winsford, UK
    Posts
    584
    Thanks for the explanation Martin.
    I'm pretty confident in my network not being the problem as I'm not seeing any network issues across any other devices attached. (and most of my rather long working life has been spent in IT hardware / system design . I do have some software writing experience but mostly on somewhat larger systems)
    I do see the same problem consistently on all the RPi's so I think you're spot on with pointing to their poor network handling.
    Shame considering they're pretty good for their overall cost/size.
    NPVR Version= 4.2.2
    Intel i7 Quad Core 3200 + 16GB DDR2 Gigabyte Motherboard
    Windows 10 Pro 64bit
    BlackGold dual DVB T & S tuner
    60Gb SSD System Disk (Raid 1)
    60Gb SSD Recording Cache
    4Tb Media Store (WD Red 4Tb x 2 in Raid 1)

    Raspberry 2 x Pi2 running OSMC (Kodi v17.6)
    Raspberry Pi3 B+ running OSMC (Kodi v17.6)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •