A d-u this weekend (after not du-ing for a while) seem to have messed up the handling of system time. Problem: clock is two hour behind.
Here is the full story:
During boot I enter BIOS to check clock is correct. Clock shows 17:09:56
After booting into init 3, let’s check date:
Tue Aug 9 15:11:46 CEST 2011
Ok, let’s correct date using ntpdate-debian:
9 Aug 17:12:23 ntpdate: step time server 220.127.116.11 offset 7199.910742 sec
Verify with date:
Tue Aug 9 17:13:57 CEST 2011
Now take eth0 down/up to get something into log
$ ifdown eth0
$ ifup eth0
Aug 9 17:17:05 siduxbox kernel: [ 448.385247] via-rhine 0000:00:12.0: eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
Seems ok. Now reboot.
After reboot, check date again:
Tue Aug 9 15:21:46 CEST 2011
Back to point A again..
Anything interesting in /var/log/messages? Well, to me this look strange, but maybe it is not?
Aug 9 17:18:55 siduxbox shutdown: shutting down for system reboot
Aug 9 17:18:00 siduxbox exiting on signal 15
Aug 9 17:19:52 siduxbox syslogd 1.5.0#6.1: restart.
Aug 9 15:20:47 siduxbox /usr/sbin/gpm: *** info [daemon/startup.c(131)]:
Aug 9 15:20:47 siduxbox /usr/sbin/gpm: Started gpm successfully. Entered daemon mode.
Aug 9 15:20:48 siduxbox kernel: Inspecting /boot/System.map-3.0-1.slh.4-aptosid-686
It seems like the date/time is correct at boot time but then gets changed.
Can anybody explain what is going on? Any ideas on how this can be resolved?