[vdr] Re: vdr died just after start

[Stefan Lucke <stefan@lucke.in-berlin.de>]

On Friday 02 May 2003 12:20, Klaus Schmidinger wrote:
> Stefan Lucke wrote:
> > On Friday 02 May 2003 11:30, Klaus Schmidinger wrote:
> > > Stefan Lucke wrote:
> > > > Hi,
> > > >
> > > > could someone please explain what went wrong?
> >
> > [ .. ]
> >
> > > > 20:13:00 farpoint vdr[734]: recording thread started (pid=734) Mai  1
> > > > 20:13:00 farpoint vdr[735]: receiver thread started on device 1
> > > > (pid=735) Mai  1 20:13:31 farpoint vdr[735]: ERROR: video data stream
> > > > broken on device 1
> > >
> > > Fr some reason there was no data delivered from the DVB card.
> > > This is what the "emergency exit" is for - it reloads the driver
> > > and restarts VDR.
> > >
> > > Did the recording work after the restart?
> >
> > No. vdr was started via command line (my fault) and not via inittab.
> >   ./vdr -d -v /data/video/ -Pstreamdev
> > Today I restarted vdr without reloading DVB driver and it looks well.
> > There is some strange behaviour with EPG data too. After deletion of
> > "epg.data" there was no program info available for hours (epg.data size
> > less than 1000 bytes). Programm info appeared just after a timer
> > recording started.
>
> Maybe there was no transpoder tuned to in the beginning?
> What happens if you manually change the channel? Do you get EPG data
> from that transponder then?
No. I tried it again (stop vdr;rm epg.data;start vdr [on my server]
start vdr on client site with:
 ./vdr -Pdxr3 -Pstreamdev  -c /net_data/vdr_bodega1/ -v /net_data/video/
did several channel switches but there is no program info up to now.

-rw-r--r--    1 stefan   sysprog      1413 Apr 27 15:31 ca.conf
-rw-r--r--    1 stefan   sysprog      8771 Apr 27 15:31 channels.conf
-rw-r--r--    1 stefan   sysprog      2026 Apr 27 15:31 diseqc.conf
-rw-r--r--    1 stefan   users          86 Mai  2 13:04 epg.data
-rw-r--r--    1 stefan   sysprog       195 Apr 27 15:31 keymacros.conf
-rw-r--r--    1 stefan   sysprog      1184 Apr 29 19:58 remote.conf

SERVER LOG:
Mai  2 12:53:05 farpoint vdr[3736]: VDR version 1.1.29 started
Mai  2 12:53:05 farpoint vdr[3736]: loading plugin: ./PLUGINS/lib/libvdr-streamdev.so.1.1.29
Mai  2 12:53:05 farpoint vdr[3736]: loading /data/video/setup.conf
Mai  2 12:53:05 farpoint vdr[3736]: loading /data/video/sources.conf
Mai  2 12:53:05 farpoint vdr[3736]: loading /data/video/diseqc.conf
Mai  2 12:53:05 farpoint vdr[3736]: loading /data/video/channels.conf
Mai  2 12:53:05 farpoint vdr[3736]: loading /data/video/timers.conf
Mai  2 12:53:05 farpoint vdr[3736]: loading /data/video/svdrphosts.conf
Mai  2 12:53:05 farpoint vdr[3736]: loading /data/video/ca.conf
Mai  2 12:53:05 farpoint vdr[3736]: loading /data/video/remote.conf
Mai  2 12:53:05 farpoint vdr[3736]: loading /data/video/keymacros.conf
Mai  2 12:53:05 farpoint vdr[3736]: probing /dev/dvb/adapter0/frontend0
Mai  2 12:53:05 farpoint vdr[3739]: EIT processing thread started (pid=3739) - master
Mai  2 12:53:06 farpoint vdr[3740]: tuner thread started on device 1 (pid=3740)
Mai  2 12:53:06 farpoint vdr[3736]: probing /dev/dvb/adapter1/frontend0
Mai  2 12:53:06 farpoint vdr[3736]: found 1 video device
Mai  2 12:53:06 farpoint vdr[3736]: starting plugin: streamdev (0.0.1a): VTP Streaming Server and Client
Mai  2 12:53:06 farpoint vdr[3741]: Streamdevice Server thread started (pid = 3741)
Mai  2 12:53:06 farpoint vdr[3741]: Streamdevice: Listening on 0.0.0.0:2004
Mai  2 12:53:06 farpoint vdr[3736]: setting primary device to 1
Mai  2 12:53:06 farpoint vdr[3736]: device 1 has no MPEG decoder
Mai  2 12:53:06 farpoint vdr[3736]: SVDRP listening on port 2001
Mai  2 12:53:06 farpoint vdr[3736]: ERROR: /dev/lircd: Datei oder Verzeichnis nicht gefunden
Mai  2 12:53:06 farpoint vdr[3736]: ERROR: remote control LIRC not ready!
Mai  2 12:53:06 farpoint vdr[3736]: switching to channel 1
Mai  2 12:54:17 farpoint vdr[3741]: Streamdevice: Accepted new client 192.168.192.129:32783
Mai  2 12:54:17 farpoint vdr[3741]: Streamdev: Setting data connection to 192.168.192.129:0
Mai  2 12:54:17 farpoint vdr[3745]: Streamdev: Transceiver thread started (pid=3745)
Mai  2 12:54:17 farpoint vdr[3746]: receiver thread started on device 1 (pid=3746)
Mai  2 12:55:06 farpoint vdr[3745]: Streamdev: Transceiver thread ended
Mai  2 12:55:06 farpoint vdr[3746]: receiver thread ended on device 1 (pid=3746)
Mai  2 12:55:06 farpoint vdr[3741]: cTS2PES got 0 TS errors, 2 TS continuity errors
Mai  2 12:55:06 farpoint vdr[3741]: cTS2PES got 0 TS errors, 4 TS continuity errors
Mai  2 12:55:06 farpoint vdr[3741]: buffer stats: 30456 (2%) used
Mai  2 12:55:06 farpoint vdr[3741]: Streamdev: Setting data connection to 192.168.192.129:0
Mai  2 12:55:06 farpoint vdr[3747]: Streamdev: Transceiver thread started (pid=3747)
Mai  2 12:55:06 farpoint vdr[3748]: receiver thread started on device 1 (pid=3748)
Mai  2 12:55:14 farpoint vdr[3747]: Streamdev: Transceiver thread ended
Mai  2 12:55:14 farpoint vdr[3748]: receiver thread ended on device 1 (pid=3748)
Mai  2 12:55:14 farpoint vdr[3741]: cTS2PES got 0 TS errors, 1 TS continuity errors
Mai  2 12:55:14 farpoint vdr[3741]: cTS2PES got 0 TS errors, 1 TS continuity errors
Mai  2 12:55:14 farpoint vdr[3741]: buffer stats: 16544 (1%) used
Mai  2 12:55:14 farpoint vdr[3741]: Streamdev: Setting data connection to 192.168.192.129:0
Mai  2 12:55:14 farpoint vdr[3749]: Streamdev: Transceiver thread started (pid=3749)
Mai  2 12:55:14 farpoint vdr[3750]: receiver thread started on device 1 (pid=3750)

-- 

mfg

  Stefan Lucke (stefan@lucke.in-berlin.de)


-- 
Info:
To unsubscribe send a mail to ecartis@linuxtv.org with "unsubscribe vdr" as subject.