[FernetMenta]

great, I will prepare something until tomorrow. stay tuned.

[FernetMenta]

could you please try the following

- cd to vdr folder
- curl https://dl.dropboxusercontent.com/u/47522966/vdr.patch > vdr.patch
- patch < vdr.path
- make
- sudo make install

please post syslog

[salose]

Done.
Syslog here: http://pastebin.ca/2890712

Not sure if it is of any help, the latest, patched version no longer spams syslog with the same lines.
The git version seems to be 2.1.6 where as the version available from yavdr repositories (that had the issue) was 2.0.6.

Lines like these seem to be new:
Dec 22 01:40:03 torni vdr: [10234] frontend 1/0 lost lock on channel 1, tp 562
Dec 22 01:40:03 torni vdr: [10234] frontend 1/0 regained lock on channel 1, tp 562
Dec 22 01:41:27 torni vdr: [10234] frontend 1/0 lost lock on channel 1, tp 562
Dec 22 01:41:27 torni vdr: [10234] frontend 1/0 regained lock on channel 1, tp 562
Dec 22 01:42:37 torni vdr: [10422] epg data writer thread started (pid=10226, tid=10422, prio=low)
Dec 22 01:42:37 torni vdr: [10422] epg data writer thread ended (pid=10226, tid=10422)
Dec 22 01:42:51 torni vdr: [10234] frontend 1/0 lost lock on channel 1, tp 562
Dec 22 01:42:51 torni vdr: [10234] frontend 1/0 regained lock on channel 1, tp 562
Dec 22 01:44:15 torni vdr: [10234] frontend 1/0 lost lock on channel 1, tp 562
Dec 22 01:44:15 torni vdr: [10234] frontend 1/0 regained lock on channel 1, tp 562

[tzieg]

Hi Fernet Menta,

I also have the issue with the vdr log entries. However, the state numbers do no increase as regularily as spider4's list and the numbers are significantly higher.

Dec 29 00:17:46 goldmund vdr: [30180] VNSI: Recordings state changed (798432)
Dec 29 00:17:46 goldmund vdr: [30180] VNSI: Requesting clients to reload recordings list
Dec 29 00:17:53 goldmund vdr: [30180] VNSI: Recordings state changed (798802)
Dec 29 00:17:53 goldmund vdr: [30180] VNSI: Requesting clients to reload recordings list
Dec 29 00:17:59 goldmund vdr: [30180] VNSI: Recordings state changed (799177)
Dec 29 00:17:59 goldmund vdr: [30180] VNSI: Requesting clients to reload recordings list
Dec 29 00:18:14 goldmund vdr: [30180] VNSI: Requesting clients to reload channel list

The message indicates that the clients have to reload the recordings list. Is that correct?

In my case that list is rather long and would cause severe workload problems if it needs to be reloaded every ~10s. That's what I see even on a Gotham-13.2 raspberry


Details

- vdr 2.0.3 (from e-toby.net), debian wheezy (ix86), vdr-plugin-vnsi compiled from you git repository

- pi-1
o Raspbmc /w xbmc-13.2, works usually without any issues
o There are no log messages like ones above in the vdr.log

