Login at Kodi Home

Spirou · (This post was last modified: 2017-06-13, 20:16 by Spirou.)

Seems like vdr development is gaining momentum. New releases are coming in quickly and latest release is already at 2.3.7.

I am wondering if it is safe to update vdr with every new release or if there are dependencies that would require adaption in vnsiserver and -client prior to upgrade.

My system is running on vdr 2.3.6 with kodi 17.3 and latest vniserver/vnsiclient with no compalints so far. However I noticed an issue posted on github regarding faulty lock sequence with current vnsiserver plugin and vdr 2.3.6. Hence I am considering downgrade to vdr 2.3.5. to avoid the potential issue.

FernetMenta, from your point of view, what is the recommended vdr release to run and how save is it currently to uprade to vdr 2.3.7?

FernetMenta · 2017-06-14, 07:44

I have not tried 2.3.6 and 2.3.7. This is on my list. 2.3.7 seems to be mostly fixes. One for false positive logs for wrong locking sequence introduced with 2.3.6. Maybe the isue reported on github goes away with 2.3.7

Spirou · 2017-06-15, 03:27

Just updated to vdr 2.3.7 and seems it's running smoothly. However, reporting of invalid lock sequence in syslog is still present. According to vdr developer adaptions in plugin code are required. Not sure, how this will affect my setup in the meantime....

FernetMenta · 2017-06-15, 08:23

I fixed the invalid locking sequence in vnsiserver. btw: this also affected earlier versions of vdr but with 2.3.6 it gets logged.

Spirou · 2017-06-16, 02:08

Great, thanks. Updated the vnsiserver plugin and no more invalid lock sequence messages in syslog. Smile

FernetMenta · 2017-07-14, 15:01

vdr stable release 2.4.0 is on the horizon

http://www.vdr-portal.de/board1-news/boa...375e4605f9

Spirou · 2018-01-06, 02:18

Out of a sudden I'm getting invalid lock seqence log messages again. Using latest vdr 2.3.8 develeoper release (w/o patches) and recent kodi 18 alpha from github:

