Hello,
from one day to another my vdr (1.3.31) stopped working. It seems to be running fine as nothing appears in the logfiles (started with -l 3 6), but I have no video/sound and top shows a vdr-kbd eating cpu.
I don't know how to track this, maybe I could try something with strace (how?)? Or could I check DVB-functions on hardware level?
In the meantime between running and running I installed some debs, but as far as I know nothing which should interfere with vdr.
Any suggestions what I could do?
Output from logfile and top follows:
Jan 14 12:24:10 linux vdr[13336]: VDR version 1.3.31 started Jan 14 12:24:10 linux vdr[13336]: loading plugin: /usr/lib/vdr/plugins/libvdr-dxr3.so.1.3.31 Jan 14 12:24:10 linux vdr[13336]: loading /var/lib/vdr/setup.conf Jan 14 12:24:10 linux vdr[13336]: loading /var/lib/vdr/sources.conf Jan 14 12:24:10 linux vdr[13336]: loading /var/lib/vdr/diseqc.conf Jan 14 12:24:10 linux vdr[13336]: loading /var/lib/vdr/channels.conf Jan 14 12:24:10 linux vdr[13336]: loading /var/lib/vdr/timers.conf Jan 14 12:24:10 linux vdr[13336]: loading /var/lib/vdr/commands.conf Jan 14 12:24:10 linux vdr[13336]: loading /var/lib/vdr/reccmds.conf Jan 14 12:24:10 linux vdr[13336]: loading /var/lib/vdr/svdrphosts.conf Jan 14 12:24:10 linux vdr[13336]: loading /var/lib/vdr/ca.conf Jan 14 12:24:10 linux vdr[13336]: loading /var/lib/vdr/remote.conf Jan 14 12:24:10 linux vdr[13336]: loading /var/lib/vdr/keymacros.conf Jan 14 12:24:10 linux vdr[13336]: reading EPG data from /var/cache/vdr/epg.data Jan 14 12:24:10 linux vdr[13336]: probing /dev/dvb/adapter0/frontend0 Jan 14 12:24:11 linux vdr[13336]: found 1 video device 2Jan 14 12:24:11 linux vdr[13336]: initializing plugin: dxr3 (0.2.4): Hardware MPEG decoder Jan 14 12:24:11 linux vdr[13339]: tuner on device 1 thread started (pid=13339, tid=16386) Jan 14 12:24:11 linux vdr[13340]: Section handler thread started (pid=13340, tid=32771) Jan 14 12:24:12 linux vdr[13336]: dxr3: configure: video mode: PAL Jan 14 12:24:12 linux vdr[13336]: dxr3: intf: brightness=500,contrast=500,saturation=500 at init Jan 14 12:24:12 linux vdr[13341]: DXR3 audio output thread started (pid=13341, tid=49156) Jan 14 12:24:12 linux vdr[13342]: DXR3 video output thread started (pid=13342, tid=65541) Jan 14 12:24:12 linux vdr[13336]: setting primary device to 2 Jan 14 12:24:12 linux vdr[13336]: SVDRP listening on port 2001 Jan 14 12:24:12 linux vdr[13336]: loading /var/lib/vdr/themes/classic-default.theme Jan 14 12:24:12 linux vdr[13336]: starting plugin: dxr3 Jan 14 12:24:12 linux vdr[13336]: loading /var/lib/vdr/themes/classic-default.theme Jan 14 12:24:12 linux vdr[13336]: ERROR: /dev/lircd: No such file or directory Jan 14 12:24:12 linux vdr[13336]: ERROR: remote control LIRC not ready! Jan 14 12:24:12 linux vdr[13336]: switching to channel 13 Jan 14 12:24:12 linux vdr[13343]: transfer thread started (pid=13343, tid=81926) Jan 14 12:24:12 linux vdr[13344]: receiver on device 1 thread started (pid=13344, tid=98311) Jan 14 12:24:12 linux vdr[13345]: TS buffer on device 1 thread started (pid=13345, tid=114696) Jan 14 12:24:21 linux vdr[13340]: channel 12 (WDR Köln) event 11:00 'Es war eine rauschende Ballnacht' status 4 Jan 14 12:24:21 linux vdr[13340]: channel 15 (MDR Fernsehen) event 11:45 'Mare TV' status 4 Jan 14 12:24:21 linux vdr[13340]: channel 13 (NDR FS NDS) event 11:30 'Verrücktes Wohnen in Mecklenburg-Vorpommern' status 4 Jan 14 12:24:22 linux vdr[13340]: channel 14 (SÜDWEST RP) event 12:00 'DASDING.tv' status 4
top - 12:25:26 up 16:18, 8 users, load average: 1.09, 0.42, 0.16 Tasks: 168 total, 3 running, 165 sleeping, 0 stopped, 0 zombie Cpu(s): 3.9% us, 22.1% sy, 0.1% ni, 0.0% id, 73.6% wa, 0.2% hi, 0.2% si Mem: 906588k total, 897164k used, 9424k free, 178632k buffers Swap: 2088440k total, 124k used, 2088316k free, 154104k cached
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 13336 vdr 18 0 38908 11m 2452 R 22.0 1.4 0:38.74 vdr-kbd
Any help is greatly appreciated! André
Andre Bischof wrote:
Hello,
from one day to another my vdr (1.3.31) stopped working. It seems to be running fine as nothing appears in the logfiles (started with -l 3 6), but I have no video/sound and top shows a vdr-kbd eating cpu.
I don't know how to track this, maybe I could try something with strace (how?)? Or could I check DVB-functions on hardware level?
In the meantime between running and running I installed some debs, but as far as I know nothing which should interfere with vdr.
Any suggestions what I could do?
...
Talking to myself:
I couldn't really track down this error, but I installed almost everything new, thus now running vdr 1.3.38 with only dxr3 and remote plugins. I have it working, with video/audio, but vdr keeps eating alot ressources, more than it took before, see top:
top - 16:01:32 up 22:55, 8 users, load average: 2.86, 2.43, 1.48 Tasks: 192 total, 2 running, 189 sleeping, 0 stopped, 1 zombie Cpu(s): 4.8% us, 58.7% sy, 0.1% ni, 0.0% id, 35.8% wa, 0.1% hi, ^^^^^^^^^^^^^^^^^ 0.5% si Mem: 906588k total, 897272k used, 9316k free, 191060k buffers Swap: 2088440k total, 124k used, 2088316k free, 97000k cached
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 6943 vdr 16 0 45020 16m 2760 S 60.9 1.9 6:57.85 vdr
There's harddisk activity all the time when I start vdr, could it be that this comes from reading my video dir (about 80GB, there is s.th. in the logs saying:
Jan 15 15:50:24 linux vdr[6943]: loading ./keymacros.conf Jan 15 15:50:24 linux vdr[6943]: video directory scanner thread started (pid=6943, tid=6944) Jan 15 15:50:24 linux vdr[6943]: video directory scanner thread started (pid=6943, tid=6945) Jan 15 15:50:24 linux vdr[6943]: reading EPG data from /video/epg.data
I really would like to know what vdr (6943, see top) is doing exactly, but I don't know how - anyone who could give me a hint? If you'd like more information, please let me know.
Thanks in advance for helping, André
Andre Bischof wrote:
... I couldn't really track down this error, but I installed almost everything new, thus now running vdr 1.3.38 with only dxr3 and remote plugins. I have it working, with video/audio, but vdr keeps eating alot ressources, more than it took before, see top:
top - 16:01:32 up 22:55, 8 users, load average: 2.86, 2.43, 1.48 Tasks: 192 total, 2 running, 189 sleeping, 0 stopped, 1 zombie Cpu(s): 4.8% us, 58.7% sy, 0.1% ni, 0.0% id, 35.8% wa, 0.1% hi, ^^^^^^^^^^^^^^^^^ 0.5% si Mem: 906588k total, 897272k used, 9316k free, 191060k buffers Swap: 2088440k total, 124k used, 2088316k free, 97000k cached
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 6943 vdr 16 0 45020 16m 2760 S 60.9 1.9 6:57.85 vdr
There's harddisk activity all the time when I start vdr, could it be that this comes from reading my video dir (about 80GB, there is s.th. in the logs saying:
Jan 15 15:50:24 linux vdr[6943]: loading ./keymacros.conf Jan 15 15:50:24 linux vdr[6943]: video directory scanner thread started (pid=6943, tid=6944) Jan 15 15:50:24 linux vdr[6943]: video directory scanner thread started (pid=6943, tid=6945) Jan 15 15:50:24 linux vdr[6943]: reading EPG data from /video/epg.data
I really would like to know what vdr (6943, see top) is doing exactly, but I don't know how - anyone who could give me a hint? If you'd like more information, please let me know.
You could start by consulting the log file to find out which thread actually eats up the most CPU time.
You can use
ps -T u -C vdr
to find out the thread's SPID and locate the corresponding "thread ... started" line in the log where it says "tid=nnn".
Klaus
Klaus Schmidinger wrote: ...
I really would like to know what vdr (6943, see top) is doing exactly, but I don't know how - anyone who could give me a hint? If you'd like more information, please let me know.
You could start by consulting the log file to find out which thread actually eats up the most CPU time.
You can use
ps -T u -C vdr
to find out the thread's SPID and locate the corresponding "thread ... started" line in the log where it says "tid=nnn".
root@linux:/downloads/vdr/1.3.38/vdr-1.3.38# ps -T u -C vdr USER PID SPID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND vdr 9709 9709 0.7 1.2 34268 11624 ? Ssl 18:34 0:00 ./vdr --config=. --lib=./PLUGINS/lib -d --no-kbd -l 3 6 -p vdr 9709 9710 48.2 1.2 34268 11624 ? Rsl 18:34 0:13 ./vdr --config=. --lib=./PLUGINS/lib -d --no-kbd -l 3 6 -p vdr 9709 9711 48.2 1.2 34268 11624 ? Rsl 18:34 0:13 ./vdr --config=. --lib=./PLUGINS/lib -d --no-kbd -l 3 6 -p vdr 9709 9713 0.0 1.2 34268 11624 ? Ssl 18:34 0:00 ./vdr --config=. --lib=./PLUGINS/lib -d --no-kbd -l 3 6 -p vdr 9709 9714 0.0 1.2 34268 11624 ? SNsl 18:34 0:00 ./vdr --config=. --lib=./PLUGINS/lib -d --no-kbd -l 3 6 -p vdr 9709 9715 0.0 1.2 34268 11624 ? Ssl 18:34 0:00 ./vdr --config=. --lib=./PLUGINS/lib -d --no-kbd -l 3 6 -p vdr 9709 9716 0.0 1.2 34268 11624 ? Ssl 18:34 0:00 ./vdr --config=. --lib=./PLUGINS/lib -d --no-kbd -l 3 6 -p vdr 9709 9717 0.0 1.2 34268 11624 ? Ssl 18:34 0:00 ./vdr --config=. --lib=./PLUGINS/lib -d --no-kbd -l 3 6 -p
so they are two!
Jan 15 18:34:03 linux vdr[9709]: VDR version 1.3.38 started Jan 15 18:34:03 linux vdr[9709]: switched to user 'vdr' Jan 15 18:34:03 linux vdr[9709]: running as daemon (tid=9709) Jan 15 18:34:03 linux vdr[9709]: loading plugin: ./PLUGINS/lib/libvdr-remote.so.1.3.38 Jan 15 18:34:03 linux vdr[9709]: loading plugin: ./PLUGINS/lib/libvdr-dxr3.so.1.3.38 Jan 15 18:34:03 linux vdr[9709]: loading ./sources.conf Jan 15 18:34:03 linux vdr[9709]: loading ./diseqc.conf Jan 15 18:34:03 linux vdr[9709]: loading ./channels.conf Jan 15 18:34:03 linux vdr[9709]: loading ./svdrphosts.conf Jan 15 18:34:03 linux vdr[9709]: loading ./keymacros.conf Jan 15 18:34:03 linux vdr[9709]: reading EPG data from /video/epg.data
searched tids --- Jan 15 18:34:03 linux vdr[9709]: video directory scanner thread started (pid=9709, tid=9710) Jan 15 18:34:03 linux vdr[9709]: video directory scanner thread started (pid=9709, tid=9711) --- searched tids
Jan 15 18:34:03 linux vdr[9709]: probing /dev/dvb/adapter0/frontend0 Jan 15 18:34:04 linux vdr[9709]: found 1 video device Jan 15 18:34:04 linux vdr[9709]: initializing plugin: remote (0.3.4): Remote control Jan 15 18:34:04 linux vdr[9709]: initializing plugin: dxr3 (0.2.5): Hardware MPEG decoder Jan 15 18:34:04 linux vdr[9709]: tuner on device 1 thread started (pid=9709, tid=9713) Jan 15 18:34:04 linux vdr[9709]: section handler thread started (pid=9709, tid=9714) Jan 15 18:34:05 linux vdr[9709]: dxr3: configure: video mode: PAL Jan 15 18:34:05 linux vdr[9709]: dxr3: configure: audio mode: analog Jan 15 18:34:05 linux vdr[9709]: dxr3: intf: brightness=500,contrast=500,saturation=500 at init Jan 15 18:34:05 linux vdr[9709]: setting primary device to 1 Jan 15 18:34:05 linux vdr[9709]: device 1 has no MPEG decoder Jan 15 18:34:05 linux vdr[9709]: trying device number 2 instead Jan 15 18:34:05 linux vdr[9709]: setting primary device to 2 Jan 15 18:34:05 linux vdr[9709]: SVDRP listening on port 2001 Jan 15 18:34:05 linux vdr[9709]: loading ./themes/sttng-default.theme Jan 15 18:34:05 linux vdr[9709]: starting plugin: remote Jan 15 18:34:05 linux vdr[9709]: device /dev/input/event4: Budget-CI dvb ir receiver saa7146 (0) Jan 15 18:34:05 linux vdr[9709]: remote: using '/dev/input/event4' Jan 15 18:34:05 linux vdr[9709]: remote-event4: exclusive access granted Jan 15 18:34:05 linux vdr[9709]: starting plugin: dxr3 Jan 15 18:34:05 linux vdr[9709]: loading ./themes/sttng-default.theme Jan 15 18:34:05 linux vdr[9709]: remote control remote-event4 - learning keys Jan 15 18:34:05 linux vdr[9709]: dxr3: cSPUEncoder::Flush: OSD data size: 8741 Jan 15 18:34:05 linux vdr[9709]: device /dev/input/event4: Budget-CI dvb ir receiver saa7146 (0) Jan 15 18:34:05 linux vdr[9709]: DXR3 video output thread started (pid=9709, tid=9716) Jan 15 18:34:05 linux vdr[9709]: DXR3 audio output thread started (pid=9709, tid=9715) Jan 15 18:34:08 linux vdr[9709]: dxr3: cSPUEncoder::Flush: OSD data size: 8546
Now that they are identified, what should I do next?
I can't see s.th. wrong with /video: root@linux:/# la /video/ total 20287988 drwxrwxr-x 17 vdr users 4096 Jan 15 17:21 . drwxr-xr-x 27 root root 4096 Jan 14 15:19 .. drwxr-xr-x 3 vdr users 4096 Dec 9 20:18 Der_200-Jahre-Mann
/video belongs vdr, as do _old_ recordings. The menue for recordings does not show my old recordings.
BTW for the moment I start vdr from within my compile-dir vdr-1.3.38 with: root@linux:/downloads/vdr/1.3.38/vdr-1.3.38# ./vdr --config=. --lib=./PLUGINS/lib -d --no-kbd -l 3.6 -p 2001 --video=/video -w 60-u vdr -g vdr -P remote -P dxr3
thus the video-dir should be right?
Do you have any guesses what my problem could be? What does the "video directory scanner thread" do?
Kind regards, and thanks so far, André
Andre Bischof wrote:
Klaus Schmidinger wrote: ...
I really would like to know what vdr (6943, see top) is doing exactly, but I don't know how - anyone who could give me a hint? If you'd like more information, please let me know.
You could start by consulting the log file to find out which thread actually eats up the most CPU time.
You can use
ps -T u -C vdr
to find out the thread's SPID and locate the corresponding "thread ... started" line in the log where it says "tid=nnn".
root@linux:/downloads/vdr/1.3.38/vdr-1.3.38# ps -T u -C vdr USER PID SPID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND vdr 9709 9709 0.7 1.2 34268 11624 ? Ssl 18:34 0:00 ./vdr --config=. --lib=./PLUGINS/lib -d --no-kbd -l 3 6 -p vdr 9709 9710 48.2 1.2 34268 11624 ? Rsl 18:34 0:13 ./vdr --config=. --lib=./PLUGINS/lib -d --no-kbd -l 3 6 -p vdr 9709 9711 48.2 1.2 34268 11624 ? Rsl 18:34 0:13 ./vdr --config=. --lib=./PLUGINS/lib -d --no-kbd -l 3 6 -p vdr 9709 9713 0.0 1.2 34268 11624 ? Ssl 18:34 0:00 ./vdr --config=. --lib=./PLUGINS/lib -d --no-kbd -l 3 6 -p vdr 9709 9714 0.0 1.2 34268 11624 ? SNsl 18:34 0:00 ./vdr --config=. --lib=./PLUGINS/lib -d --no-kbd -l 3 6 -p vdr 9709 9715 0.0 1.2 34268 11624 ? Ssl 18:34 0:00 ./vdr --config=. --lib=./PLUGINS/lib -d --no-kbd -l 3 6 -p vdr 9709 9716 0.0 1.2 34268 11624 ? Ssl 18:34 0:00 ./vdr --config=. --lib=./PLUGINS/lib -d --no-kbd -l 3 6 -p vdr 9709 9717 0.0 1.2 34268 11624 ? Ssl 18:34 0:00 ./vdr --config=. --lib=./PLUGINS/lib -d --no-kbd -l 3 6 -p
so they are two!
Jan 15 18:34:03 linux vdr[9709]: VDR version 1.3.38 started Jan 15 18:34:03 linux vdr[9709]: switched to user 'vdr' Jan 15 18:34:03 linux vdr[9709]: running as daemon (tid=9709) Jan 15 18:34:03 linux vdr[9709]: loading plugin: ./PLUGINS/lib/libvdr-remote.so.1.3.38 Jan 15 18:34:03 linux vdr[9709]: loading plugin: ./PLUGINS/lib/libvdr-dxr3.so.1.3.38 Jan 15 18:34:03 linux vdr[9709]: loading ./sources.conf Jan 15 18:34:03 linux vdr[9709]: loading ./diseqc.conf Jan 15 18:34:03 linux vdr[9709]: loading ./channels.conf Jan 15 18:34:03 linux vdr[9709]: loading ./svdrphosts.conf Jan 15 18:34:03 linux vdr[9709]: loading ./keymacros.conf Jan 15 18:34:03 linux vdr[9709]: reading EPG data from /video/epg.data
searched tids --- Jan 15 18:34:03 linux vdr[9709]: video directory scanner thread started (pid=9709, tid=9710) Jan 15 18:34:03 linux vdr[9709]: video directory scanner thread started (pid=9709, tid=9711) --- searched tids
Jan 15 18:34:03 linux vdr[9709]: probing /dev/dvb/adapter0/frontend0 Jan 15 18:34:04 linux vdr[9709]: found 1 video device Jan 15 18:34:04 linux vdr[9709]: initializing plugin: remote (0.3.4): Remote control Jan 15 18:34:04 linux vdr[9709]: initializing plugin: dxr3 (0.2.5): Hardware MPEG decoder Jan 15 18:34:04 linux vdr[9709]: tuner on device 1 thread started (pid=9709, tid=9713) Jan 15 18:34:04 linux vdr[9709]: section handler thread started (pid=9709, tid=9714) Jan 15 18:34:05 linux vdr[9709]: dxr3: configure: video mode: PAL Jan 15 18:34:05 linux vdr[9709]: dxr3: configure: audio mode: analog Jan 15 18:34:05 linux vdr[9709]: dxr3: intf: brightness=500,contrast=500,saturation=500 at init Jan 15 18:34:05 linux vdr[9709]: setting primary device to 1 Jan 15 18:34:05 linux vdr[9709]: device 1 has no MPEG decoder Jan 15 18:34:05 linux vdr[9709]: trying device number 2 instead Jan 15 18:34:05 linux vdr[9709]: setting primary device to 2 Jan 15 18:34:05 linux vdr[9709]: SVDRP listening on port 2001 Jan 15 18:34:05 linux vdr[9709]: loading ./themes/sttng-default.theme Jan 15 18:34:05 linux vdr[9709]: starting plugin: remote Jan 15 18:34:05 linux vdr[9709]: device /dev/input/event4: Budget-CI dvb ir receiver saa7146 (0) Jan 15 18:34:05 linux vdr[9709]: remote: using '/dev/input/event4' Jan 15 18:34:05 linux vdr[9709]: remote-event4: exclusive access granted Jan 15 18:34:05 linux vdr[9709]: starting plugin: dxr3 Jan 15 18:34:05 linux vdr[9709]: loading ./themes/sttng-default.theme Jan 15 18:34:05 linux vdr[9709]: remote control remote-event4 - learning keys Jan 15 18:34:05 linux vdr[9709]: dxr3: cSPUEncoder::Flush: OSD data size: 8741 Jan 15 18:34:05 linux vdr[9709]: device /dev/input/event4: Budget-CI dvb ir receiver saa7146 (0) Jan 15 18:34:05 linux vdr[9709]: DXR3 video output thread started (pid=9709, tid=9716) Jan 15 18:34:05 linux vdr[9709]: DXR3 audio output thread started (pid=9709, tid=9715) Jan 15 18:34:08 linux vdr[9709]: dxr3: cSPUEncoder::Flush: OSD data size: 8546
Now that they are identified, what should I do next?
I can't see s.th. wrong with /video: root@linux:/# la /video/ total 20287988 drwxrwxr-x 17 vdr users 4096 Jan 15 17:21 . drwxr-xr-x 27 root root 4096 Jan 14 15:19 .. drwxr-xr-x 3 vdr users 4096 Dec 9 20:18 Der_200-Jahre-Mann
What's inside "Der_200-Jahre-Mann"? Any non-VDR subdirectories?
/video belongs vdr, as do _old_ recordings. The menue for recordings does not show my old recordings.
Where are those _old_ recordings?
BTW for the moment I start vdr from within my compile-dir vdr-1.3.38 with: root@linux:/downloads/vdr/1.3.38/vdr-1.3.38# ./vdr --config=. --lib=./PLUGINS/lib -d --no-kbd -l 3.6 -p 2001 --video=/video -w 60-u vdr -g vdr -P remote -P dxr3
There's a blank mitting between 60 and -u. Also, the GRAB directory (option -g) must be a full path name.
thus the video-dir should be right?
Do you have any guesses what my problem could be? What does the "video directory scanner thread" do?
Well, it scans the video directory ;-)
Are you sure that there is no other data in your video directory that might cause VDR to do unnecessary work?
Klaus
Andre Bischof wrote: ...
searched tids --- Jan 15 18:34:03 linux vdr[9709]: video directory scanner thread started (pid=9709, tid=9710) Jan 15 18:34:03 linux vdr[9709]: video directory scanner thread started (pid=9709, tid=9711) --- searched tids
Jan 15 18:34:03 linux vdr[9709]: probing /dev/dvb/adapter0/frontend0 Jan 15 18:34:04 linux vdr[9709]: found 1 video device
I now did an strace on them:
strace -ff -F -o vdr-strace.txt ./vdr --config=. --lib=./PLUGINS/lib -d --no-kbd -l 3.6 -p 2001 --video=/video -w 60 -u vdr -g vdr -P remote -P dxr3
the pids output shows some ENOENTs (file not found), which doesn't seem to disturb vdr, as video/audio are there:
open("/dev/dvb/adapter0/osd0", O_RDWR) = -1 ENOENT (No such file or directory) open("/dev/dvb/adapter0/video0", O_RDWR|O_NONBLOCK) = -1 ENOENT (No such file or directory) open("/dev/dvb/adapter0/audio0", O_RDWR|O_NONBLOCK) = -1 ENOENT (No such file or directory) open("/dev/dvb/adapter0/demux0", O_RDWR) = 13 open("/proc/video/dev/video0", O_RDONLY) = -1 ENOENT (No such file or directory) ioctl(4, 0x80a86f3d, 0xbfaa893c) = 0 open("/dev/dvb/adapter0/ca0", O_RDWR) = -1 ENOENT (No such file or directory)
the tids output shows alot entries like this one:
stat64("/video/14/etc/ssl/certs/ff783690.0", 0x40dffafc) = -1 ENOENT (No such file or directory)
which comes because a moved a backup copy temporarly to my video dir (space problems). This dir is quite big ~26GB, maybe this is the problem?
Could it be that every file is scanned in /video to build the record list?
Ahrg, right at this very moment I read your reply, so moving unnecessary files from /video should do it.
I also didn't know that -g means grab directory, I thought u and g were user and group :(
Thanks for helping Klaus, I appreciate it much! Kind regards, André
Andre Bischof wrote:
Andre Bischof wrote: ...
searched tids --- Jan 15 18:34:03 linux vdr[9709]: video directory scanner thread started (pid=9709, tid=9710) Jan 15 18:34:03 linux vdr[9709]: video directory scanner thread started (pid=9709, tid=9711) --- searched tids
Jan 15 18:34:03 linux vdr[9709]: probing /dev/dvb/adapter0/frontend0 Jan 15 18:34:04 linux vdr[9709]: found 1 video device
I now did an strace on them:
strace -ff -F -o vdr-strace.txt ./vdr --config=. --lib=./PLUGINS/lib -d --no-kbd -l 3.6 -p 2001 --video=/video -w 60 -u vdr -g vdr -P remote -P dxr3
the pids output shows some ENOENTs (file not found), which doesn't seem to disturb vdr, as video/audio are there:
open("/dev/dvb/adapter0/osd0", O_RDWR) = -1 ENOENT (No such file or directory) open("/dev/dvb/adapter0/video0", O_RDWR|O_NONBLOCK) = -1 ENOENT (No such file or directory) open("/dev/dvb/adapter0/audio0", O_RDWR|O_NONBLOCK) = -1 ENOENT (No such file or directory) open("/dev/dvb/adapter0/demux0", O_RDWR) = 13 open("/proc/video/dev/video0", O_RDONLY) = -1 ENOENT (No such file or directory) ioctl(4, 0x80a86f3d, 0xbfaa893c) = 0 open("/dev/dvb/adapter0/ca0", O_RDWR) = -1 ENOENT (No such file or directory)
the tids output shows alot entries like this one:
stat64("/video/14/etc/ssl/certs/ff783690.0", 0x40dffafc) = -1 ENOENT (No such file or directory)
which comes because a moved a backup copy temporarly to my video dir (space problems). This dir is quite big ~26GB, maybe this is the problem?
Could it be that every file is scanned in /video to build the record list?
Ahrg, right at this very moment I read your reply, so moving unnecessary files from /video should do it.
From VDR's INSTALL file:
Note that you should not copy any non-VDR files into the /videoX directories, since this might cause the watchdog timer to expire when VDR cleans up those directories and there is a large number of files and/or subdirectories in there.
I also didn't know that -g means grab directory, I thought u and g were user and group :(
Well, it may have been "group" with some patch, but since I believe -u to set the user should be enough (why wouod you need to set an extra group?) and I had already implemented the -g option for the GRAB directory, this is how it is now.
Klaus
Klaus Schmidinger wrote: ...
Ahrg, right at this very moment I read your reply, so moving unnecessary files from /video should do it.
From VDR's INSTALL file:
Note that you should not copy any non-VDR files into the /videoX directories, since this might cause the watchdog timer to expire when VDR cleans up those directories and there is a large number of files and/or subdirectories in there.
Shame on me :( - sometime reading _does_ help!
I also didn't know that -g means grab directory, I thought u and g were user and group :(
Well, it may have been "group" with some patch, but since I believe -u to set the user should be enough (why wouod you need to set an extra group?) and I had already implemented the -g option for the GRAB directory, this is how it is now.
Didn't want to make that a feature request, for me -u is enough - but I believe to remember programs where both could be set, and as you know I don't read enough, you know why I thought instead of knowing ;-)
Anyway, great software Klaus, keep on going!
André
-
Andre Bischof -
Klaus Schmidinger