- pi-2
o Raspbmc, was also a xbmc-13.2 but got automatically updated to kodi-14
o since the update, the machine behaves strange, crashes sometimes, and I'm not the only one
(see VNSI related comments at http://goo.gl/Sb0Z7F)
o As soon, as I activate the VNSI-plugin here, the log messages above appear

The strange thing is that on pi-1 those message have a huge impact on the GUI-responsivenes of anything below Live-TV->Recordings. The CPU-load goes up to 98% just after a new reload recordings request.

Any thoughts?

Thanks,
Thomas

[FernetMenta]

as stated by saloze, the issue goes away with an upgrade of vdr. Something must hammering at the recordings state of vdr if the counter increases this fast. You can either upgrade vdr or execute the steps in post 17 to track it down further.

[tzieg]

Hi FernetMenta,

thanks for the fast feedback.

I had to adapt your patch from post 17 --recording.c from 2.0.3 is rather different to the current head revision.

According to the marker, the issue seems to come from cRecordings::ScanVideoDir().

This function shows work in progress in nearly all versions since 2.0.3.
I gave 2.0.6 from Debian-sid a try: With that one, kodi-14 works as expected, but the impact on the xbmc-13.2 raspi is still there --as well as the log messages.

It's good to know that the head revision seems to be ok regarding the 'recordings state changed'. For now, I'd like to stay with Debian packages.

Best, Thomas

[FernetMenta]

you can disable "allow vdr messages" (addon setting) on the pi. then it won't get the update notifications.

[martin.haager]

Same Problem over here

using:
- yavdr 2.0.6 from https://launchpad.net/~yavdr/+archive/ub...esting-vdr
- compiled vdr-plugin-vnsiserver 1.2.0 from FernetMenta's GIT
- Helix 14 stable
on xbmcbuntu (or should I say KODIbuntu :-)

syslog complains every 10 seconds about
- VNSI: Recordings state changed (1494)
- VNSI: Requesting clients to reload recordings list

Also from time to time my vdr server crashes
Helix complains about loosing connection to PVR
VDR Log shows crash and restart
But this seams to happen when switchin channels pretty fast
Have to dig deeper into this :-)

No Problems when running
- Gotham Stable
- vdr-plugin-vnsiserver 1:0.9.2~git20130714.1106-5b20fa5-2yavdr4~trusty

[FernetMenta]

why don't you upgrade to vdr 2.1.6 which solved the issue

[martin.haager]

Yep guess I'm gonna go for that :-)

would you compile yourself or is

yavdr unstable (vdr 2.1.6-8yavdr0~trusty) "stable" enough to use as productive environment

https://launchpad.net/~yavdr/+archive/ub...ter=trusty

either ways ok for me :-)

thx4info
Martin

[martin.haager]

so far so good

upgraded to yavdr unstable 2.1.6
error concerning "Recording State Changed" is gone

But as mentioned before... when switching channels pretty fast my vdr crashes.

or lets say vdr restarts
runvdr: restarting VDR

haven't had this problems with
- Gotham Stable
- vnsi-client 1.9.8
- vdr 2.0.6 (yavdr testing)
- vdr-plugin-vnsiserver 1:0.9.2~git20130714.1106-5b20fa5-2yavdr4~trusty

Code:

dpkg -l | grep vdr

ii  vdr                                 2.1.6-8yavdr0~trusty                     amd64        Video Disk Recorder for DVB cards
ii  vdr-dev                             2.1.6-8yavdr0~trusty                     all          Video Disk Recorder for DVB cards
ii  vdr-plugin-epgsearch                1.0.1.beta5~git20141227-0yavdr0~trusty   amd64        VDR plugin that provides extensive EPG searching capabilities
ii  vdr-plugin-live                     0.3.0+git20130915-6yavdr0~trusty         amd64        Web administration plugin for VDR
ii  vdr-plugin-restfulapi               20141221100726unstable-0yavdr0~trusty    amd64        VDR restfulapi
ii  vdr-plugin-streamdev-server         0.6.1.git20140919-0yavdr0~trusty         amd64        VDR Plugin to stream Live-TV to other VDR's - server part
ii  vdr-plugin-vnsiserver               1.1.0~git20141008-a7cb405-0yavdr0~trusty amd64        VDR-Network-Streaming-Interface

Code:

vdr -V

vdr (2.1.6/2.1.6) - The Video Disk Recorder
restfulapi (0.2.0) - Offers a RESTful-API to retrieve data from VDR
quickepgsearch (0.0.1) - Quick search for broadcasts
epgsearchonly (0.0.1) - Direct access to epgsearch's search menu
epgsearch (1.0.1.beta5) - search the EPG for repeats and more
conflictcheckonly (0.0.1) - Direct access to epgsearch's conflict check menu
streamdev-server (0.6.1-git) - VDR Streaming Server
vnsiserver (1.2.0) - VDR-Network-Streaming-Interface (VNSI) Server
live (0.3.0) - Live Interactive VDR Environment

Code:

tail -f syslog | grep vdr