Quote:Jan 6 01:06:49 kodi-mc vdr: [1961] timer 1 (52 1652-1725 'Dragons - Auf zu neuen Ufern') set to event Mo. 08.01.2018 16:55-17:20 'Dragons - Auf zu neuen Ufern'
Jan 6 01:06:49 kodi-mc vdr: [1961] timer 2 (52 1652-1725 'Dragons - Auf zu neuen Ufern') set to event Di. 09.01.2018 16:55-17:20 'Dragons - Auf zu neuen Ufern'
Jan 6 01:06:49 kodi-mc vdr: [1961] timer 3 (52 1652-1725 'Dragons - Auf zu neuen Ufern') set to event Mi. 10.01.2018 16:55-17:20 'Dragons - Auf zu neuen Ufern'
Jan 6 01:06:49 kodi-mc vdr: [1961] max. latency time 2 seconds
Jan 6 01:06:49 kodi-mc vdr: [1974] VNSI: Requesting clients to reload timers
Jan 6 01:06:50 kodi-mc vdr: [1976] --- begin invalid lock sequence report
Jan 6 01:06:50 kodi-mc vdr: [1976] 1966 - W - - W - - - - - L
Jan 6 01:06:50 kodi-mc vdr: [1976] 1966 - * - - U - - - - - U
Jan 6 01:06:50 kodi-mc vdr: [1976] 1966 - U - - - - - - - - U
Jan 6 01:06:50 kodi-mc vdr: [1976] 1974 - R - - - - - - - - L
Jan 6 01:06:50 kodi-mc vdr: [1976] 1974 - U - - - - - - - - U
Jan 6 01:06:50 kodi-mc vdr: [1976] 1974 - - R - - - - - - - L
Jan 6 01:06:50 kodi-mc vdr: [1976] 1974 - - U - - - - - - - U
Jan 6 01:06:50 kodi-mc vdr: [1976] 1974 R - - - - - - - - - L
Jan 6 01:06:50 kodi-mc vdr: [1976] 1974 U - - - - - - - - - U
Jan 6 01:06:50 kodi-mc vdr: [1976] 1966 - W - - - - - - - - L
Jan 6 01:06:50 kodi-mc vdr: [1976] 1966 - * - - W - - - - - L
Jan 6 01:06:50 kodi-mc vdr: [1976] 1966 - * - - U - - - - - U
Jan 6 01:06:50 kodi-mc vdr: [1976] 1966 - U - - - - - - - - U
Jan 6 01:06:50 kodi-mc vdr: [1976] 1966 - W - - - - - - - - L
Jan 6 01:06:50 kodi-mc vdr: [1976] 1966 - U - - - - - - - - U
Jan 6 01:06:50 kodi-mc vdr: [1976] 1976 W - - - - - - - - - L
Jan 6 01:06:50 kodi-mc vdr: [1976] 1976 * - - - R - - - - - L
Jan 6 01:06:50 kodi-mc vdr: [1976] 1966 W W - - W - - - - - L
Jan 6 01:06:50 kodi-mc vdr: [1976] 1966 - U - - - - - - - - U
Jan 6 01:06:50 kodi-mc vdr: [1976] 1976 R - R - R - - - - - L
Jan 6 01:06:50 kodi-mc vdr: [1976] 1976 invalid lock sequence: 3 Recordings
Jan 6 01:06:50 kodi-mc vdr: [1976] full backtrace:
Jan 6 01:06:50 kodi-mc vdr: [1976] /usr/local/bin/vdr cStateLock::Lock(cStateKey&, bool, int) at thread.c:734
Jan 6 01:06:50 kodi-mc vdr: [1976] /usr/local/lib/vdr/plugins/libvdr-vnsiserver.so.2.3.8 CVNSITimers::Action() calling cRecordings::GetRecordingsRead(cStateKey&, int) at recording.h:236 at cRecordings_Lock::cRecordings_Lock(bool) at recording.h:298 at CVNSITimers::Action() at vnsitimer.c:459
Jan 6 01:06:50 kodi-mc vdr[1961]: invalid lock sequence at Sa. 06.01. 01:06
Jan 6 01:06:50 kodi-mc vdr: [1976] /usr/local/bin/vdr cThread::StartThread(cThread*) at thread.c:294
Jan 6 01:06:50 kodi-mc vdr: [1976] /lib/x86_64-linux-gnu/libpthread.so.0 at ??:?
Jan 6 01:06:50 kodi-mc vdr: [1976] /lib/x86_64-linux-gnu/libc.so.6 clone at clone.S:111
Jan 6 01:06:50 kodi-mc vdr: [1976] --- end invalid lock sequence report
Jan 6 01:06:50 kodi-mc vdr: [1976] --- THERE WILL BE NO FURTHER REPORTS UNTIL VDR IS RESTARTED!

Anything to worry about?

FernetMenta · 2018-01-06, 10:51

This feature of VDR is buggy and can even lead to crashing. I switched it off in my branch: https://github.com/FernetMenta/VDR/commi...c080b7374a

Spirou · 2018-01-06, 12:09

Ok, thanks.

If I understand correctly you only disabled the debug output for this feature in your branch. So I might continue to use my unpatched vdr and just ignore the log messages. In fact, besides the log messages, I've not noticed any defects.

Are there any other changes in your branch that would recommend its use instead of the original release from Klaus?

FernetMenta · 2018-01-06, 12:16

(2018-01-06, 12:09)Spirou Wrote: Ok, thanks.

If I understand correctly you only disabled the debug output for this feature in your branch.

Wrong. This disables the entire feature which is buggy. It's not just the logging but also the tracking of the locking.

Quote:Are there any other changes in your branch that would recommend its use instead of the original release from Klaus?

My branch is plain VDR with only this buggy feature disabled.