Crash causes clock to akt strange (runs backwards)
 

Hi,

This night we had a power outage in our building which had the nice effect that all computers shut down in a rather nasty way. Most computers are back up and running except one.

The computer boots up nicely, but then the following things appear in the /var/log/messages

Mar 29 10:58:40 inwtheo1 ntpd[6214]: adjusting local clock by 188.198045s
Mar 29 11:00:47 inwtheo1 ntpd[6214]: adjusting local clock by 188.107806s
Mar 29 11:00:51 inwtheo1 ntpd[5606]: adjusting local clock by 188.141614s
Mar 29 11:03:00 inwtheo1 ntpd[5606]: adjusting local clock by 187.870878s
Mar 29 11:03:23 inwtheo1 ntpd[6214]: adjusting local clock by 187.879573s
Mar 29 09:04:29 inwtheo1 ntpd[6215]: reply from 157.193.40.37: not synced, next query 624s
Mar 29 09:04:37 inwtheo1 ntpd[5607]: reply from 157.193.40.37: not synced, next query 607s

If you look at the timestamp of the log you notice that the system is running "backwards"!
After these last two notices, the system hanged completely! Hard reboot is the only way to survive get it back up and running.

I will try to post more info here, from the moment I have more.
any help would be welcome.

Okay, I still don't know what is going on, but here is a better snipet of the /var/log/messages

Mar 29 08:40:06 inwtheo1 ntpd[5689]: peer 157.193.40.37 now valid
Mar 29 10:40:13 inwtheo1 kernel: Shorewall:net2all:DROP:IN=eth0 OUT= MAC= SRC=157.193.98.10 DST=224.0.0.251 LEN=110 TOS=0x00 PREC=0x00 TTL=
255 ID=9 DF PROTO=UDP SPT=5353 DPT=5353 LEN=90
Mar 29 10:40:45 inwtheo1 kernel: Shorewall:net2all:DROP:IN=eth0 OUT= MAC= SRC=157.193.98.10 DST=224.0.0.251 LEN=110 TOS=0x00 PREC=0x00 TTL=
255 ID=10 DF PROTO=UDP SPT=5353 DPT=5353 LEN=90
Mar 29 10:40:57 inwtheo1 ntpd[5688]: adjusting local clock by 166.241134s
Mar 29 10:41:05 inwtheo1 sshd[6228]: Accepted publickey for klaas from 157.193.99.34 port 50284 ssh2
Mar 29 10:41:18 inwtheo1 su(pam_unix)[6274]: session opened for user root by klaas(uid=501)
Mar 29 10:41:49 inwtheo1 kernel: Shorewall:net2all:DROP:IN=eth0 OUT= MAC= SRC=157.193.98.10 DST=224.0.0.251 LEN=110 TOS=0x00 PREC=0x00 TTL=
255 ID=11 DF PROTO=UDP SPT=5353 DPT=5353 LEN=90
Mar 29 10:41:59 inwtheo1 ntpd[5688]: adjusting local clock by 166.240065s
Mar 29 10:44:13 inwtheo1 ntpd[5688]: adjusting local clock by 166.238681s
Mar 29 10:45:13 inwtheo1 ntpd[5688]: adjusting local clock by 166.174413s
Mar 29 10:46:15 inwtheo1 ntpd[5688]: adjusting local clock by 187.903248s


So the time does not run backwards or anything like that, but when checking the peer, it uses UTC otherwise summertime (for some strange reason)
the last calls show that the time is just not updated, although in the really last call, there is a loss of 20 seconds!
After this the server hanged.

I already removed openntpd and installed ntp-client, this worked and set the clock right!
Nonetheless the server is still hanging from time to time.

But regarding this, why is the clock not updated?

regards
klaas