[mythtv-users] Backend wakes up too early then shuts down and misses recording

[Hika van den Hoven]

Hoi Tony,

Thursday, January 30, 2014, 3:44:30 PM, you wrote:

> Hika van den Hoven wrote, on 30/01/14 13:59:
>> Hoi Tony,
>>
>> Thursday, January 30, 2014, 2:28:43 PM, you wrote:
>>
>>> I've running a 0.27 system where my backend shuts down when idle and
>>> ACPI wakes up 10 minutes before recording. Normally this works very
>>> well, but I saw something very odd last night. The system finished a
>>> transcoding job just after 11pm, just after 2300, and the next recording
>>> was at 12:53am, i.e. 00:53. So it should have woken itself at approx 00:43.
>>> What it actually did was wakeup at 00:29:40, decide that the next
>>> recording at 00:53 was too far into the future, and then, at 00:30:16,
>>> write the next ACPI wake up time as 00:29:40 (in the past!!!), and shut
>>> itself down. Needless to say, the recording was missed (or would have
>>> been if I hadn't been in the room tinkering with another box and spotted
>>> what was going on...)
>>> Any ideas? Logs below.
>>> Jan 29 23:03:48 tv mythbackend: mythbackend[1960]: I Scheduler
>>> scheduler.cpp:2839 (CheckShutdownServer) CheckShutdownServer returned -
>>> OK to shutdown
>>> Jan 29 23:03:48 tv mythbackend: mythbackend[1960]: N Scheduler
>>> scheduler.cpp:2934 (ShutdownServer) Running the command to set the next
>>> scheduled wakeup time :-#012#011#011#011#011#011#011mythshutdown
>>> --setwakeup 2014-01-30T00:29:40
>>> Jan 29 23:03:49 tv mythbackend: mythbackend[1960]: N Scheduler
>>> scheduler.cpp:2965 (ShutdownServer) Running the command to shutdown this
>>> computer :-#012#011#011#011#011#011#011sudo -H mythshutdown --shutdown
>>> Jan 30 00:30:16 tv mythbackend: mythbackend[1912]: C thread_unknown
>>> mythcommandlineparser.cpp:2595 (ConfigureLogging) mythbackend version:
>>> fixes/0.27 [v0.27-122-g9d4b5e2] www.mythtv.org
>>> ...
>>> Jan 30 00:31:27 tv mythbackend: mythbackend[1912]: I Scheduler
>>> scheduler.cpp:2839 (CheckShutdownServer) CheckShutdownServer returned -
>>> OK to shutdown
>>> Jan 30 00:31:27 tv mythbackend: mythbackend[1912]: N Scheduler
>>> scheduler.cpp:2934 (ShutdownServer) Running the command to set the next
>>> scheduled wakeup time :-#012#011#011#011#011#011#011mythshutdown
>>> --setwakeup 2014-01-30T00:29:40
>>> Jan 30 00:31:28 tv mythbackend: mythbackend[1912]: N Scheduler
>>> scheduler.cpp:2965 (ShutdownServer) Running the command to shutdown this
>>> computer :-#012#011#011#011#011#011#011sudo -H mythshutdown --shutdown
>>> _______________________________________________
>>> mythtv-users mailing list
>>> mythtv-users at mythtv.org
>>> http://www.mythtv.org/mailman/listinfo/mythtv-users
>>
>> I don't understand it setting a wake up time in the past, but as I
>> understand setting wake up times in the bios can be haphazard.
>>
>> You can set it not to shutdown if an action is expected within a
>> set time. I guess you should set it larger then the time it wakes up
>> before an event. That being to small could explain the shutting down.
>>
>> Tot mails,
>>    Hika                            mailto:hikavdh at gmail.com
>>
>> "Zonder hoop kun je niet leven
>> Zonder leven is er geen hoop
>> Het eeuwige dilemma
>> Zeker als je hoop moet vernietigen om te kunnen overleven!"
>>
>> De lerende Mens
>> --
>>
>> _______________________________________________
>> mythtv-users mailing list
>> mythtv-users at mythtv.org
>> http://www.mythtv.org/mailman/listinfo/mythtv-users

> thanks. It looks like there is a (very obscure*) bug in the code which
> calculates next wake up time. This caused my box to wake up too early 
> (and then after waking up set the next wake up time to be in the past 
> which really messed things up). I could set the no-shutdown time to be
> longer, but I can't avoid the bug unless I set it to be very very long,
> in which case I might as well leave the machine on anyway...

> (*I've been running 0.21 for quite a few years until December and never
> seen this before. The only thing that screwed up shutdown and wakeup was
> some kind of operating system or hardware problem: hanging on power down
> or power up.)
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://www.mythtv.org/mailman/listinfo/mythtv-users


I don't have experience with it for my backend is also fileserver etc.
so it's running fulltime. But if you could find out the max early wake
up, you could adjust the max wait time to that.

Tot mails,
  Hika                            mailto:hikavdh at gmail.com

"Zonder hoop kun je niet leven
Zonder leven is er geen hoop
Het eeuwige dilemma
Zeker als je hoop moet vernietigen om te kunnen overleven!"

De lerende Mens
--