[mythtv-users] acpi wakeup fails - set to wakeup 3 min ago

[Robert Koblish]

I am setting up a master backend that will eventually live below the
stairs. I started with Ubuntu 9.10 and installed Mythbuntu on top of
it. For convenience of administering it I installed the frontend also.

I am running mythwelcome, configured in /etc/mythtv/session-settings
-- I uncommented the line that reads MYTHWELCOME=true. At the moment I
have the machine set to run an XFCE session with autologin to the
mythuser account and autostartup of mythfrontend -- this happens
because of the aforementioned edit to session-settings. I found that I
also had to edit /usr/bin/checklogin.sh to allow shutdown to happen
with 0 or 1 users logged in, instead of just 0. (Once I get out of the
testing phase I will get rid of the autologin, but for now it seems
handy.)

I have successfully configured and tested acpi wakeup, and also
wake-on-lan (to be used to start the MBE box when a remote frontend
starts). My hardware clock is set to GMT and I have made the
appropriate adjustments as outlined in
<www.mythtv.org/wiki/ACPI_Wakeup>.

Problem is, sometimes the machine has failed to wake up on schedule.
When I later woke the box manually, it has booted fine. Per the
following extract from the backend log, it appears to me that the
shutdown happened three minutes after the scheduled wakeup time, so
the scheduled wakeup never happened.
2010-02-04 09:43:10.828 I'm idle now... shutdown will occur in 600 seconds.
2010-02-04 09:50:31.642 UPnpMedia: BuildMediaMap - no VideoStartupDir
set,  skipping scan.
2010-02-04 09:51:33.893 AutoExpire: CalcParams(): Max required Free
Space: 1.0 GB w/freq: 15 min
2010-02-04 09:53:10.514 MainServer::ANN Monitor
2010-02-04 09:53:10.544 adding: myth2 as a client (events: 0)
2010-02-04 09:53:10.579 MainServer::ANN Monitor
2010-02-04 09:53:10.628 adding: myth2 as a client (events: 1)
2010-02-04 09:53:10.705 CheckShutdownServer returned - OK to shutdown
2010-02-04 09:53:10.761 Running the command to set the next scheduled
wakeup time :-
						mythshutdown --setwakeup 2010-02-04T09:50:00

2010-02-04 09:53:10.961 Running the command to shutdown this computer :-
						mythshutdown --shutdown
2010-02-04 11:24:40.056 mythbackend version:
branches/release-0-22-fixes [22594] www.mythtv.org

(This last line is from a manual wakeup -- the box should have started
at 0950 for a 1000 recording.)

Immediately prior to the above snippet, I was watching a recording
that had been made from 0800..0830. I suspect that commercial flagging
was occurring at this time, also.

The relevant backend settings are
Idle shutdown timeout = 600 sec
Max wait for recording = 15 min
Startup before recording = 600 sec
Pre Shutdown Check Command = /usr/bin/checklogin.sh

Note that the idle shutdown timeout is 600 sec (10 min). I changed it
from the default of 900 sec because I suspected a race condition
between it and the Max Wait for Recording. I saw the same behavior
(set wakeup time ~ 3 min in the past) when the idle shutdown timeout
was at its default value.

Any ideas about what I've misconfigured, or about the next steps to
debug this? Would increasing the verbosity of the logs be useful?

Thanks in advance,
Bob Koblish