Hello,
I'm running vdr 1.3.31 with a nova-t and a dxr3. I'm experiencing a lot sync problems, investigating in that problem I had to recognize that vdr builds a lot of subprocesses.
|-runvdr /usr/sbin/runvdr -v /video -c /var/lib/vdr -r /usr/lib/vdr/vdr-recordingaction -s... | `-vdr-kbd -v /video -c /var/lib/vdr -r /usr/lib/vdr/vdr-recordingaction -s/usr/lib/vdr/vdr-shut | `-vdr-kbd -v /video -c /var/lib/vdr -r /usr/lib/vdr/vdr-recordingaction -s... | |-vdr-kbd -v /video -c /var/lib/vdr -r /usr/lib/vdr/vdr-recordingaction -s... | |-vdr-kbd -v /video -c /var/lib/vdr -r /usr/lib/vdr/vdr-recordingaction -s... | |-vdr-kbd -v /video -c /var/lib/vdr -r /usr/lib/vdr/vdr-recordingaction -s... | |-vdr-kbd -v /video -c /var/lib/vdr -r /usr/lib/vdr/vdr-recordingaction -s... | |-vdr-kbd -v /video -c /var/lib/vdr -r /usr/lib/vdr/vdr-recordingaction -s... | |-vdr-kbd -v /video -c /var/lib/vdr -r /usr/lib/vdr/vdr-recordingaction -s... | |-vdr-kbd -v /video -c /var/lib/vdr -r /usr/lib/vdr/vdr-recordingaction -s... | `-vdr-kbd -v /video -c /var/lib/vdr -r /usr/lib/vdr/vdr-recordingaction -s...
Is that normal behaviour or some kind of misconfiguration? If so, how I can I put that right?
Any help is greatly appreciated! André
André Bischof wrote:
Hello,
I'm running vdr 1.3.31 with a nova-t and a dxr3. I'm experiencing a lot sync problems, investigating in that problem I had to recognize that vdr builds a lot of subprocesses.
|-runvdr /usr/sbin/runvdr -v /video -c /var/lib/vdr -r /usr/lib/vdr/vdr-recordingaction -s... | `-vdr-kbd -v /video -c /var/lib/vdr -r /usr/lib/vdr/vdr-recordingaction -s/usr/lib/vdr/vdr-shut | `-vdr-kbd -v /video -c /var/lib/vdr -r /usr/lib/vdr/vdr-recordingaction -s... | |-vdr-kbd -v /video -c /var/lib/vdr -r /usr/lib/vdr/vdr-recordingaction -s... | |-vdr-kbd -v /video -c /var/lib/vdr -r /usr/lib/vdr/vdr-recordingaction -s... | |-vdr-kbd -v /video -c /var/lib/vdr -r /usr/lib/vdr/vdr-recordingaction -s... | |-vdr-kbd -v /video -c /var/lib/vdr -r /usr/lib/vdr/vdr-recordingaction -s... | |-vdr-kbd -v /video -c /var/lib/vdr -r /usr/lib/vdr/vdr-recordingaction -s... | |-vdr-kbd -v /video -c /var/lib/vdr -r /usr/lib/vdr/vdr-recordingaction -s... | |-vdr-kbd -v /video -c /var/lib/vdr -r /usr/lib/vdr/vdr-recordingaction -s... | `-vdr-kbd -v /video -c /var/lib/vdr -r /usr/lib/vdr/vdr-recordingaction -s...
Is that normal behaviour or some kind of misconfiguration? If so, how I can I put that right?
Depending on how many DVB devices your system has, this is normal. See the log file for information on what these threads do.
Klaus
Klaus Schmidinger schrieb:
André Bischof wrote:
Hello,
I'm running vdr 1.3.31 with a nova-t and a dxr3. I'm experiencing a lot sync problems, investigating in that problem I had to recognize that vdr builds a lot of subprocesses.
...
Is that normal behaviour or some kind of misconfiguration? If so, how I can I put that right?
Depending on how many DVB devices your system has, this is normal. See the log file for information on what these threads do.
Hello Klaus,
thanks for your immediate answer, but I cannot see anything regarding processes in the logs - maybe I simply look at the wrong place? Or is one vdr-kbd process started for each plugin?
Starting vdr I get (first lines are the error I'm investigating in):
==> /var/log/messages <== Dec 13 09:21:54 linux vdr[15164]: cAudioRepacker: skipped 1117 bytes to sync on next audio frame Dec 13 09:21:54 linux vdr[15164]: cAudioRepacker: skipped 769 bytes to sync on next audio frame Dec 13 09:21:54 linux vdr[15164]: cAudioRepacker: skipped 269 bytes to sync on next audio frame Dec 13 09:21:54 linux vdr[15164]: cAudioRepacker: skipped 1467 bytes while syncing on next audio frame Dec 13 09:21:55 linux vdr[15164]: cAudioRepacker: skipped 1467 bytes while syncing on next audio frame Dec 13 09:21:55 linux vdr[15164]: cAudioRepacker: skipped 504 bytes to sync on next audio frame Dec 13 09:21:55 linux vdr[15164]: cAudioRepacker: skipped 146 bytes to sync on next audio frame ... Dec 13 11:15:56 linux vdr-kbd: deleting plugin: femon Dec 13 11:15:56 linux vdr-kbd: deleting plugin: remote Dec 13 11:15:56 linux vdr-kbd: deleting plugin: dxr3 Dec 13 11:15:56 linux vdr-kbd: deleting plugin: epgsearch Dec 13 11:15:56 linux vdr-kbd: deleting plugin: dvd Dec 13 11:15:56 linux vdr-kbd: deleting plugin: mp3 Dec 13 11:15:56 linux vdr-kbd: deleting plugin: sysinfo Dec 13 11:15:57 linux vdr[18068]: VDR version 1.3.31 started Dec 13 11:15:57 linux vdr[18068]: loading plugin: /usr/lib/vdr/plugins/libvdr-sysinfo.so.1.3.31 Dec 13 11:15:57 linux vdr[18068]: loading plugin: /usr/lib/vdr/plugins/libvdr-mp3.so.1.3.31 Dec 13 11:15:57 linux vdr[18068]: loading plugin: /usr/lib/vdr/plugins/libvdr-dvd.so.1.3.31 Dec 13 11:15:57 linux vdr[18068]: loading plugin: /usr/lib/vdr/plugins/libvdr-epgsearch.so.1.3.31 Dec 13 11:15:57 linux vdr[18068]: loading plugin: /usr/lib/vdr/plugins/libvdr-dxr3.so.1.3.31 Dec 13 11:15:57 linux vdr[18068]: loading plugin: /usr/lib/vdr/plugins/libvdr-remote.so.1.3.31 Dec 13 11:15:57 linux vdr[18068]: loading plugin: /usr/lib/vdr/plugins/libvdr-femon.so.1.3.31 Dec 13 11:15:57 linux vdr[18068]: loading /var/lib/vdr/setup.conf Dec 13 11:15:57 linux vdr[18068]: loading /var/lib/vdr/sources.conf Dec 13 11:15:57 linux vdr[18068]: loading /var/lib/vdr/diseqc.conf Dec 13 11:15:57 linux vdr[18068]: loading /var/lib/vdr/channels.conf Dec 13 11:15:57 linux vdr[18068]: loading /var/lib/vdr/timers.conf Dec 13 11:15:57 linux vdr[18068]: loading /var/lib/vdr/commands.conf Dec 13 11:15:57 linux vdr[18068]: loading /var/lib/vdr/reccmds.conf Dec 13 11:15:57 linux vdr[18068]: loading /var/lib/vdr/svdrphosts.conf Dec 13 11:15:57 linux vdr[18068]: loading /var/lib/vdr/ca.conf Dec 13 11:15:57 linux vdr[18068]: loading /var/lib/vdr/remote.conf Dec 13 11:15:57 linux vdr[18068]: loading /var/lib/vdr/keymacros.conf Dec 13 11:15:57 linux vdr[18068]: found 1 video device Dec 13 11:15:57 linux vdr[18068]: initializing plugin: sysinfo (0.0.4a): System information plugin Dec 13 11:15:57 linux vdr[18068]: initializing plugin: mp3 (0.9.13): A versatile audio player Dec 13 11:15:57 linux vdr[18068]: loading /var/lib/vdr/plugins/mp3sources.conf Dec 13 11:15:57 linux vdr[18068]: loading id3 cache from /video/id3info.cache Dec 13 11:15:57 linux vdr[18068]: initializing plugin: dvd (0.3.6-b03): turn VDR into an (almost) full featured DVD player Dec 13 11:15:57 linux vdr[18068]: initializing plugin: epgsearch (0.9.7): search the EPG for repeats and more Dec 13 11:15:57 linux vdr[18068]: initializing plugin: dxr3 (0.2.4): Hardware MPEG decoder Dec 13 11:15:58 linux kernel: adv717x.o: Configuring for PAL Dec 13 11:15:58 linux kernel: em8300_audio.o: Analog audio enabled Dec 13 11:15:58 linux kernel: em8300: Microcode version 0x29 loaded Dec 13 11:15:58 linux kernel: adv717x.o: Configuring for PAL Dec 13 11:15:58 linux vdr[18068]: initializing plugin: remote (0.3.3): Remote control Dec 13 11:15:58 linux vdr[18068]: initializing plugin: femon (0.9.1): DVB Signal Information Monitor (OSD) Dec 13 11:15:58 linux vdr[18068]: setting primary device to 2 Dec 13 11:15:58 linux vdr[18068]: SVDRP listening on port 2001 Dec 13 11:15:58 linux vdr[18068]: loading /var/lib/vdr/themes/classic-default.theme Dec 13 11:15:58 linux vdr[18068]: starting plugin: sysinfo Dec 13 11:15:58 linux vdr[18068]: starting plugin: mp3 Dec 13 11:15:58 linux vdr[18068]: starting plugin: dvd Dec 13 11:15:58 linux vdr[18068]: starting plugin: epgsearch Dec 13 11:15:58 linux vdr[18068]: loading /var/lib/vdr/plugins/epgsearch.conf Dec 13 11:15:58 linux vdr[18068]: starting plugin: dxr3 Dec 13 11:15:58 linux vdr[18068]: starting plugin: remote Dec 13 11:15:58 linux vdr[18068]: starting plugin: femon Dec 13 11:15:58 linux vdr[18068]: loading /var/lib/vdr/themes/classic-default.theme Dec 13 11:15:58 linux vdr[18068]: switching to channel 13 Dec 13 11:15:58 linux vdr[18068]: dxr3: Setting digital PCM audio mode Dec 13 11:15:58 linux kernel: em8300_audio.o: Digital PCM audio enabled
André
André Bischof wrote:
Klaus Schmidinger schrieb:
André Bischof wrote:
Hello,
I'm running vdr 1.3.31 with a nova-t and a dxr3. I'm experiencing a lot sync problems, investigating in that problem I had to recognize that vdr builds a lot of subprocesses.
...
Is that normal behaviour or some kind of misconfiguration? If so, how I can I put that right?
Depending on how many DVB devices your system has, this is normal. See the log file for information on what these threads do.
Hello Klaus,
thanks for your immediate answer, but I cannot see anything regarding processes in the logs - maybe I simply look at the wrong place? Or is one vdr-kbd process started for each plugin?
Starting vdr I get (first lines are the error I'm investigating in):
==> /var/log/messages <== Dec 13 09:21:54 linux vdr[15164]: cAudioRepacker: skipped 1117 bytes to sync on next audio frame Dec 13 09:21:54 linux vdr[15164]: cAudioRepacker: skipped 769 bytes to sync on next audio frame Dec 13 09:21:54 linux vdr[15164]: cAudioRepacker: skipped 269 bytes to sync on next audio frame Dec 13 09:21:54 linux vdr[15164]: cAudioRepacker: skipped 1467 bytes while syncing on next audio frame Dec 13 09:21:55 linux vdr[15164]: cAudioRepacker: skipped 1467 bytes while syncing on next audio frame Dec 13 09:21:55 linux vdr[15164]: cAudioRepacker: skipped 504 bytes to sync on next audio frame Dec 13 09:21:55 linux vdr[15164]: cAudioRepacker: skipped 146 bytes to sync on next audio frame ... Dec 13 11:15:56 linux vdr-kbd: deleting plugin: femon Dec 13 11:15:56 linux vdr-kbd: deleting plugin: remote Dec 13 11:15:56 linux vdr-kbd: deleting plugin: dxr3 Dec 13 11:15:56 linux vdr-kbd: deleting plugin: epgsearch Dec 13 11:15:56 linux vdr-kbd: deleting plugin: dvd Dec 13 11:15:56 linux vdr-kbd: deleting plugin: mp3 Dec 13 11:15:56 linux vdr-kbd: deleting plugin: sysinfo Dec 13 11:15:57 linux vdr[18068]: VDR version 1.3.31 started Dec 13 11:15:57 linux vdr[18068]: loading plugin: /usr/lib/vdr/plugins/libvdr-sysinfo.so.1.3.31 Dec 13 11:15:57 linux vdr[18068]: loading plugin: /usr/lib/vdr/plugins/libvdr-mp3.so.1.3.31 Dec 13 11:15:57 linux vdr[18068]: loading plugin: /usr/lib/vdr/plugins/libvdr-dvd.so.1.3.31 Dec 13 11:15:57 linux vdr[18068]: loading plugin: /usr/lib/vdr/plugins/libvdr-epgsearch.so.1.3.31 Dec 13 11:15:57 linux vdr[18068]: loading plugin: /usr/lib/vdr/plugins/libvdr-dxr3.so.1.3.31 Dec 13 11:15:57 linux vdr[18068]: loading plugin: /usr/lib/vdr/plugins/libvdr-remote.so.1.3.31 Dec 13 11:15:57 linux vdr[18068]: loading plugin: /usr/lib/vdr/plugins/libvdr-femon.so.1.3.31 Dec 13 11:15:57 linux vdr[18068]: loading /var/lib/vdr/setup.conf Dec 13 11:15:57 linux vdr[18068]: loading /var/lib/vdr/sources.conf Dec 13 11:15:57 linux vdr[18068]: loading /var/lib/vdr/diseqc.conf Dec 13 11:15:57 linux vdr[18068]: loading /var/lib/vdr/channels.conf Dec 13 11:15:57 linux vdr[18068]: loading /var/lib/vdr/timers.conf Dec 13 11:15:57 linux vdr[18068]: loading /var/lib/vdr/commands.conf Dec 13 11:15:57 linux vdr[18068]: loading /var/lib/vdr/reccmds.conf Dec 13 11:15:57 linux vdr[18068]: loading /var/lib/vdr/svdrphosts.conf Dec 13 11:15:57 linux vdr[18068]: loading /var/lib/vdr/ca.conf Dec 13 11:15:57 linux vdr[18068]: loading /var/lib/vdr/remote.conf Dec 13 11:15:57 linux vdr[18068]: loading /var/lib/vdr/keymacros.conf Dec 13 11:15:57 linux vdr[18068]: found 1 video device Dec 13 11:15:57 linux vdr[18068]: initializing plugin: sysinfo (0.0.4a): System information plugin Dec 13 11:15:57 linux vdr[18068]: initializing plugin: mp3 (0.9.13): A versatile audio player Dec 13 11:15:57 linux vdr[18068]: loading /var/lib/vdr/plugins/mp3sources.conf Dec 13 11:15:57 linux vdr[18068]: loading id3 cache from /video/id3info.cache Dec 13 11:15:57 linux vdr[18068]: initializing plugin: dvd (0.3.6-b03): turn VDR into an (almost) full featured DVD player Dec 13 11:15:57 linux vdr[18068]: initializing plugin: epgsearch (0.9.7): search the EPG for repeats and more Dec 13 11:15:57 linux vdr[18068]: initializing plugin: dxr3 (0.2.4): Hardware MPEG decoder Dec 13 11:15:58 linux kernel: adv717x.o: Configuring for PAL Dec 13 11:15:58 linux kernel: em8300_audio.o: Analog audio enabled Dec 13 11:15:58 linux kernel: em8300: Microcode version 0x29 loaded Dec 13 11:15:58 linux kernel: adv717x.o: Configuring for PAL Dec 13 11:15:58 linux vdr[18068]: initializing plugin: remote (0.3.3): Remote control Dec 13 11:15:58 linux vdr[18068]: initializing plugin: femon (0.9.1): DVB Signal Information Monitor (OSD) Dec 13 11:15:58 linux vdr[18068]: setting primary device to 2 Dec 13 11:15:58 linux vdr[18068]: SVDRP listening on port 2001 Dec 13 11:15:58 linux vdr[18068]: loading /var/lib/vdr/themes/classic-default.theme Dec 13 11:15:58 linux vdr[18068]: starting plugin: sysinfo Dec 13 11:15:58 linux vdr[18068]: starting plugin: mp3 Dec 13 11:15:58 linux vdr[18068]: starting plugin: dvd Dec 13 11:15:58 linux vdr[18068]: starting plugin: epgsearch Dec 13 11:15:58 linux vdr[18068]: loading /var/lib/vdr/plugins/epgsearch.conf Dec 13 11:15:58 linux vdr[18068]: starting plugin: dxr3 Dec 13 11:15:58 linux vdr[18068]: starting plugin: remote Dec 13 11:15:58 linux vdr[18068]: starting plugin: femon Dec 13 11:15:58 linux vdr[18068]: loading /var/lib/vdr/themes/classic-default.theme Dec 13 11:15:58 linux vdr[18068]: switching to channel 13 Dec 13 11:15:58 linux vdr[18068]: dxr3: Setting digital PCM audio mode Dec 13 11:15:58 linux kernel: em8300_audio.o: Digital PCM audio enabled
André
You are either running VDR with a limited log level (option -l), or your syslog setup is spreading the various log messages all over the place. Normally all log messages should go into /var/log/messages.
Klaus
On Tue, 2005-12-13 at 11:18 +0100, Klaus Schmidinger wrote:
You are either running VDR with a limited log level (option -l),
...or your /etc/syslog.conf discards the debug messages (see also the syslog.conf manual page),
or your syslog setup is spreading the various log messages all over the place.
Ville Skyttä schrieb:
On Tue, 2005-12-13 at 11:18 +0100, Klaus Schmidinger wrote:
You are either running VDR with a limited log level (option -l),
...or your /etc/syslog.conf discards the debug messages (see also the syslog.conf manual page),
or your syslog setup is spreading the various log messages all over the place.
thanks, I changed the logbehaviour by modifying /etc/syslog.conf and /etc/init.d/vdr (added -l 3.6 as suggested in thread "Logging", started on 20051202):
startvdr() { ... start-stop-daemon --start --quiet --background \ --exec /usr/sbin/runvdr -- -v $VIDEO_DIR -c $CFG_DIR -r $REC_CMD \ -s $VDRSHUTDOWN -E $EPG_FILE -u $USER -g $GROUP --port $SVDRP_PORT \ $OPTIONS $PLUGINS -l 3.6 else echo -n " - seems to be running already" fi }
# First some standard logfiles. Log by facility. ... local6.* /var/log/vdr.log auth,authpriv.* /var/log/auth.log *.*;auth,authpriv,local6,mail.none -/var/log/syslog
Still some log info shows up in messages, some other shows up in the newly created vdr.log, which shows exactly my problem:
Dec 13 13:38:43 linux vdr[19308]: cAudioRepacker: skipped 6 bytes to sync on next audio frame Dec 13 13:38:43 linux vdr[19308]: cAudioRepacker: skipped 884 bytes while syncing on next audio frame Dec 13 13:38:43 linux vdr[19308]: cAudioRepacker: skipped 107 bytes to sync on next audio frame Dec 13 13:38:43 linux vdr[19308]: cAudioRepacker: skipped 372 bytes to sync on next audio frame Dec 13 13:38:43 linux vdr[19308]: cAudioRepacker: skipped 190 bytes while syncing on next audio frame Dec 13 13:38:43 linux vdr[19308]: cAudioRepacker: skipped 14 bytes while syncing on next audio frame Dec 13 13:39:08 linux vdr[19308]: cAudioRepacker: skipped 4 bytes to sync on next audio frame Dec 13 13:39:08 linux vdr[19308]: cAudioRepacker: skipped 207 bytes to sync on next audio frame Dec 13 13:39:08 linux vdr[19308]: dxr3: audiodecoder: sample rate=48000 Dec 13 13:39:08 linux vdr[19308]: dxr3: audiodecoder: channels=2 Dec 13 13:39:08 linux vdr[19308]: dxr3: audiodecoder: sample rate=32000 Dec 13 13:39:08 linux vdr[19308]: dxr3: audiodecoder: unexpected parameter change Dec 13 13:39:08 linux vdr[19308]: dxr3: audiodecoder: skipping 217 broken data bytes Dec 13 13:39:08 linux vdr[19308]: dxr3: audiodecoder: sample rate=48000 Dec 13 13:39:08 linux vdr[19308]: dxr3: audiodecoder: channels=2 Dec 13 13:39:09 linux vdr[19308]: cAudioRepacker: skipped 245 bytes to sync on next audio frame Dec 13 13:39:09 linux vdr[19308]: cAudioRepacker: skipped 157 bytes while syncing on next audio frame Dec 13 13:39:09 linux vdr[19308]: cAudioRepacker: skipped 1467 bytes while syncing on next audio frame Dec 13 13:39:09 linux vdr[19308]: cAudioRepacker: skipped 449 bytes to sync on next audio frame Dec 13 13:39:09 linux vdr[19308]: cAudioRepacker: skipped 87 bytes to sync on next audio frame Dec 13 13:39:09 linux vdr[19308]: cAudioRepacker: skipped 303 bytes to sync on next audio frame Dec 13 13:39:09 linux vdr[19308]: cAudioRepacker: skipped 207 bytes to sync on next audio frame Dec 13 13:39:09 linux vdr[19308]: dxr3: audiodecoder: sample rate=48000 Dec 13 13:39:09 linux vdr[19308]: dxr3: audiodecoder: channels=2 Dec 13 13:39:10 linux vdr[19308]: cAudioRepacker: skipped 295 bytes to sync on next audio frame
Any clues or workarounds for fixing this?
André
Klaus Schmidinger wrote:
Normally all log messages should go into /var/log/messages.
There is no 'normally' in Linux... ;)
For Debian, /var/log/messages has no debug messages and nothing from error and above, and nothing regarding auth, authpriv, cron, daemon, mail, news. Not much left then. The most complete Debian log is /var/log/syslog.
Cheers,
Udo
Udo Richter wrote:
Klaus Schmidinger wrote:
Normally all log messages should go into /var/log/messages.
There is no 'normally' in Linux... ;)
For Debian, /var/log/messages has no debug messages and nothing from error and above, and nothing regarding auth, authpriv, cron, daemon, mail, news. Not much left then. The most complete Debian log is /var/log/syslog.
Well, whatever. Personally I find it better to have all such messages in one log file (whatever name it may have), because otherwise I'd have to consult several files to see the actual sequence of messages that have been generated.
But if others like to spread all log messages into various files, so be it. The problem in such cases is that before being able to get to the actual problem, there are discussions about where all the log messages might be... ;-)
Klaus