[SOLVED] yaVDR 0.5 auto shutdown?

jbjbjb · October 25, 2012 at 9:06 AM

Hi.

My recently installed yaVDR 0.5 has in the morning an odd behavior.

I have ACPI automatic wake up at 6:20, and two hours afterwards yaVDR 0.5 shutdown by it-self, like if someone pressed the power button (but no one does that).

I have configured yaVDR to keep always awake by mean the config menu "osd/7.System/2.Setup/8.Miscelanea/Minimum time of inactivity (m) = 0" . At least this config worked in previous versions.

But two hours after awake at 6:20, yaVDR shutdowns again (I have checked syslog, awaking it by mean wakeonlan from outside home). This is the syslog:

Code

Oct 25 08:21:00 yaVDR05 vdr: [1461] dbus2vdr: new message, object /Shutdown, interface de.tvdr.vdr.shutdown, member ConfirmShutdown
Oct 25 08:21:00 yaVDR05 vdr: [1461] dbus2vdr: 1 idle message handler, reusing 0x7f80582ae0e0
Oct 25 08:21:00 yaVDR05 vdr: [2407] dbus2vdr message handler thread started (pid=1118, tid=2407)
Oct 25 08:21:01 yaVDR05 vdr: [2407] dbus2vdr: calling shutdown-hook-wrapper /usr/share/vdr-plugin-dbus2vdr/shutdown-wrapper /usr/share/vdr/shutdown-hooks "1351196100 50040 3 \"El B$
Oct 25 08:21:01 yaVDR05 shutdown-wrapper: [2408] dbus2vdr-shutdown-wrapper: asking shutdown-hook /bin/sh /usr/share/vdr/shutdown-hooks/S90.acpiwakeup
Oct 25 08:21:01 yaVDR05 vdr-addon-acpiwakeup: Setting ACPI alarm time to: 2012-10-25 20:10:00
Oct 25 08:21:01 yaVDR05 vdr-addon-acpiwakeup: Writing to /sys/class/rtc/rtc0/wakealarm
Oct 25 08:21:01 yaVDR05 vdr-addon-acpiwakeup: Writing to /sys/class/rtc/rtc0/wakealarm
Oct 25 08:21:01 yaVDR05 shutdown-wrapper: [2408] dbus2vdr-shutdown-wrapper: result(0) = (null)
Oct 25 08:21:01 yaVDR05 shutdown-wrapper: [2408] dbus2vdr-shutdown-wrapper: asking shutdown-hook /bin/sh /usr/share/vdr/shutdown-hooks/S90.custom
Oct 25 08:21:01 yaVDR05 shutdown-wrapper: [2408] dbus2vdr-shutdown-wrapper: result(0) = (null)
Oct 25 08:21:01 yaVDR05 shutdown-wrapper: [2408] dbus2vdr-shutdown-wrapper: asking shutdown-hook /bin/sh /usr/share/vdr/shutdown-hooks/S90.nvram-wakeup
Oct 25 08:21:01 yaVDR05 vdr-nvram-wakeup: nvram-wakeup functionality is disabled
Oct 25 08:21:01 yaVDR05 shutdown-wrapper: [2408] dbus2vdr-shutdown-wrapper: result(0) = (null)
Oct 25 08:21:01 yaVDR05 shutdown-wrapper: [2408] dbus2vdr-shutdown-wrapper: asking shutdown-hook /bin/sh /usr/share/vdr/shutdown-hooks/S91.lifeguard
Oct 25 08:21:01 yaVDR05 shutdown-wrapper: [2408] dbus2vdr-shutdown-wrapper: result(0) = (null)
Oct 25 08:21:01 yaVDR05 shutdown-wrapper: [2408] dbus2vdr-shutdown-wrapper: asking shutdown-hook /usr/share/vdr/shutdown-hooks/S99.shutdown
Oct 25 08:21:01 yaVDR05 shutdown-wrapper: [2408] dbus2vdr-shutdown-wrapper: result(0) = SHUTDOWNCMD="stop vdr ; /sbin/halt -p"
Oct 25 08:21:01 yaVDR05 vdr: [2407] dbus2vdr: result(0) = SHUTDOWNCMD="stop vdr ; /sbin/halt -p"
Oct 25 08:21:01 yaVDR05 vdr: [2407] dbus2vdr: moving message handler 0x7f80582ae0e0 from active to finished
Oct 25 08:21:01 yaVDR05 vdr: [2407] dbus2vdr message handler thread ended (pid=1118, tid=2407)
Oct 25 08:21:01 yaVDR05 vdr: [1461] dbus2vdr: connection has messages to send, flushing
Oct 25 08:21:01 yaVDR05 vdr: [1461] dbus2vdr: done flushing
Oct 25 08:21:01 yaVDR05 vdr: [1461] dbus2vdr: new message, object /Remote, interface de.tvdr.vdr.remote, member Enable
Oct 25 08:21:01 yaVDR05 vdr: [1461] dbus2vdr: 1 idle message handler, reusing 0x7f80582ae0e0
Oct 25 08:21:01 yaVDR05 vdr: [2466] dbus2vdr message handler thread started (pid=1118, tid=2466)
Oct 25 08:21:01 yaVDR05 vdr: [2466] dbus2vdr: moving message handler 0x7f80582ae0e0 from active to finished
Oct 25 08:21:01 yaVDR05 vdr: [2466] dbus2vdr message handler thread ended (pid=1118, tid=2466)
Oct 25 08:21:01 yaVDR05 vdr: [1461] dbus2vdr: connection has messages to send, flushing
Oct 25 08:21:01 yaVDR05 vdr: [1461] dbus2vdr: done flushing
Oct 25 08:21:01 yaVDR05 vdr: [1461] dbus2vdr: new message, object /Remote, interface de.tvdr.vdr.remote, member HitKey
Oct 25 08:21:01 yaVDR05 vdr: [1461] dbus2vdr: 1 idle message handler, reusing 0x7f80582ae0e0
Oct 25 08:21:01 yaVDR05 vdr: [2467] dbus2vdr message handler thread started (pid=1118, tid=2467)
Oct 25 08:21:01 yaVDR05 vdr: [2467] dbus2vdr: de.tvdr.vdr.remote.HitKey: get key 'POWER'
Oct 25 08:21:01 yaVDR05 vdr: [1118] Power button pressed
Oct 25 08:21:01 yaVDR05 vdr: [2467] dbus2vdr: moving message handler 0x7f80582ae0e0 from active to finished
Oct 25 08:21:01 yaVDR05 vdr: [2467] dbus2vdr message handler thread ended (pid=1118, tid=2467)
Oct 25 08:21:01 yaVDR05 vdr: [1461] dbus2vdr: connection has messages to send, flushing
Oct 25 08:21:01 yaVDR05 vdr: [1461] dbus2vdr: done flushing
Oct 25 08:21:01 yaVDR05 vdr: [1461] dbus2vdr: new message, object /Remote, interface de.tvdr.vdr.remote, member Disable
Oct 25 08:21:01 yaVDR05 vdr: [1461] dbus2vdr: 1 idle message handler, reusing 0x7f80582ae0e0
Oct 25 08:21:01 yaVDR05 vdr: [2468] dbus2vdr message handler thread started (pid=1118, tid=2468)
Oct 25 08:21:01 yaVDR05 vdr: [2468] dbus2vdr: moving message handler 0x7f80582ae0e0 from active to finished
Oct 25 08:21:01 yaVDR05 vdr: [2468] dbus2vdr message handler thread ended (pid=1118, tid=2468)
Oct 25 08:21:01 yaVDR05 vdr: [1461] dbus2vdr: connection has messages to send, flushing
Oct 25 08:21:01 yaVDR05 vdr: [1461] dbus2vdr: done flushing
Oct 25 08:21:01 yaVDR05 vdr: [1118] confirm: Pulse una tecla para interrumpir apagar
Oct 25 08:21:01 yaVDR05 vdr: [1118] warning: Pulse una tecla para interrumpir apagar
Oct 25 08:21:01 yaVDR05 vdr: [2469] Text2Skin: message display update thread started (pid=1118, tid=2469)
Oct 25 08:21:07 yaVDR05 vdr: [2469] Text2Skin: message display update thread ended (pid=1118, tid=2469)
Oct 25 08:21:07 yaVDR05 vdr: [1118] next timer event at Thu Oct 25 22:15:00 2012
Oct 25 08:21:07 yaVDR05 vdr: [1118] executing '/usr/lib/vdr/vdr-shutdown.wrapper 1351196100 50033 3 "El Barco~El Barco" 1'
Oct 25 08:21:07 yaVDR05 vdr: [1118] saved setup to /var/lib/vdr/setup.conf
Oct 25 08:21:08 yaVDR05 vdr-shutdown: executing /usr/share/vdr/shutdown-hooks/S90.acpiwakeup as shell script
Oct 25 08:21:08 yaVDR05 vdr-addon-acpiwakeup: Setting ACPI alarm time to: 2012-10-25 20:10:00
Oct 25 08:21:08 yaVDR05 vdr-addon-acpiwakeup: Writing to /sys/class/rtc/rtc0/wakealarm
Oct 25 08:21:08 yaVDR05 vdr-addon-acpiwakeup: Writing to /sys/class/rtc/rtc0/wakealarm
Oct 25 08:21:08 yaVDR05 vdr-shutdown: executing /usr/share/vdr/shutdown-hooks/S90.custom as shell script
Oct 25 08:21:08 yaVDR05 vdr-shutdown: executing /usr/share/vdr/shutdown-hooks/S90.nvram-wakeup as shell script
Oct 25 08:21:08 yaVDR05 vdr-nvram-wakeup: nvram-wakeup functionality is disabled
Oct 25 08:21:08 yaVDR05 vdr-shutdown: executing /usr/share/vdr/shutdown-hooks/S91.lifeguard as shell script
Oct 25 08:21:08 yaVDR05 vdr-shutdown: executing /usr/share/vdr/shutdown-hooks/S99.shutdown
Oct 25 08:21:08 yaVDR05 kernel: [ 7545.884233] init: vdr-frontend main process (1480) killed by TERM signal
Oct 25 08:21:08 yaVDR05 vdr: [1461] dbus2vdr: new message, object /Plugins/softhddevice, interface de.tvdr.vdr.plugin, member SVDRPCommand
Oct 25 08:21:08 yaVDR05 vdr: [1461] dbus2vdr: 1 idle message handler, reusing 0x7f80582ae0e0
Oct 25 08:21:08 yaVDR05 vdr: [2550] dbus2vdr message handler thread started (pid=1118, tid=2550)
Oct 25 08:21:08 yaVDR05 vdr: [2550] dbus2vdr: de.tvdr.vdr.plugin.SVDRPCommand: command 'STAT' has no option
Oct 25 08:21:08 yaVDR05 vdr: [2550] dbus2vdr: invoking softhddevice.SVDRPCommand("STAT", "")
Oct 25 08:21:08 yaVDR05 vdr: [2550] dbus2vdr: moving message handler 0x7f80582ae0e0 from active to finished
Oct 25 08:21:08 yaVDR05 vdr: [2550] dbus2vdr message handler thread ended (pid=1118, tid=2550)
Oct 25 08:21:08 yaVDR05 vdr: [1461] dbus2vdr: connection has messages to send, flushing
Oct 25 08:21:08 yaVDR05 vdr: [1461] dbus2vdr: done flushing
Oct 25 08:21:08 yaVDR05 vdr: [1461] dbus2vdr: new message, object /Plugins/softhddevice, interface de.tvdr.vdr.plugin, member SVDRPCommand
Oct 25 08:21:08 yaVDR05 vdr: [1461] dbus2vdr: 1 idle message handler, reusing 0x7f80582ae0e0
Oct 25 08:21:08 yaVDR05 vdr: [2553] dbus2vdr message handler thread started (pid=1118, tid=2553)
Oct 25 08:21:08 yaVDR05 vdr: [2553] dbus2vdr: de.tvdr.vdr.plugin.SVDRPCommand: command 'DETA' has no option
Oct 25 08:21:08 yaVDR05 vdr: [2553] dbus2vdr: invoking softhddevice.SVDRPCommand("DETA", "")
Oct 25 08:21:08 yaVDR05 vdr: [2553] dbus2vdr: moving message handler 0x7f80582ae0e0 from active to finished
Oct 25 08:21:08 yaVDR05 vdr: [2553] dbus2vdr message handler thread ended (pid=1118, tid=2553)
Oct 25 08:21:08 yaVDR05 vdr: [1461] dbus2vdr: connection has messages to send, flushing
Oct 25 08:21:08 yaVDR05 vdr: [1461] dbus2vdr: done flushing
Oct 25 08:21:08 yaVDR05 vdr: [1118] stopping plugin: dynamite
Oct 25 08:21:08 yaVDR05 vdr: [1118] dynamite: force detaching all devices
Oct 25 08:21:08 yaVDR05 vdr: [1118] stopping plugin: menuorg
Oct 25 08:21:08 yaVDR05 vdr: [1118] stopping plugin: dbus2vdr
Oct 25 08:21:08 yaVDR05 vdr: [1118] dbus2vdr: emit upstart-signal stopped for all plugins
Oct 25 08:21:08 yaVDR05 vdr: [1118] dbus2vdr: upstart-signal stopped queued
Oct 25 08:21:08 yaVDR05 vdr: [1469] dbus2vdr: dequeue signal vdr-plugin/stopped
Oct 25 08:21:08 yaVDR05 vdr: [1118] dbus2vdr: stop DBus-Upstart-Signal-Sender
Oct 25 08:21:08 yaVDR05 vdr: [1469] dbus2vdr: retrieving connection for sending signal
Oct 25 08:21:08 yaVDR05 vdr: [1469] dbus2vdr: SendSignal Lock
Oct 25 08:21:08 yaVDR05 vdr: [1469] dbus2vdr: SendSignal Unlock
Oct 25 08:21:08 yaVDR05 vdr: [1469] dbus2vdr: SendSignal: dbus_connection_send
Oct 25 08:21:08 yaVDR05 vdr: [1469] dbus2vdr: SendSignal: dbus_message_unref
Oct 25 08:21:08 yaVDR05 vdr: [1469] dbus2vdr: signal sent
Oct 25 08:21:08 yaVDR05 vdr: [1469] dbus2vdr: emit upstart-signal vdr-plugin for stopped
Oct 25 08:21:08 yaVDR05 vdr: [1469] dbus2vdr: DBus-Upstart-Signal-Sender thread ended (pid=1118, tid=1469)
Oct 25 08:21:09 yaVDR05 vdr: [1461] dbus2vdr: connection has messages to send, flushing
Oct 25 08:21:09 yaVDR05 vdr: [1461] dbus2vdr: done flushing
Oct 25 08:21:09 yaVDR05 vdr: [1118] dbus2vdr: delete DBus-Upstart-Signal-Sender
Oct 25 08:21:09 yaVDR05 vdr: [1118] dbus2vdr: StopMonitor Lock

