PVR Addon for Kodi 17

[the_man]

Bump...@the_man @oberon

I'm running KODI Krypton Beta 5 on RPI2 Librelec, and while in general everything is very stable, including the DVblink client, there is one small issue that I wonder if anyone knows about or is also seeing...
The DVBlink client is fine until we go to bed...the PI2 then stays turned on over night and then in the morning, we try to pick a live TV channel and Kodi hangs. Unplug the power and then everything is OK again.
Anyone any ideas?

Are you aware of this behaviour?
Is it a kodi issue or a DVBlink client issue?

I have not faced with that issue. May you provide a log files with the reproduced issue?

[solomalee]

Hi the_man,

Find attached a collection of log files - these are from two Raspberry PI, both running KODI 17 Beta 5 with the same basic configuration (Built from the same configuration backup). They are named PI_ATTIC & PI_LIVINGROOM respectively and both exhibit exactly the same behaviour:

After the TV is turned off at ~23:30 and turned back on in the morning (about 7 hours not being used overnight), I navigate to TV, select BBC1 from the channel list and click select to switch to that channel. The spinning timer appears and the TV channel never switches. (I notice that the onscreen Debug information is still happily updating on screen at top left)

Here are the log files for PI_ATTIC taken after I navigated to TV and selected from the channel list BBC 1
https://dl.dropboxusercontent.com/u/14484025/pi_attic.zip

For PI_LIVINGROOM, I have two versions of the log files for you...
One set taken before the TV freeze:
https://dl.dropboxusercontent.com/u/14484025/pi_livingroom_pre.zip

One set taken after the TV freeze:
https://dl.dropboxusercontent.com/u/14484025/pi_livingroom_post.zip

I tried last night waiting various lengths of time, I am up to 2 hours now with the TV off (PI running) and the error doesn't manifest itself, today, I'll be increasing to 3 hours, 4 hours etc until I find out how long it takes for this failure to manifest itself.

I also tried yesterday turning off the wifi connection and turning it back on again before trying to change TV channels, with this action taken, the first time TV channel change after overnight "sleep" had no problems.

[the_man]

Hi the_man,

Find attached a collection of log files - these are from two Raspberry PI, both running KODI 17 Beta 5 with the same basic configuration (Built from the same configuration backup). They are named PI_ATTIC & PI_LIVINGROOM respectively and both exhibit exactly the same behaviour:

After the TV is turned off at ~23:30 and turned back on in the morning (about 7 hours not being used overnight), I navigate to TV, select BBC1 from the channel list and click select to switch to that channel. The spinning timer appears and the TV channel never switches. (I notice that the onscreen Debug information is still happily updating on screen at top left)

Here are the log files for PI_ATTIC taken after I navigated to TV and selected from the channel list BBC 1
https://dl.dropboxusercontent.com/u/1448..._attic.zip

For PI_LIVINGROOM, I have two versions of the log files for you...
One set taken before the TV freeze:
https://dl.dropboxusercontent.com/u/1448..._attic.zip

One set taken after the TV freeze:
https://dl.dropboxusercontent.com/u/1448...m_post.zip

I tried last night waiting various lengths of time, I am up to 2 hours now with the TV off (PI running) and the error doesn't manifest itself, today, I'll be increasing to 3 hours, 4 hours etc until I find out how long it takes for this failure to manifest itself.

I also tried yesterday turning off the wifi connection and turning it back on again before trying to change TV channels, with this action taken, the first time TV channel change after overnight "sleep" had no problems.

Links are not correct.

[solomalee]

Sorry about that...not sure what happened. I've updated the links in the original post - they should work now.

Solo

[the_man]

Sorry about that...not sure what happened. I've updated the links in the original post - they should work now.

Solo

I'd like to check the dvblink logs as well (with reprocessed issue and log level set to info )

[solomalee]

Sorry about that...not sure what happened. I've updated the links in the original post - they should work now.

Solo

I'd like to check the dvblink logs as well (with reprocessed issue and log level set to info )

Here you go...hope this is set at the right logging level for you. Logging was set to errors and warnings only. I've changed it to info now I'll need to upload new logs later when the freeze issue reoccurs.

