[mythtv-users] MythTv BE/FE go to sleep but doesn't wake up
ganassa at gmail.com
Thu Feb 16 18:51:43 UTC 2012
Finally, it looks like it's working:
Feb 16 19:24:39 multisala kernel: Kernel logging (proc) stopped.
Feb 16 19:45:52 multisala kernel: imklog 4.2.0, log source = /proc/kmsg
Thank you very much to all of you, all those time factores really got me
mad and I miss the chanche to blame BIOS - I could not believe that the
local OS time could be different from the BIOS one, not after a reboot, at
The very-final test will be tomorrow, but I expect to see my BE/FE wake up
at the right time, this time :)
2012/2/16 ganassa <ganassa at gmail.com>
> Check done:
> 1) /etc/default/rcS
> I've changed:
> 2) BIOS
> time was set as 20:15, but my local time is 19:15, and UTC time is 18:15 -
> now it all make sense.
> Probably, when the BE/FE is started up, it reports the BIOS time (that is
> wrong) in the log, but immediately after it the OS update the time to
> what's set for Local (that is right), and this explain the time-warp in the
> log. Last, this update is not effective after a restart, so at the next
> boot the time setting was still wrong, and so on.
> 3) BE/FE restarted and tzdata reconfigured
> $ date
> Thu Feb 16 19:17:05 CET 2012
> $ sudo dpkg-reconfigure tzdata
> Current default time zone: 'Europe/Rome'
> Local time is now: Thu Feb 16 19:17:27 CET 2012.
> Universal Time is now: Thu Feb 16 18:17:27 UTC 2012.
> $ date
> Thu Feb 16 19:17:30 CET 2012
> Now it makes sense!
> 4) BE/FE shutting down for the final test
> 2012-02-16 19:24:39.461 CheckShutdownServer returned - OK to shutdown
> 2012-02-16 19:24:39.474 Running the command to set the next scheduled
> wakeup time :-
> mythshutdown --setwakeup
> 2012-02-16 19:24:39.563 Running the command to shutdown this computer :-
> mythshutdown --shutdown
> Running /usr/bin/setwakeup.sh to set the wakeup time to 1329417900
> Broadcast message from root at multisala
> (unknown) at 19:24 ...
> The system is going down for halt NOW!
> next scheduled recording is for 20:00
> $ time=1329417900
> $ date -d @$time +%F" "%T
> 2012-02-16 19:45:00
> and this is right, too. Let's wait some minutes...
> 2012/2/16 ganassa <ganassa at gmail.com>
>> Douglas, maybe you got it:
>> $ cat /etc/default/rcS |grep UTC
>> I'm going to try your suggest.
>> In the meanwhile: thank you in advanca.
>> PS: I think this should be added in the Wiki (maybe I can do it, too?
>> I'll check)
>> 2012/2/16 Douglas Mackay <douglas.mackay at gmail.com>
>>> On 16 February 2012 10:46, ganassa <ganassa at gmail.com> wrote:
>>> > This seems to be a reasonable hypothesis, but does it means that the
>>> > clock and the OS clock are totally indipendent? Or I'm missing
>>> > BTW, this night I'll try to check BIOS settings and changing date
>>> > to 'real' UTC time, and check if local time keeps being +1.
>>> > Just for information: the behavior is not random, today the BE/FE woke
>>> up at
>>> > 10:30 and reported the same confusing timing as yesterday:
>>> I would check UTC is set to yes in /etc/default/rcS, set the time to
>>> UTC in the bios and reset the timezone to CET using 'dpkg-reconfigure
>>> mythtv-users mailing list
>>> mythtv-users at mythtv.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the mythtv-users