Display More

I guess it is a failure in my configuration, someone can tell me how to avoid this shutdown?

Regards.
jbjbjb

jbjbjb · October 25, 2012 at 9:30 AM

For more info, this is the syslog of yesterday (no one pressed power button):

Code

Oct 24 08:15:45 yaVDR05 vdr: [1073] cleaning up schedules data
Oct 24 08:15:47 yaVDR05 vdr: [1423] dbus2vdr: new message, object /Shutdown, interface org.freedesktop.DBus.Introspectable, member Introspect
Oct 24 08:15:47 yaVDR05 vdr: [1423] dbus2vdr: introspect object /Shutdown with Introspect
Oct 24 08:15:47 yaVDR05 vdr: [1423] dbus2vdr: new message, object /Shutdown, interface de.tvdr.vdr.shutdown, member SetUserInactive
Oct 24 08:15:47 yaVDR05 vdr: [1423] dbus2vdr: 1 idle message handler, reusing 0x7f773c0055a0
Oct 24 08:15:47 yaVDR05 vdr: [1949] dbus2vdr message handler thread started (pid=1073, tid=1949)
Oct 24 08:15:47 yaVDR05 vdr: [1949] dbus2vdr: moving message handler 0x7f773c0055a0 from active to finished
Oct 24 08:15:47 yaVDR05 vdr: [1949] dbus2vdr message handler thread ended (pid=1073, tid=1949)
Oct 24 08:15:47 yaVDR05 vdr: [1423] dbus2vdr: connection has messages to send, flushing
Oct 24 08:15:47 yaVDR05 vdr: [1423] dbus2vdr: done flushing
Oct 24 08:15:47 yaVDR05 vdr: [1423] dbus2vdr: new message, object /Shutdown, interface de.tvdr.vdr.shutdown, member ConfirmShutdown
Oct 24 08:15:47 yaVDR05 vdr: [1423] dbus2vdr: 1 idle message handler, reusing 0x7f773c0055a0
Oct 24 08:15:47 yaVDR05 vdr: [1950] dbus2vdr message handler thread started (pid=1073, tid=1950)
Oct 24 08:15:47 yaVDR05 vdr: [1950] dbus2vdr: calling shutdown-hook-wrapper /usr/share/vdr-plugin-dbus2vdr/shutdown-wrapper /usr/share/vdr/shutdown-hooks "1351110300 50953 3 \"Gran$
Oct 24 08:15:47 yaVDR05 shutdown-wrapper: [1951] dbus2vdr-shutdown-wrapper: asking shutdown-hook /bin/sh /usr/share/vdr/shutdown-hooks/S90.acpiwakeup
Oct 24 08:15:47 yaVDR05 vdr-addon-acpiwakeup: Setting ACPI alarm time to: 2012-10-24 20:20:00
Oct 24 08:15:47 yaVDR05 vdr-addon-acpiwakeup: Writing to /sys/class/rtc/rtc0/wakealarm
Oct 24 08:15:47 yaVDR05 vdr-addon-acpiwakeup: Writing to /sys/class/rtc/rtc0/wakealarm
Oct 24 08:15:47 yaVDR05 shutdown-wrapper: [1951] dbus2vdr-shutdown-wrapper: result(0) = (null)
Oct 24 08:15:47 yaVDR05 shutdown-wrapper: [1951] dbus2vdr-shutdown-wrapper: asking shutdown-hook /bin/sh /usr/share/vdr/shutdown-hooks/S90.custom
Oct 24 08:15:47 yaVDR05 shutdown-wrapper: [1951] dbus2vdr-shutdown-wrapper: result(0) = (null)
Oct 24 08:15:47 yaVDR05 shutdown-wrapper: [1951] dbus2vdr-shutdown-wrapper: asking shutdown-hook /bin/sh /usr/share/vdr/shutdown-hooks/S90.nvram-wakeup
Oct 24 08:15:47 yaVDR05 vdr-nvram-wakeup: nvram-wakeup functionality is disabled
Oct 24 08:15:47 yaVDR05 shutdown-wrapper: [1951] dbus2vdr-shutdown-wrapper: result(0) = (null)
Oct 24 08:15:47 yaVDR05 shutdown-wrapper: [1951] dbus2vdr-shutdown-wrapper: asking shutdown-hook /bin/sh /usr/share/vdr/shutdown-hooks/S91.lifeguard
Oct 24 08:15:48 yaVDR05 shutdown-wrapper: [1951] dbus2vdr-shutdown-wrapper: result(0) = (null)
Oct 24 08:15:48 yaVDR05 shutdown-wrapper: [1951] dbus2vdr-shutdown-wrapper: asking shutdown-hook /usr/share/vdr/shutdown-hooks/S99.shutdown
Oct 24 08:15:48 yaVDR05 shutdown-wrapper: [1951] dbus2vdr-shutdown-wrapper: result(0) = SHUTDOWNCMD="stop vdr ; /sbin/halt -p"
Oct 24 08:15:48 yaVDR05 vdr: [1950] dbus2vdr: result(0) = SHUTDOWNCMD="stop vdr ; /sbin/halt -p"
Oct 24 08:15:48 yaVDR05 vdr: [1950] dbus2vdr: moving message handler 0x7f773c0055a0 from active to finished
Oct 24 08:15:48 yaVDR05 vdr: [1950] dbus2vdr message handler thread ended (pid=1073, tid=1950)
Oct 24 08:15:48 yaVDR05 vdr: [1423] dbus2vdr: connection has messages to send, flushing
Oct 24 08:15:48 yaVDR05 vdr: [1423] dbus2vdr: done flushing
Oct 24 08:15:48 yaVDR05 vdr: [1423] dbus2vdr: new message, object /Remote, interface de.tvdr.vdr.remote, member Enable
Oct 24 08:15:48 yaVDR05 vdr: [1423] dbus2vdr: 1 idle message handler, reusing 0x7f773c0055a0
Oct 24 08:15:48 yaVDR05 vdr: [2008] dbus2vdr message handler thread started (pid=1073, tid=2008)
Oct 24 08:15:48 yaVDR05 vdr: [2008] dbus2vdr: moving message handler 0x7f773c0055a0 from active to finished
Oct 24 08:15:48 yaVDR05 vdr: [2008] dbus2vdr message handler thread ended (pid=1073, tid=2008)
Oct 24 08:15:48 yaVDR05 vdr: [1423] dbus2vdr: connection has messages to send, flushing
Oct 24 08:15:48 yaVDR05 vdr: [1423] dbus2vdr: done flushing
Oct 24 08:15:48 yaVDR05 vdr: [1423] dbus2vdr: new message, object /Remote, interface de.tvdr.vdr.remote, member HitKey
Oct 24 08:15:48 yaVDR05 vdr: [1423] dbus2vdr: 1 idle message handler, reusing 0x7f773c0055a0
Oct 24 08:15:48 yaVDR05 vdr: [2009] dbus2vdr message handler thread started (pid=1073, tid=2009)
Oct 24 08:15:48 yaVDR05 vdr: [2009] dbus2vdr: de.tvdr.vdr.remote.HitKey: get key 'POWER'
Oct 24 08:15:48 yaVDR05 vdr: [1073] Power button pressed
Oct 24 08:15:48 yaVDR05 vdr: [2009] dbus2vdr: moving message handler 0x7f773c0055a0 from active to finished
Oct 24 08:15:48 yaVDR05 vdr: [2009] dbus2vdr message handler thread ended (pid=1073, tid=2009)
Oct 24 08:15:48 yaVDR05 vdr: [1423] dbus2vdr: connection has messages to send, flushing
Oct 24 08:15:48 yaVDR05 vdr: [1423] dbus2vdr: done flushing
Oct 24 08:15:48 yaVDR05 vdr: [1423] dbus2vdr: new message, object /Remote, interface de.tvdr.vdr.remote, member Disable
Oct 24 08:15:48 yaVDR05 vdr: [1423] dbus2vdr: 1 idle message handler, reusing 0x7f773c0055a0
Oct 24 08:15:48 yaVDR05 vdr: [2010] dbus2vdr message handler thread started (pid=1073, tid=2010)
Oct 24 08:15:48 yaVDR05 vdr: [2010] dbus2vdr: moving message handler 0x7f773c0055a0 from active to finished
Oct 24 08:15:48 yaVDR05 vdr: [2010] dbus2vdr message handler thread ended (pid=1073, tid=2010)
Oct 24 08:15:48 yaVDR05 vdr: [1423] dbus2vdr: connection has messages to send, flushing
Oct 24 08:15:48 yaVDR05 vdr: [1423] dbus2vdr: done flushing
Oct 24 08:15:48 yaVDR05 vdr: [1073] confirm: Pulse una tecla para interrumpir apagar
Oct 24 08:15:48 yaVDR05 vdr: [1073] warning: Pulse una tecla para interrumpir apagar
Oct 24 08:15:48 yaVDR05 vdr: [2011] Text2Skin: message display update thread started (pid=1073, tid=2011)
Oct 24 08:15:54 yaVDR05 vdr: [2011] Text2Skin: message display update thread ended (pid=1073, tid=2011)
Oct 24 08:15:54 yaVDR05 vdr: [1073] confirmed
Oct 24 08:15:54 yaVDR05 vdr: [1073] next timer event at Wed Oct 24 22:25:00 2012
Oct 24 08:15:54 yaVDR05 vdr: [1073] executing '/usr/lib/vdr/vdr-shutdown.wrapper 1351110300 50946 3 "Gran hotel~Gran Hotel" 1'
Oct 24 08:15:54 yaVDR05 vdr: [1073] saved setup to /var/lib/vdr/setup.conf
Oct 24 08:15:54 yaVDR05 vdr-shutdown: executing /usr/share/vdr/shutdown-hooks/S90.acpiwakeup as shell script
Oct 24 08:15:54 yaVDR05 vdr-addon-acpiwakeup: Setting ACPI alarm time to: 2012-10-24 20:20:00
Oct 24 08:15:54 yaVDR05 vdr-addon-acpiwakeup: Writing to /sys/class/rtc/rtc0/wakealarm
Oct 24 08:15:54 yaVDR05 vdr-addon-acpiwakeup: Writing to /sys/class/rtc/rtc0/wakealarm
Oct 24 08:15:54 yaVDR05 vdr-shutdown: executing /usr/share/vdr/shutdown-hooks/S90.custom as shell script
Oct 24 08:15:54 yaVDR05 vdr-shutdown: executing /usr/share/vdr/shutdown-hooks/S90.nvram-wakeup as shell script
Oct 24 08:15:54 yaVDR05 vdr-nvram-wakeup: nvram-wakeup functionality is disabled

