2018-05-04, 16:07
This is the output I get in syslog when starting vdr 2.4.0 with latest vnsiserver:
Can this be ignored? What are the side effects of this?
Quote:May 4 15:51:19 kodi-mc vdr: [14298] --- begin invalid lock sequence reportvdr-2.4.0 has both offical patches from klaus and vnsiserver is latest code (as of May 1, 2018). vdr is running on ubuntu 16.04.03.
May 4 15:51:19 kodi-mc vdr: [14298] 14281 - U - - - - - - - - U
May 4 15:51:19 kodi-mc vdr: [14298] 14281 - U - - - - - - - - U
May 4 15:51:19 kodi-mc vdr: [14298] 14281 - W - - - - - - - - L
May 4 15:51:19 kodi-mc vdr: [14298] 14281 - U - - - - - - - - U
May 4 15:51:19 kodi-mc vdr: [14298] 14281 - W - - - - - - - - L
May 4 15:51:19 kodi-mc vdr: [14298] 14281 - * - - W - - - - - L
May 4 15:51:19 kodi-mc vdr: [14298] 14281 - * - - U - - - - - U
May 4 15:51:19 kodi-mc vdr: [14298] 14281 - U - - - - - - - - U
May 4 15:51:19 kodi-mc vdr: [14298] 14281 - W - - - - - - - - L
May 4 15:51:19 kodi-mc vdr: [14298] 14281 - * - - W - - - - - L
May 4 15:51:19 kodi-mc vdr: [14298] 14281 - * - - U - - - - - U
May 4 15:51:19 kodi-mc vdr: [14298] 14281 - U - - - - - - - - U
May 4 15:51:19 kodi-mc vdr: [14298] 14281 - W - - - - - - - - L
May 4 15:51:19 kodi-mc vdr: [14298] 14281 - U - - - - - - - - U
May 4 15:51:19 kodi-mc vdr: [14298] 14273 - R - - - - - - - - L
May 4 15:51:19 kodi-mc vdr: [14298] 14273 - * - - R - - - - - L
May 4 15:51:19 kodi-mc vdr: [14298] 14273 - * - - U - - - - - U
May 4 15:51:19 kodi-mc vdr: [14298] 14298 W W - - - - - - - - L
May 4 15:51:19 kodi-mc vdr: [14298] 14298 * - - - R - - - - - L
May 4 15:51:19 kodi-mc vdr: [14298] 14298 * - R - * - - - - - L
May 4 15:51:19 kodi-mc vdr: [14298] 14298 invalid lock sequence: 3 Recordings
May 4 15:51:19 kodi-mc vdr: [14298] full backtrace:
May 4 15:51:19 kodi-mc vdr: [14298] /usr/local/bin/vdr cStateLock::Lock(cStateKey&, bool, int) at thread.c:735
May 4 15:51:19 kodi-mc vdr: [14298] /usr/local/lib/vdr/plugins/libvdr-vnsiserver.so.2.4.0 CVNSITimers::Action() calling cRecordings::GetRecordingsRead(cStateKey&, int) at recording.h:237 at cRecordings_Lock::cRecordings_Lock(bool) at recording.h:299 at CVNSITimers::Action() at vnsitimer.c:459
May 4 15:51:19 kodi-mc vdr: [14298] /usr/local/bin/vdr cThread::StartThread(cThread*) at thread.c:294
May 4 15:51:19 kodi-mc vdr: [14298] /lib/x86_64-linux-gnu/libpthread.so.0 at ??:?
May 4 15:51:19 kodi-mc vdr: [14298] /lib/x86_64-linux-gnu/libc.so.6 clone at clone.S:111
May 4 15:51:19 kodi-mc vdr: [14298] --- end invalid lock sequence report
May 4 15:51:19 kodi-mc vdr: [14298] --- THERE WILL BE NO FURTHER REPORTS UNTIL VDR IS RESTARTED!
May 4 15:51:19 kodi-mc vdr[14273]: invalid lock sequence at Fr. 04.05. 15:51
Can this be ignored? What are the side effects of this?