https://dl.dropboxusercontent.com/u/14484025/dvblink-log-20161118-1145.zip

Solo

[solomalee]

Some additional information...I've installed KODI 17 Beta 5 on OSX and see that the issue seems to be replicated there too.

Solo

[solomalee]

I'd like to check the dvblink logs as well (with reprocessed issue and log level set to info )

Hi the_man

Here's a new log file...just had the failure again at ~2225CET - hope you see something in this.

https://dl.dropboxusercontent.com/u/14484025/dvblink-log-20161119-2232.zip

Solo

[Traxx]

Hi all,

I had the same Issue using the (meanwhile 1 week old) nightly of Kodi 17 beta with the DVBlink plugin comming with it and the current version of DVBlink server.
Really annoying, Kodi crashed almost every time after it had been running for a while (the PC is always on or on standby because it also hosts the dvblink-Server and manages the recordings).
Then I tried something that seems to have solved it (only three kodi crashes so far which seem to be related to be nightly I'm using as they happend randomly not having something to do with TV)

My recordings are stored on a different physical drive than the system including kodi and dvb-link. So with the standard power cofiguration windows turns off the hard drive not currently in use.
So when kodi sets the PC into sleep and wakes it up later, the second hard drive might continue to sleep. When you now try to enter the TV recordings section it doesn't find whats supposed to be there and crashes.

Solution:
Set the HDD idle time to the highest possible value, so that its always on when the PC is not sleeping. (When the PC is sleeping its turned off as well, so the environment and power bill are fine )

I had this issue before with Kodi 16, but that version didn't crash, I "just" didn't show any recordings until kodi was restarted. Also annying...
Would it be possible to always send a wakeup event when opening the section? This would solve all issues for users with multiple hard drives...

[solomalee]

Hi Traxx,

Not quite the same problem - my DVBlink server is running all together in a Synology NAS with all internal drives.

I've wondered if it was an overnight sleep issue (or some overnight scheduled job, but I've now seen the issue during day time too.

Solo

[Traxx]

Hi Traxx,

Not quite the same problem - my DVBlink server is running all together in a Synology NAS with all internal drives.

I've wondered if it was an overnight sleep issue (or some overnight scheduled job, but I've now seen the issue during day time too.

Solo

Hi Solomalee,

ok, then your problem might be a different one. But maybe not, as we both have the problem "Kodi trying to access recordings which aren't there"... (In my case second HDD, in yours NAS maybe not reacting quick enough)
Could be related to the Kodi (advanced) option "try to wake remote servers". Do you have that activated?
Afaik the function calls have been changed in Kodi 17 and maybe the plugin is sending the v16 one who's misinterpretation in v17 is causing it to crash?

Just some thoughts for the developer.

[solomalee]

Hi traxx,

My problem is accessing Live TV from the channel list - I haven't noticed that I have a fail to access recorded TV too - I'll need to check that.

Solo

[the_man]

Hi traxx,
My problem is accessing Live TV from the channel list - I haven't noticed that I have a fail to access recorded TV too - I'll need to check that.
Solo

Your log files looks a quite good. Just to clarify - Can you play LiveTV on any other device/client from the same server after the night? Just need to know whether the server still alive in a full way.

[solomalee]

My windows MCE uses the same DVBlink backend and never has this problem. Same with DVBlink client never seen this issue.

But it happens on every KODI Krypton Beta client (all 4). I've not used Jarvis much, but when I did, I also never noticed such a problem.

If my RPIs would switch off and on with the TV I suppose I would almost never see this problem, but turning a PI back on with a remote needs extra hardware and config.

Solo

[solomalee]

I have now confirmed that after Kodi (Pi2) has been left running over night unused for ~6 hours,

1. When selecting a channel from Channels icon Guide or recently watched from the DVBlink KODI TV client, KODI freezes (list of TV channels is shown or guide is shown)

NEW
2. When choosing the Recorded TV icon from the DVBlink KODI TV client, KODI freezes (no list of recordings is shown)

Solo