Display More

Regards.
jbjbjb

DocViper · October 25, 2012 at 9:30 AM

It's not a bug its a feature !

After an automated wakeup the VDR shuts down when the recording is finished. But you can push a button at it will detect the user activity and will consider the value of minuseractivity timer.

Joe

seahawk1986 · October 25, 2012 at 9:35 AM

Hi,

Quote from jbjbjb

I guess it is a failure in my configuration, someone can tell me how to avoid this shutdown?

The Shutdown is probably caused by the vdr-frontend upstart job (when using softhddevice). I will update yavdr-utils it to omit the shutdown-Request if Minimum time of inactivity (m) is set to "0".

What value is assigned to MinEventTimeout?

Code

grep MinEventTimeout /etc/vdr/setup.conf

jbjbjb · October 25, 2012 at 9:53 AM

Quote from seahawk1986
What value is assigned to MinEventTimeout?
Code
grep MinEventTimeout /etc/vdr/setup.conf

Hi,

Code

grep MinEventTimeout /etc/vdr/setup.conf

returns

Code

MinEventTimeout = 120

Also I have configured:

Code

MinUserInactivity = 0

Regards.
jbjbjb

jbjbjb · October 29, 2012 at 9:20 AM

Quote from seahawk1986

I will update yavdr-utils it to omit the shutdown-Request if Minimum time of inactivity (m) is set to "0".

Hi.

Is it already done this change in yavdr-utils?

Regards.
jbjbjb

seahawk1986 · October 29, 2012 at 9:24 AM

Not yet, I will probably be able to update it this evening.

jbjbjb · November 1, 2012 at 9:28 AM

Hi
It works fine, thanks.

Regards
jbjbjb

seahawk1986 · November 1, 2012 at 10:02 AM

That's great

[SOLVED] yaVDR 0.5 auto shutdown?

Participate now!

Users Viewing This Thread