Kodi Community Forum

Hi, I'm running OpenELEC 5.0.3 with VDR & vnsi on rPi2 as both backend and client. Watching TV and time shifting works great. It's only when I'm doing anything with recordings (I use the live interface) that things go awry.

I set my Timeshift to a local USB flash drive, and my recording path to a NAS (ext4, NFS) that is mounted on boot with the systemd method here: http://wiki.openelec.tv/index.php/Mounti...ork_shares

Basically, more often than not, when the time comes for VDR to record something, it writes an info, and empty index/TS files, 0 bytes in size. When manipulating timers and recordings, the Live UI tends to crash and sometimes restarts automatically. For example, I tried to cancel a timer; browser gives me the "can't connect" error, I try entering the UI again, it works, and this time around I can cancel the timer successfully. Recordings work sometimes, seemingly randomly. I realise this info is not all that useful without logs, so how would I go about setting the log level in OpenELEC? And where is it stored?

What do you consider the "live interface"?

The web UI: https://www.hagen-bauer.de//201011/201011-vdr-life.png

Try to grab syslog which is iirc called messages on OE. Maybe it tells us what plugin crashes or if it is vdr itself.

Doesn't appear to be a cat /var/log/messages file, so some googling led me to


Which gave me this: http://pastebin.com/j8f6i2y5

And Kodi's log: http://pastebin.com/gdBwdkYF

In the above logs, all I did was power the Pi 2, log into VDR's web UI on my PC, and schedule a recording of a show that was currently airing. The resultant TS file is 0 bytes.

System log of me cancelling that timer-- the browser times out when I do. I then try the home page of the web UI a moment later, and am able to cancel it successfully and then delete the recording (which doesn't actually get deleted when I check the NAS):

Syslog: http://pastebin.com/8CZ65EPd
Kodi: http://pastebin.com/Hws3Xkrw

Quote:Feb 23 22:43:07 OpenELEC vdr[746]: [808] ERROR: video data stream broken
Feb 23 22:43:07 OpenELEC vdr[746]: [808] initiating emergency exit
Feb 23 22:43:08 OpenELEC vdr[746]: [746] emergency exit requested - shutting down

looks like a vdr error message. google shows that there should be a vdr setting to disable emergency exits.

vdr-plugin-live was buggy on timers some time ago.
In VDR - Forum we were discussing and fixing it here

are you saying that you found a fix? do you see any relationship of the issue to vnsi?

In the following logs, I booted the Pi 2, scheduled a timer (again, 0 bytes TS file), deleted the timer and then the recording (again, the recording wasn't actually deleted). This is with emergency exits off, which appears to have stopped the web UI from crashing.

syslog: http://pastebin.com/d5rVDN5L
kodi: http://pastebin.com/Xk108DCx

This log shows me scheduling two recordings on different channels simultaneously (dual tuner), one of them works, the other writes 0 bytes: http://pastebin.com/LsxxHcJW

The web UI hasn't crashed so far. Edit: yep, appears to have solved the crashing, scheduled and deleted a lot of times, no crash.

I think a higher log level might be more revealing but I'm not sure how to set that in OpenELEC

Edit: Think I may have found the problem, will test later tonight or tomorrow

If fiddling around with live-plugin crashes vdr - i don't see a link with vnsi.