[mythtv-users] MythTv BE/FE go to sleep but doesn't wake up

[ganassa]

Update about the "future issue":

Yesterday I've set a wake period for 12.30 (AM), and turned it off after
midnight.

I've just checked if it was online and, yes, I could log in via ssh. It's
about 11.15 (AM)

So I've looked in syslog to see at what time it woke up:

Feb 15 00:37:01 multisala kernel: Kernel logging (proc) stopped.
Feb 15 11:30:53 multisala kernel: imklog 4.2.0, log source = /proc/kmsg
started.


Ok, it woke up at 11.30, instead than 12.30

But.. WAIT: now it's 11.15! The "future" issue is still here, and NTPD is
offline, I can't blame it.

So I decided to check why it's online. First, check mythshutdown to see why
it's still online:

$ mythshutdown -c -s -v general


2012-02-15 11:15:12.824 Mythshutdown: --check
2012-02-15 11:15:12.824 Mythshutdown: --status
...
2012-02-15 11:15:12.937 Mythshutdown: --status returned: 0
2012-02-15 11:15:12.937 OK to shutdown
2012-02-15 11:15:12.937 Mythshutdown: --check returned: 0


It shouldn't be online, let's see other logs... OH WAIT, now it's offline :/

Anyone have an idea of the reason why:
- I set a wakeup period at 12.30
- I found it woked up at 11.15
- It logs that he wake up ad 11.30

this thing is getting me mad worst than Daylight Saving Time issues in real
life ;)




2012/2/14 ganassa <ganassa at gmail.com>

> An update regarding this problem: yesterday I've encountered the same
> non-waking up problem again, in a random manner: I was expecting two
> wake-up moments, one in the morning and the other one in the afternoon.
> Well: for the first one scheduling the MythTv BE/FA woke up and recorded
> correctly, for the secondo one it didn't wake up at all.
>
> So, while doing a further check, connecting and disconnecting via shh, I
> saw this:
>
> ~$ ssh multisala
> datLinux multisala 2.6.35-32-generic #65-Ubuntu SMP Tue Jan 24 13:48:14
> UTC 2012 i686 GNU/Linux
> Ubuntu 10.10
> ...
> No mail.
> *Last login: Tue Feb 14 01:58:57 2012 from lapsung*
> date
> ~$ date
> *Tue Feb 14 01:02:16 CET 2012*
>
>
> In brief: the second time I logged into the BE/FE ssh reported that the
> last login was in the future!
> So I realized that, probably, the problem isn't related to the
> MythTv/MythWelcome configuration but in something related to the time
> settings itself of the system, instead.
> I've checked running processes and, yes, my backend was running 'ntpd'.
> So I stopped and disabled at boot the NTP daemon . Let's see if I can
> blame it.
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.mythtv.org/pipermail/mythtv-users/attachments/20120215/3be1c881/attachment.html