Hello,
I'm using vdr for a few years now and last weekend I upgraded to version 1.4.0.
When vdr is running awhile and now starts a recording, it exits. On the other hand when the recording starts immediately after booting my system everything is fine.
In the log file is a little difference between the two cases. In the first case the cam module is already loaded, when the recording starts. In the second case the recording starts before my cam module is loaded.
My configuration: Ubuntu 5.10, one dvb device (fujitsu siemens dvb-c ff) with a cam - vdr primary device, another dvb device (hauppauge dvb-c ff) without a cam.
Perhaps someone out there has a solution for my problem.
Thanks to all contributors for the great work.
Greetings Berni
Bernhard Wager wrote:
Hello,
I'm using vdr for a few years now and last weekend I upgraded to version 1.4.0.
When vdr is running awhile and now starts a recording, it exits. On the other hand when the recording starts immediately after booting my system everything is fine.
In the log file is a little difference between the two cases. In the first case the cam module is already loaded, when the recording starts. In the second case the recording starts before my cam module is loaded.
My configuration: Ubuntu 5.10, one dvb device (fujitsu siemens dvb-c ff) with a cam - vdr primary device, another dvb device (hauppauge dvb-c ff) without a cam.
At startup VDR is supposed to wait until all devices (and their CAM modules, if any) are ready. Are you getting any log messages like "not all devices ready after 30 seconds"?
Klaus
Klaus Schmidinger wrote:
I'm using vdr for a few years now and last weekend I upgraded to version 1.4.0.
When vdr is running awhile and now starts a recording, it exits. On the other hand when the recording starts immediately after booting my system everything is fine.
In the log file is a little difference between the two cases. In the first case the cam module is already loaded, when the recording starts. In the second case the recording starts before my cam module is loaded.
My configuration: Ubuntu 5.10, one dvb device (fujitsu siemens dvb-c ff) with a cam - vdr primary device, another dvb device (hauppauge dvb-c ff) without a cam.
At startup VDR is supposed to wait until all devices (and their CAM modules, if any) are ready. Are you getting any log messages like "not all devices ready after 30 seconds"?
I couldn't something like this :-(
The log looks like thes for the first case:
May 8 18:22:53 localhost vdr: [8930] VDR version 1.4.0 started May 8 18:22:53 localhost vdr: [8930] loading plugin: VDR/PLUGINS/lib/libvdr-dvd.so.1.4.0 May 8 18:22:53 localhost vdr: [8930] loading /root/vdr.conf/setup.conf May 8 18:22:53 localhost vdr: [8930] loading /root/vdr.conf/sources.conf May 8 18:22:53 localhost vdr: [8930] loading /root/vdr.conf/diseqc.conf May 8 18:22:53 localhost vdr: [8930] loading /root/vdr.conf/channels.conf May 8 18:22:53 localhost vdr: [8930] loading /root/vdr.conf/timers.conf May 8 18:22:53 localhost vdr: [8930] loading /root/vdr.conf/svdrphosts.conf May 8 18:22:53 localhost vdr: [8930] loading /root/vdr.conf/remote.conf May 8 18:22:53 localhost vdr: [8930] loading /root/vdr.conf/keymacros.conf May 8 18:22:58 localhost vdr: [8930] found 2 video devices May 8 18:22:58 localhost vdr: [8930] initializing plugin: dvd (0.3.6-b03): turn VDR into an (almost) full featured DVD playe r May 8 18:22:58 localhost vdr: [8930] setting primary device to 2 May 8 18:22:58 localhost vdr: [8930] SVDRP listening on port 2001 May 8 18:22:58 localhost vdr: [8930] loading /root/vdr.conf/themes/sttng-default.theme May 8 18:22:58 localhost vdr: [8930] starting plugin: dvd May 8 18:22:58 localhost vdr: [8930] loading /root/vdr.conf/themes/sttng-default.theme May 8 18:23:02 localhost vdr: [8930] CAM: AlphaCrypt Light, 01, 4A20, 4A20 May 8 18:23:02 localhost vdr: [8930] switching to channel 1 [...] May 8 20:49:12 localhost vdr: [8934] frontend 0 lost lock on channel 0, tp 522 May 8 20:49:14 localhost vdr: [8934] frontend 0 timed out while tuning to channel 0, tp 522 May 8 20:49:32 localhost vdr: [8934] frontend 0 regained lock on channel 106, tp 113 May 8 20:50:15 localhost vdr: [8934] frontend 0 lost lock on channel 0, tp 338 May 8 20:50:17 localhost vdr: [8934] frontend 0 timed out while tuning to channel 0, tp 338 May 8 20:51:00 localhost vdr: [8930] editing timer 1 (11 2055-2245 'Tatort: Tödlicher Galopp') May 8 20:51:05 localhost vdr: [8930] timer 1 (11 2052-2245 'Tatort: Tödlicher Galopp') set to event Mon 08.05.2006 21:00-22: 30 (VPS: 08.05 21:00) 'Tatort: Tödlicher Galopp' May 8 20:51:05 localhost vdr: [8930] timer 1 (11 2052-2245 'Tatort: Tödlicher Galopp') modified (active) May 8 20:51:20 localhost vdr: [8934] frontend 0 timed out while tuning to channel 0, tp 338 May 8 20:51:55 localhost vdr: [8934] frontend 0 regained lock on channel 0, tp 338 May 8 20:51:56 localhost vdr: [8934] frontend 0 lost lock on channel 0, tp 338 May 8 20:51:58 localhost vdr: [8934] frontend 0 timed out while tuning to channel 0, tp 338 May 8 20:52:00 localhost vdr: [8930] timer 1 (11 2052-2245 'Tatort: Tödlicher Galopp') start May 8 20:52:00 localhost vdr: [8930] record /media/video/Tatort:_Tödlicher_Galopp/2006-05-08.20.52.99.99.rec May 8 20:52:01 localhost vdr: [8934] frontend 0 regained lock on channel 11, tp 426 May 8 20:52:11 localhost vdr: [8930] stopping plugin: dvd May 8 20:52:12 localhost vdr: [8930] timer 1 (11 2052-2245 'Tatort: Tödlicher Galopp') stop May 8 20:52:12 localhost vdr: [8930] saved setup to /root/vdr.conf/setup.conf May 8 20:52:12 localhost vdr: [8930] deleting plugin: dvd May 8 20:52:12 localhost vdr: [8930] exiting
... and so for the second case:
May 8 20:56:44 localhost vdr: [7574] VDR version 1.4.0 started May 8 20:56:44 localhost vdr: [7574] loading plugin: VDR/PLUGINS/lib/libvdr-dvd.so.1.4.0 May 8 20:56:44 localhost vdr: [7574] loading /root/vdr.conf/setup.conf May 8 20:56:44 localhost vdr: [7574] loading /root/vdr.conf/sources.conf May 8 20:56:44 localhost vdr: [7574] loading /root/vdr.conf/diseqc.conf May 8 20:56:44 localhost vdr: [7574] loading /root/vdr.conf/channels.conf May 8 20:56:44 localhost vdr: [7574] loading /root/vdr.conf/timers.conf May 8 20:56:44 localhost vdr: [7574] loading /root/vdr.conf/svdrphosts.conf May 8 20:56:44 localhost vdr: [7574] loading /root/vdr.conf/remote.conf May 8 20:56:44 localhost vdr: [7574] loading /root/vdr.conf/keymacros.conf May 8 20:56:50 localhost vdr: [7574] found 2 video devices May 8 20:56:50 localhost vdr: [7574] initializing plugin: dvd (0.3.6-b03): turn VDR into an (almost) full featured DVD playe r May 8 20:56:50 localhost vdr: [7574] setting primary device to 2 May 8 20:56:50 localhost vdr: [7574] SVDRP listening on port 2001 May 8 20:56:50 localhost vdr: [7574] loading /root/vdr.conf/themes/sttng-default.theme May 8 20:56:50 localhost vdr: [7574] starting plugin: dvd May 8 20:56:50 localhost vdr: [7574] loading /root/vdr.conf/themes/sttng-default.theme May 8 20:56:50 localhost vdr: [7574] switching to channel 1 May 8 20:56:50 localhost vdr: [7574] timer 1 (11 2052-2245 'Tatort: Tödlicher Galopp') set to event Mon 08.05.2006 21:00-22: 30 (VPS: 08.05 21:00) 'Tatort: Tödlicher Galopp' May 8 20:56:50 localhost vdr: [7574] timer 1 (11 2052-2245 'Tatort: Tödlicher Galopp') start May 8 20:56:50 localhost vdr: [7574] record /media/video/Tatort:_Tödlicher_Galopp/2006-05-08.20.52.99.99.rec May 8 20:56:51 localhost vdr: [7582] channel 8 (WDR Köln) event Mon 08.05.2006 20:15-21:00 (VPS: 08.05 20:15) 'Der Große Ges undheits-Check' status 4 May 8 20:56:51 localhost vdr: [7582] channel 10 (hr-fernsehen) event Mon 08.05.2006 20:15-21:00 (VPS: 08.05 20:15) 'Südameri kas Ameisenbären' status 4 May 8 20:56:51 localhost vdr: [7579] channel 13 (MDR FERNSEHEN) event Mon 08.05.2006 20:15-21:45 (VPS: 08.05 20:15) 'Das Tra umhotel - Zauber von Bali' status 4 May 8 20:56:52 localhost vdr: [7579] channel 184 (rbb Brandenburg) event Mon 08.05.2006 20:15-21:00 (VPS: 08.05 20:15) 'WAS! ' status 4 May 8 20:56:52 localhost vdr: [7582] channel 9 (SÜDWEST Ferns. BW) event Mon 08.05.2006 20:15-21:45 (VPS: 08.05 20:15) 'Die Schokoladenkönigin' status 4 May 8 20:56:52 localhost vdr: [7582] channel 1 (Das Erste) event Mon 08.05.2006 20:15-21:00 (VPS: 08.05 20:15) 'Die Kommissa rin' status 4 May 8 20:56:52 localhost vdr: [7579] channel 11 (NDR FS MV) event Mon 08.05.2006 20:15-21:00 (VPS: 08.05 20:15) 'markt' stat us 4 May 8 20:56:52 localhost vdr: [7579] channel 18 (EinsFestival) event Mon 08.05.2006 20:15-21:00 (VPS: 08.05 20:15) 'Friedric h Jahn' status 4 May 8 20:57:16 localhost vdr: [7581] CAM: AlphaCrypt Light, 01, 4A20, 4A20
Berni
Bernhard Wager wrote:
Klaus Schmidinger wrote:
I'm using vdr for a few years now and last weekend I upgraded to version 1.4.0.
When vdr is running awhile and now starts a recording, it exits. On the other hand when the recording starts immediately after booting my system everything is fine.
In the log file is a little difference between the two cases. In the first case the cam module is already loaded, when the recording starts. In the second case the recording starts before my cam module is loaded.
My configuration: Ubuntu 5.10, one dvb device (fujitsu siemens dvb-c ff) with a cam - vdr primary device, another dvb device (hauppauge dvb-c ff) without a cam.
At startup VDR is supposed to wait until all devices (and their CAM modules, if any) are ready. Are you getting any log messages like "not all devices ready after 30 seconds"?
I couldn't something like this :-(
The log looks like thes for the first case:
May 8 18:22:53 localhost vdr: [8930] VDR version 1.4.0 started May 8 18:22:53 localhost vdr: [8930] loading plugin: VDR/PLUGINS/lib/libvdr-dvd.so.1.4.0 May 8 18:22:53 localhost vdr: [8930] loading /root/vdr.conf/setup.conf May 8 18:22:53 localhost vdr: [8930] loading /root/vdr.conf/sources.conf May 8 18:22:53 localhost vdr: [8930] loading /root/vdr.conf/diseqc.conf May 8 18:22:53 localhost vdr: [8930] loading /root/vdr.conf/channels.conf May 8 18:22:53 localhost vdr: [8930] loading /root/vdr.conf/timers.conf May 8 18:22:53 localhost vdr: [8930] loading /root/vdr.conf/svdrphosts.conf May 8 18:22:53 localhost vdr: [8930] loading /root/vdr.conf/remote.conf May 8 18:22:53 localhost vdr: [8930] loading /root/vdr.conf/keymacros.conf May 8 18:22:58 localhost vdr: [8930] found 2 video devices May 8 18:22:58 localhost vdr: [8930] initializing plugin: dvd (0.3.6-b03): turn VDR into an (almost) full featured DVD playe r May 8 18:22:58 localhost vdr: [8930] setting primary device to 2 May 8 18:22:58 localhost vdr: [8930] SVDRP listening on port 2001 May 8 18:22:58 localhost vdr: [8930] loading /root/vdr.conf/themes/sttng-default.theme May 8 18:22:58 localhost vdr: [8930] starting plugin: dvd May 8 18:22:58 localhost vdr: [8930] loading /root/vdr.conf/themes/sttng-default.theme May 8 18:23:02 localhost vdr: [8930] CAM: AlphaCrypt Light, 01, 4A20, 4A20 May 8 18:23:02 localhost vdr: [8930] switching to channel 1 [...] May 8 20:49:12 localhost vdr: [8934] frontend 0 lost lock on channel 0, tp 522 May 8 20:49:14 localhost vdr: [8934] frontend 0 timed out while tuning to channel 0, tp 522 May 8 20:49:32 localhost vdr: [8934] frontend 0 regained lock on channel 106, tp 113 May 8 20:50:15 localhost vdr: [8934] frontend 0 lost lock on channel 0, tp 338 May 8 20:50:17 localhost vdr: [8934] frontend 0 timed out while tuning to channel 0, tp 338
Well, maybe there's a problem with your sat cable or your multiswitch (if any). Apparently there is a problem with the signal.
May 8 20:51:00 localhost vdr: [8930] editing timer 1 (11 2055-2245 'Tatort: Tödlicher Galopp') May 8 20:51:05 localhost vdr: [8930] timer 1 (11 2052-2245 'Tatort: Tödlicher Galopp') set to event Mon 08.05.2006 21:00-22: 30 (VPS: 08.05 21:00) 'Tatort: Tödlicher Galopp' May 8 20:51:05 localhost vdr: [8930] timer 1 (11 2052-2245 'Tatort: Tödlicher Galopp') modified (active) May 8 20:51:20 localhost vdr: [8934] frontend 0 timed out while tuning to channel 0, tp 338 May 8 20:51:55 localhost vdr: [8934] frontend 0 regained lock on channel 0, tp 338 May 8 20:51:56 localhost vdr: [8934] frontend 0 lost lock on channel 0, tp 338 May 8 20:51:58 localhost vdr: [8934] frontend 0 timed out while tuning to channel 0, tp 338 May 8 20:52:00 localhost vdr: [8930] timer 1 (11 2052-2245 'Tatort: Tödlicher Galopp') start May 8 20:52:00 localhost vdr: [8930] record /media/video/Tatort:_Tödlicher_Galopp/2006-05-08.20.52.99.99.rec May 8 20:52:01 localhost vdr: [8934] frontend 0 regained lock on channel 11, tp 426 May 8 20:52:11 localhost vdr: [8930] stopping plugin: dvd May 8 20:52:12 localhost vdr: [8930] timer 1 (11 2052-2245 'Tatort: Tödlicher Galopp') stop May 8 20:52:12 localhost vdr: [8930] saved setup to /root/vdr.conf/setup.conf May 8 20:52:12 localhost vdr: [8930] deleting plugin: dvd May 8 20:52:12 localhost vdr: [8930] exiting
From this log I can't see any real reason for the exit. Are you sure you have run VDR with maximum logging (-l3 or default), and that all your log messages go into *one* file?
... and so for the second case:
May 8 20:56:44 localhost vdr: [7574] VDR version 1.4.0 started May 8 20:56:44 localhost vdr: [7574] loading plugin: VDR/PLUGINS/lib/libvdr-dvd.so.1.4.0 May 8 20:56:44 localhost vdr: [7574] loading /root/vdr.conf/setup.conf May 8 20:56:44 localhost vdr: [7574] loading /root/vdr.conf/sources.conf May 8 20:56:44 localhost vdr: [7574] loading /root/vdr.conf/diseqc.conf May 8 20:56:44 localhost vdr: [7574] loading /root/vdr.conf/channels.conf May 8 20:56:44 localhost vdr: [7574] loading /root/vdr.conf/timers.conf May 8 20:56:44 localhost vdr: [7574] loading /root/vdr.conf/svdrphosts.conf May 8 20:56:44 localhost vdr: [7574] loading /root/vdr.conf/remote.conf May 8 20:56:44 localhost vdr: [7574] loading /root/vdr.conf/keymacros.conf May 8 20:56:50 localhost vdr: [7574] found 2 video devices May 8 20:56:50 localhost vdr: [7574] initializing plugin: dvd (0.3.6-b03): turn VDR into an (almost) full featured DVD playe r May 8 20:56:50 localhost vdr: [7574] setting primary device to 2 May 8 20:56:50 localhost vdr: [7574] SVDRP listening on port 2001 May 8 20:56:50 localhost vdr: [7574] loading /root/vdr.conf/themes/sttng-default.theme May 8 20:56:50 localhost vdr: [7574] starting plugin: dvd May 8 20:56:50 localhost vdr: [7574] loading /root/vdr.conf/themes/sttng-default.theme May 8 20:56:50 localhost vdr: [7574] switching to channel 1 May 8 20:56:50 localhost vdr: [7574] timer 1 (11 2052-2245 'Tatort: Tödlicher Galopp') set to event Mon 08.05.2006 21:00-22: 30 (VPS: 08.05 21:00) 'Tatort: Tödlicher Galopp' May 8 20:56:50 localhost vdr: [7574] timer 1 (11 2052-2245 'Tatort: Tödlicher Galopp') start May 8 20:56:50 localhost vdr: [7574] record /media/video/Tatort:_Tödlicher_Galopp/2006-05-08.20.52.99.99.rec May 8 20:56:51 localhost vdr: [7582] channel 8 (WDR Köln) event Mon 08.05.2006 20:15-21:00 (VPS: 08.05 20:15) 'Der Große Ges undheits-Check' status 4 May 8 20:56:51 localhost vdr: [7582] channel 10 (hr-fernsehen) event Mon 08.05.2006 20:15-21:00 (VPS: 08.05 20:15) 'Südameri kas Ameisenbären' status 4 May 8 20:56:51 localhost vdr: [7579] channel 13 (MDR FERNSEHEN) event Mon 08.05.2006 20:15-21:45 (VPS: 08.05 20:15) 'Das Tra umhotel - Zauber von Bali' status 4 May 8 20:56:52 localhost vdr: [7579] channel 184 (rbb Brandenburg) event Mon 08.05.2006 20:15-21:00 (VPS: 08.05 20:15) 'WAS! ' status 4 May 8 20:56:52 localhost vdr: [7582] channel 9 (SÜDWEST Ferns. BW) event Mon 08.05.2006 20:15-21:45 (VPS: 08.05 20:15) 'Die Schokoladenkönigin' status 4 May 8 20:56:52 localhost vdr: [7582] channel 1 (Das Erste) event Mon 08.05.2006 20:15-21:00 (VPS: 08.05 20:15) 'Die Kommissa rin' status 4 May 8 20:56:52 localhost vdr: [7579] channel 11 (NDR FS MV) event Mon 08.05.2006 20:15-21:00 (VPS: 08.05 20:15) 'markt' stat us 4 May 8 20:56:52 localhost vdr: [7579] channel 18 (EinsFestival) event Mon 08.05.2006 20:15-21:00 (VPS: 08.05 20:15) 'Friedric h Jahn' status 4 May 8 20:57:16 localhost vdr: [7581] CAM: AlphaCrypt Light, 01, 4A20, 4A20
No frontend problems here, so maybe the signal problem is actually what's causing this.
Klaus
Klaus Schmidinger wrote:
May 8 20:49:12 localhost vdr: [8934] frontend 0 lost lock on channel 0, tp 522 May 8 20:49:14 localhost vdr: [8934] frontend 0 timed out while tuning to channel 0, tp 522 May 8 20:49:32 localhost vdr: [8934] frontend 0 regained lock on channel 106, tp 113 May 8 20:50:15 localhost vdr: [8934] frontend 0 lost lock on channel 0, tp 338 May 8 20:50:17 localhost vdr: [8934] frontend 0 timed out while tuning to channel 0, tp 338
Well, maybe there's a problem with your sat cable or your multiswitch (if any). Apparently there is a problem with the signal.
This is DVB-C, so no multiswitch. And since all critical messages are channel 0, this seems to be the usual transponder scan messages for empty transponders.
Cheers,
Udo
Udo Richter wrote:
Klaus Schmidinger wrote:
May 8 20:49:12 localhost vdr: [8934] frontend 0 lost lock on channel 0, tp 522 May 8 20:49:14 localhost vdr: [8934] frontend 0 timed out while tuning to channel 0, tp 522 May 8 20:49:32 localhost vdr: [8934] frontend 0 regained lock on channel 106, tp 113 May 8 20:50:15 localhost vdr: [8934] frontend 0 lost lock on channel 0, tp 338 May 8 20:50:17 localhost vdr: [8934] frontend 0 timed out while tuning to channel 0, tp 338
Well, maybe there's a problem with your sat cable or your multiswitch (if any). Apparently there is a problem with the signal.
This is DVB-C, so no multiswitch. And since all critical messages are channel 0, this seems to be the usual transponder scan messages for empty transponders.
Well, then I'm afraid I don't know why this happened...
Maybe the missing log info would help.
Klaus
-
Bernhard Wager -
Klaus Schmidinger -
Udo Richter