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
ROP: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
ROP: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
ROP: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