Dec 30 23:45:08 svirt01 vdr: [19360] cLiveStreamer stream processor thread ended (pid=19204, tid=19360)
Dec 30 23:45:08 svirt01 vdr: [19348] VNSI: LiveStreamer::Close - close
Dec 30 23:45:08 svirt01 vdr: [19348] VNSI: close video input ...
Dec 30 23:45:08 svirt01 vdr: [19348] VNSI: call retune ...
Dec 30 23:45:08 svirt01 vdr: [19348] CAM 1: unassigned
Dec 30 23:45:08 svirt01 vdr: [19348] VNSI: call retune ...
Dec 30 23:45:08 svirt01 vdr: [19348] VNSI: close video input ...
Dec 30 23:45:09 svirt01 runvdr: restarting VDR
Dec 30 23:45:28 svirt01 vdr: [19389] VDR version 2.1.6 started
Dec 30 23:45:28 svirt01 vdr: [19389] switched to user 'vdr'
Dec 30 23:45:28 svirt01 vdr: [19389] codeset is 'UTF-8' - known
Dec 30 23:45:28 svirt01 vdr: [19389] found 28 locales in /usr/share/locale
Dec 30 23:45:28 svirt01 vdr: [19389] loading plugin: /usr/lib/vdr/plugins/libvdr-restfulapi.so.2.1.6
Dec 30 23:45:28 svirt01 vdr: [19389] restfulapi: Port has been set to 8002!
Dec 30 23:45:28 svirt01 vdr: [19389] restfulapi: Ip has been set to 0.0.0.0!
Dec 30 23:45:28 svirt01 vdr: [19389] restfulapi: trying to parse command line arguments
Dec 30 23:45:28 svirt01 vdr: [19389] restfulapi: Port has been set to 8002!
Dec 30 23:45:28 svirt01 vdr: [19389] restfulapi: Ip has been set to 0.0.0.0!
Dec 30 23:45:28 svirt01 vdr: [19389] RESTful-API Settings: port: 8002, ip: 0.0.0.0, eimgs: , cimgs: i, headers: activated
Dec 30 23:45:28 svirt01 vdr: [19389] loading plugin: /usr/lib/vdr/plugins/libvdr-quickepgsearch.so.2.1.6
Dec 30 23:45:28 svirt01 vdr: [19389] loading plugin: /usr/lib/vdr/plugins/libvdr-epgsearchonly.so.2.1.6
Dec 30 23:45:28 svirt01 vdr: [19389] loading plugin: /usr/lib/vdr/plugins/libvdr-epgsearch.so.2.1.6
Dec 30 23:45:28 svirt01 vdr: [19389] loading plugin: /usr/lib/vdr/plugins/libvdr-conflictcheckonly.so.2.1.6
Dec 30 23:45:28 svirt01 vdr: [19389] loading plugin: /usr/lib/vdr/plugins/libvdr-streamdev-server.so.2.1.6
Dec 30 23:45:28 svirt01 vdr: [19389] loading plugin: /usr/lib/vdr/plugins/libvdr-vnsiserver.so.2.1.6
Dec 30 23:45:28 svirt01 vdr: [19389] loading plugin: /usr/lib/vdr/plugins/libvdr-live.so.2.1.6
Dec 30 23:45:28 svirt01 vdr: [19389] [live] INFO: validating server ip '0.0.0.0'
Dec 30 23:45:28 svirt01 vdr: [19389] loading /var/lib/vdr/setup.conf
Dec 30 23:45:28 svirt01 vdr: [19389] ERROR: unknown config parameter: DumpNaluFill = 0
Dec 30 23:45:28 svirt01 vdr: [19389] ERROR: unknown config parameter: HardLinkCutter = 0
Dec 30 23:45:28 svirt01 vdr: [19389] ERROR: unknown config parameter: MaxRecordingSize = 100
Dec 30 23:45:28 svirt01 vdr: [19389] ERROR: unknown config parameter: PrimaryLimit = 0
Dec 30 23:45:28 svirt01 vdr: [19389] ERROR: unknown config parameter: SupportTeletext = 0
Dec 30 23:45:28 svirt01 vdr: [19389] ERROR: unknown config parameter: WarEagleIcons = 1
Dec 30 23:45:28 svirt01 vdr: [19389] loading /var/lib/vdr/sources.conf
Dec 30 23:45:28 svirt01 vdr: [19389] loading /var/lib/vdr/diseqc.conf
Dec 30 23:45:28 svirt01 vdr: [19389] loading /var/lib/vdr/scr.conf
Dec 30 23:45:28 svirt01 vdr: [19389] loading /var/lib/vdr/channels.conf
Dec 30 23:45:28 svirt01 vdr: [19389] loading /var/lib/vdr/timers.conf
Dec 30 23:45:28 svirt01 vdr: [19389] loading /var/lib/vdr/commands.conf
Dec 30 23:45:28 svirt01 vdr: [19389] loading /var/lib/vdr/reccmds.conf
Dec 30 23:45:28 svirt01 vdr: [19389] loading /var/lib/vdr/svdrphosts.conf
Dec 30 23:45:28 svirt01 vdr: [19389] loading /var/lib/vdr/keymacros.conf
Dec 30 23:45:28 svirt01 vdr: [19389] registered source parameters for 'A - ATSC'
Dec 30 23:45:28 svirt01 vdr: [19389] registered source parameters for 'C - DVB-C'
Dec 30 23:45:28 svirt01 vdr: [19389] registered source parameters for 'S - DVB-S'
Dec 30 23:45:28 svirt01 vdr: [19389] registered source parameters for 'T - DVB-T'
Dec 30 23:45:28 svirt01 vdr: [19389] probing /dev/dvb/adapter0/frontend0
Dec 30 23:45:28 svirt01 vdr: [19389] creating cDvbDevice
Dec 30 23:45:28 svirt01 vdr: [19390] video directory scanner thread started (pid=19389, tid=19390, prio=high)
Dec 30 23:45:28 svirt01 vdr: [19391] video directory scanner thread started (pid=19389, tid=19391, prio=high)
Dec 30 23:45:28 svirt01 vdr: [19389] new device number 1
Dec 30 23:45:28 svirt01 vdr: [19392] epg data reader thread started (pid=19389, tid=19392, prio=high)
Dec 30 23:45:28 svirt01 vdr: [19389] cTimeMs: using monotonic clock (resolution is 1 ns)
Dec 30 23:45:28 svirt01 vdr: [19392] reading EPG data from /var/cache/vdr/epg.data
Dec 30 23:45:28 svirt01 vdr: [19394] CI adapter on device 0 thread started (pid=19389, tid=19394, prio=high)
Dec 30 23:45:28 svirt01 vdr: [19392] epg data reader thread ended (pid=19389, tid=193

Any ideas welcome
regards martin

[martin.haager]

Another strange thing that happens

when LiveTV is running in minimized mode
or in full mode with info bar at the bottom

the epg info flickers / switches between the actual running program and an upcoming program on the same channel 12 hours ahead
lets say the info switches between these two entrys 5 times per second

same behavior using different skins
pvr and epg info already deleted and reimported

effects both helix stable on xbmcbuntu and Mac 10.10

again
any ideas welcome :-)
thanks martin

[FernetMenta]

Another strange thing that happens

when LiveTV is running in minimized mode
or in full mode with info bar at the bottom

the epg info flickers / switches between the actual running program and an upcoming program on the same channel 12 hours ahead
lets say the info switches between these two entrys 5 times per second

same behavior using different skins
pvr and epg info already deleted and reimported

effects both helix stable on xbmcbuntu and Mac 10.10

again
any ideas welcome :-)
thanks martin

This is fixed in vnsi addons master branch: https://github.com/opdenkamp/xbmc-pvr-ad...4ee7ed71c6

[martin.haager]

Thanks for this hint

just compiled and installed pvr.vdr.vnsi version="1.9.23" from opdenkamp's master for osx10.10 and xbmcbuntu 14.04
epg flickering vanished :-)

so seems that the sporadic vdr crashes / reboots are the last unsolved problem to start with Helix as my main TV Client..

As mentioned above.. didn't have this problem running vdr-plugin-vnsiserver 0.9.2
started when upgrading to vdr-plugin-vnsiserver 1.1.0

thanks for any direction where to search :-)
and by the way.....
happy 2015

[FernetMenta]

this may fix the remaining issue: https://github.com/FernetMenta/vdr-plugi...b58f457c95
Happy new year