Hi,
on sunday, I have found a weird behaviour that I never had before and which seems to be a bug concerning SVDRP.
Every sunday, nvram wakes up my VDR for recording "Lindenstraße" and turns it off automatically after the recording - as long as I don´t press any key on the remote.
The same situation was this sunday: The "Lindenstraße" recording started short before 18:50. While the recording was running (and I did NOT touch the VDR), I added another timer for a broadcast starting at 19:00 ("Unser Charly") with VDRAdmin (-> SVDRP). This recording also started successfully. Few minutes later, I stopped the recording of "Lindenstraße", because we could watch it live, and deleted the recording with VDRAdmin. The recording of "Unser Charly" was still running. Then, I changed the end time of the timer of "Unser Charly" with VDRAdmin while it was recording. After doing this, the VDR immediately shut down instead of continuing recording the broadcast until the changed end time.
Don´t know the code but if on a timer change the timer is first deleted and then set again, it might be clear why VDR thought that it can shut down - as long as no key has been pressed.
With kind regards
Joerg
Joerg Knitter wrote:
Don´t know the code but if on a timer change the timer is first deleted and then set again, it might be clear why VDR thought that it can shut down - as long as no key has been pressed.
BTW: I use VDR 1.3.23 and VDRAdmin-0.97-am2.x (going to upgrade to am3.x soon). Of course, this could also be a VDRAdmin bug, but as I am sure that some core functions have not been changed for years, I think this is more VDR related.
Jörg
On Tue, 12 Apr 2005, Joerg Knitter (JK) wrote:
JK> Joerg Knitter wrote: JK> > Don´t know the code but if on a timer change the timer is first deleted JK> > and then set again, it might be clear why VDR thought that it can shut JK> > down - as long as no key has been pressed. JK>
I think, that the vdr log is needed to analyse this.
c ya Sergei
Sergei Haller schrieb:
On Tue, 12 Apr 2005, Joerg Knitter (JK) wrote:
JK> Joerg Knitter wrote: JK> > Don´t know the code but if on a timer change the timer is first deleted JK> > and then set again, it might be clear why VDR thought that it can shut JK> > down - as long as no key has been pressed. JK>
I think, that the vdr log is needed to analyse this.
c ya Sergei
Gonna post this this evening/tomorrow and check if it was not something different causing the PC to shut down. But as the second timer, that was recording, really existet and I did not delete it, I think it´s indeed a bug.
Nevertheless, you are still able to reproduce this: - Set a timer within the next 15 minutes and turn the PC off - Let the PC boot and record the timer - Program a new timer, let the new timer start - Delete the old (running) timer - Change the end time of the new timer.
Jörg
Sergei Haller wrote:
JK> > Don´t know the code but if on a timer change the timer is first deleted JK> > and then set again, it might be clear why VDR thought that it can shut JK> > down - as long as no key has been pressed.
I think, that the vdr log is needed to analyse this.
This is the complete log - sorry for this big post. I hope you can see anything in it. Look at 'timer 18' - it is simply stopped, but I think the log does not clearly say what has been modified, just that the timer has been modified:
Apr 10 18:40:00 linux vdr[4653]: switching device 2 to channel 1 Apr 10 18:40:00 linux vdr[4653]: timer 3 (1 1840-1935 'Lindenstraße~Lindenstraße~1010. Beweise') start Apr 10 18:40:00 linux vdr[4653]: Title: 'Lindenstraße' Subtitle: '1010. Beweise' Apr 10 18:40:00 linux vdr[4653]: record /video0/Lindenstraße/Lindenstraße/1010._Beweise/2005-04-10.18.40.99.99.rec Apr 10 18:40:00 linux vdr[4653]: creating directory /video0/Lindenstraße Apr 10 18:40:00 linux vdr[4653]: creating directory /video0/Lindenstraße/Lindenstraße Apr 10 18:40:00 linux vdr[4653]: creating directory /video0/Lindenstraße/Lindenstraße/1010._Beweise Apr 10 18:40:00 linux vdr[4653]: creating directory /video0/Lindenstraße/Lindenstraße/1010._Beweise/2005-04-10.18.40.99.99.rec Apr 10 18:40:00 linux vdr[4653]: recording to '/video0/Lindenstraße/Lindenstraße/1010._Beweise/2005-04-10.18.40.99.99.rec/001.vdr' Apr 10 18:40:00 linux vdr[4653]: creating directory /video1/Lindenstraße Apr 10 18:40:00 linux vdr[4653]: creating directory /video1/Lindenstraße/Lindenstraße Apr 10 18:40:00 linux vdr[4653]: creating directory /video1/Lindenstraße/Lindenstraße/1010._Beweise Apr 10 18:40:00 linux vdr[4653]: creating directory /video1/Lindenstraße/Lindenstraße/1010._Beweise/2005-04-10.18.40.99.99.rec Apr 10 18:40:00 linux vdr[4747]: file writer thread started (pid=4747, tid=262155) Apr 10 18:40:00 linux vdr[4748]: recording thread started (pid=4748, tid=278540) Apr 10 18:40:00 linux vdr[4749]: receiver on device 2 thread started (pid=4749, tid=294925) Apr 10 18:40:00 linux vdr[4750]: TS buffer on device 2 thread started (pid=4750, tid=311310) Apr 10 18:57:05 linux vdr[4653]: connect from 127.0.0.1, port 32773 - accepted Apr 10 18:57:05 linux vdr[4653]: timer 18 (15 1858-1950 'Unser Charly') added Apr 10 18:57:06 linux vdr[4653]: closing SVDRP connection Apr 10 18:58:00 linux vdr[4653]: switching device 1 to channel 15 Apr 10 18:58:00 linux vdr[4653]: timer 18 (15 1858-1950 'Unser Charly') start Apr 10 18:58:00 linux vdr[4653]: Title: 'Unser Charly' Subtitle: 'Schneegänse' Apr 10 18:58:00 linux vdr[4653]: record /video0/Unser_Charly/2005-04-10.18.58.50.07.rec Apr 10 18:58:00 linux vdr[4653]: creating directory /video0/Unser_Charly Apr 10 18:58:00 linux vdr[4653]: creating directory /video0/Unser_Charly/2005-04-10.18.58.50.07.rec Apr 10 18:58:00 linux vdr[4653]: recording to '/video0/Unser_Charly/2005-04-10.18.58.50.07.rec/001.vdr' Apr 10 18:58:00 linux vdr[4653]: creating directory /video1/Unser_Charly Apr 10 18:58:00 linux vdr[4653]: creating directory /video1/Unser_Charly/2005-04-10.18.58.50.07.rec Apr 10 18:58:00 linux vdr[4771]: file writer thread started (pid=4771, tid=327695) Apr 10 18:58:00 linux vdr[4772]: recording thread started (pid=4772, tid=344080) Apr 10 18:58:00 linux vdr[4773]: receiver on device 1 thread started (pid=4773, tid=360465) Apr 10 18:58:00 linux vdr[4774]: TS buffer on device 1 thread started (pid=4774, tid=376850) Apr 10 18:58:01 linux vdr[4653]: switching to channel 1 Apr 10 18:58:01 linux vdr[4775]: transfer thread started (pid=4775, tid=393235) Apr 10 18:58:05 linux vdr[4653]: timer 18 (15 1858-1950 'Unser Charly') set to event Son 10.04.2005 19:00-19:45 (VPS: 10.04 19:00) 'Unser Charly' Apr 10 18:58:17 linux vdr[4653]: connect from 127.0.0.1, port 32774 - accepted Apr 10 18:58:19 linux vdr[4653]: closing SVDRP connection Apr 10 18:58:24 linux vdr[4653]: connect from 127.0.0.1, port 32775 - accepted Apr 10 18:58:26 linux vdr[4653]: closing SVDRP connection Apr 10 18:58:34 linux vdr[4653]: connect from 127.0.0.1, port 32776 - accepted Apr 10 18:58:34 linux vdr[4653]: timer 18 (15 1858-1948 'Unser Charly') modified (active) Apr 10 18:58:34 linux vdr[4772]: recording thread ended (pid=4772, tid=344080) Apr 10 18:58:34 linux vdr[4774]: TS buffer on device 1 thread ended (pid=4774, tid=376850) Apr 10 18:58:34 linux vdr[4773]: buffer stats: 49256 (2%) used Apr 10 18:58:34 linux vdr[4773]: receiver on device 1 thread ended (pid=4773, tid=360465) Apr 10 18:58:34 linux vdr[4771]: file writer thread ended (pid=4771, tid=327695) Apr 10 18:58:34 linux vdr[4653]: buffer stats: 49632 (0%) used Apr 10 18:58:34 linux vdr[4653]: timer 18 (15 1858-1948 'Unser Charly') stop Apr 10 18:58:34 linux vdr[4653]: closing SVDRP connection Apr 10 18:58:34 linux vdr[4653]: connect from 127.0.0.1, port 32777 - accepted Apr 10 18:58:36 linux vdr[4653]: closing SVDRP connection Apr 10 18:58:52 linux vdr[4653]: connect from 127.0.0.1, port 32778 - accepted Apr 10 18:58:55 linux vdr[4653]: closing SVDRP connection Apr 10 18:58:59 linux vdr[4653]: connect from 127.0.0.1, port 32779 - accepted Apr 10 18:59:01 linux vdr[4653]: closing SVDRP connection Apr 10 18:59:09 linux vdr[4653]: connect from 127.0.0.1, port 32780 - accepted Apr 10 18:59:09 linux vdr[4653]: timer 3 (1 1840-1935 'Lindenstraße~Lindenstraße~1010. Beweise') modified (inactive) Apr 10 18:59:09 linux vdr[4748]: recording thread ended (pid=4748, tid=278540) Apr 10 18:59:09 linux vdr[4747]: file writer thread ended (pid=4747, tid=262155) Apr 10 18:59:09 linux vdr[4653]: buffer stats: 105280 (2%) used Apr 10 18:59:09 linux vdr[4653]: timer 3 (1 1840-1935 'Lindenstraße~Lindenstraße~1010. Beweise') stop Apr 10 18:59:09 linux vdr[4653]: closing SVDRP connection Apr 10 18:59:09 linux vdr[4653]: next timer event at Sun Apr 10 20:11:00 2005 Apr 10 18:59:09 linux vdr[4653]: confirm: Taste drücken um Shutdown abzubrechen Apr 10 18:59:09 linux vdr[4653]: connect from 127.0.0.1, port 32781 - accepted Apr 10 18:59:11 linux vdr[4653]: closing SVDRP connection Apr 10 18:59:14 linux vdr[4653]: connect from 127.0.0.1, port 32782 - accepted Apr 10 18:59:17 linux vdr[4653]: closing SVDRP connection Apr 10 18:59:22 linux vdr[4653]: connect from 127.0.0.1, port 32783 - accepted Apr 10 18:59:22 linux vdr[4653]: closing SVDRP connection Apr 10 18:59:27 linux vdr[4653]: connect from 127.0.0.1, port 32784 - accepted Apr 10 18:59:27 linux vdr[4653]: deleting recording /video0/Lindenstraße/Lindenstraße/1010._Beweise/2005-04-10.18.40.99.99.rec Apr 10 18:59:27 linux vdr[4653]: closing SVDRP connection Apr 10 18:59:28 linux vdr[4653]: connect from 127.0.0.1, port 32785 - accepted Apr 10 18:59:28 linux vdr[4653]: closing SVDRP connection Apr 10 18:59:37 linux vdr[4653]: connect from 127.0.0.1, port 32786 - accepted Apr 10 18:59:37 linux vdr[4653]: closing SVDRP connection Apr 10 18:59:41 linux vdr[4653]: connect from 127.0.0.1, port 32787 - accepted Apr 10 18:59:41 linux vdr[4653]: closing SVDRP connection Apr 10 18:59:42 linux vdr[4653]: connect from 127.0.0.1, port 32788 - accepted Apr 10 18:59:43 linux vdr[4653]: closing SVDRP connection Apr 10 19:04:10 linux vdr[4653]: confirmed Apr 10 19:04:10 linux vdr[4653]: executing '/usr/local/src/VDRtmp/scripts/vdrshutdown 1113156660 4010 172 "Men in Black II" 0'
Joerg
Joerg Knitter wrote:
This is the complete log - sorry for this big post. I hope you can see anything in it. Look at 'timer 18' - it is simply stopped, but I think the log does not clearly say what has been modified, just that the timer has been modified:
These are imho the important lines of the log file:
18:40:00 timer 3 (1 1840-1935 'Lindenstraße') start 18:57:05 timer 18 (15 1858-1950 'Unser Charly') added 18:58:00 timer 18 (15 1858-1950 'Unser Charly') start 18:58:34 connect from 127.0.0.1, port 32776 - accepted 18:58:34 timer 18 (15 1858-1948 'Unser Charly') modified (active) 18:58:34 timer 18 (15 1858-1948 'Unser Charly') stop 18:58:34 closing SVDRP connection 18:59:09 timer 3 (1 1840-1935 'Lindenstraße') modified (inactive) 18:59:09 timer 3 (1 1840-1935 'Lindenstraße') stop
Timer 18 started at 18:57 as planned, and at 18:58:34, a local SVDRP connect modified the timer again, setting the end time from 1950 to 1948. Since VDR stopped the timer and did not restart it again, it may be set to a later starting date, otherwise VDR would have re-started it soon. The final shutdown happened at 19:04, 5 minutes after the last timer stopped.
I've tried to reproduce this on my machine, but my totally outdated vdradmin cannot handle one-day timers in the new VDR 1.3.23 format and picks a wrong day-of-month when reading the timer via SVDRP. This kills the timer when saved via vdradmin just like yours above. Maybe thats what happened to your timer too?
Cheers,
Udo
Udo Richter schrieb:
Joerg Knitter wrote:
These are imho the important lines of the log file:
18:40:00 timer 3 (1 1840-1935 'Lindenstraße') start 18:57:05 timer 18 (15 1858-1950 'Unser Charly') added 18:58:00 timer 18 (15 1858-1950 'Unser Charly') start 18:58:34 connect from 127.0.0.1, port 32776 - accepted 18:58:34 timer 18 (15 1858-1948 'Unser Charly') modified (active) 18:58:34 timer 18 (15 1858-1948 'Unser Charly') stop 18:58:34 closing SVDRP connection 18:59:09 timer 3 (1 1840-1935 'Lindenstraße') modified (inactive) 18:59:09 timer 3 (1 1840-1935 'Lindenstraße') stop
I've tried to reproduce this on my machine, but my totally outdated vdradmin cannot handle one-day timers in the new VDR 1.3.23 format and picks a wrong day-of-month when reading the timer via SVDRP. This kills the timer when saved via vdradmin just like yours above. Maybe thats what happened to your timer too?
AFAIK, the latest 2.x-Version of vdradmin-0.97-am that I use supports the 1.3.23 timers (haven´t had any problems so far). So IMHO vdradmin is not be the problem here.
With kind regards
Joerg
-
Joerg Knitter -
Sergei Haller -
Udo Richter