Hi, I've just deployed my home server, of course using Gentoo :) I setup openntpd there and /var/log/messages says to me that every few minutes clock is adjusted by ~100s. Is it a bug or I've missed smth? chipset: nForce2 And, btw, what is also strange - ntpd use different time in different log message types. Actual local time was 22h (GMT+3). System clock is UTC (note: I've terminated several times ntpd - I've changed servers, I hoped it help, but...)
thanks for any suggestion /var/log/messages: Jul 27 22:07:27 enigma ntpd[32345]: listening on 192.168.3.1 Jul 27 19:07:27 enigma ntpd[32345]: ntp engine ready Jul 27 19:07:50 enigma ntpd[32345]: peer 129.6.15.29 now valid Jul 27 19:07:53 enigma ntpd[32345]: peer 129.6.15.28 now valid Jul 27 22:08:43 enigma ntpd[32344]: adjusting local clock by 102.470196s Jul 27 19:09:31 enigma ntpd[32345]: peer 129.6.15.29 now invalid Jul 27 19:10:21 enigma ntpd[32345]: ntp engine exiting Jul 27 22:10:21 enigma ntpd[32344]: Terminating Jul 27 22:10:21 enigma ntpd[32677]: listening on 192.168.3.1 Jul 27 19:10:21 enigma ntpd[32677]: ntp engine ready Jul 27 19:10:45 enigma ntpd[32677]: peer 129.6.15.28 now valid Jul 27 19:10:45 enigma ntpd[32677]: peer 129.6.15.29 now valid Jul 27 22:11:46 enigma ntpd[32676]: adjusting local clock by 102.424075s Jul 27 22:13:21 enigma ntpd[32676]: adjusting local clock by 102.314918s Jul 27 22:17:10 enigma ntpd[32676]: adjusting local clock by 102.248247s Jul 27 22:19:13 enigma ntpd[32676]: adjusting local clock by 102.065928s Jul 27 19:20:04 enigma ntpd[32677]: ntp engine exiting Jul 27 22:20:04 enigma ntpd[32676]: Terminating Jul 27 22:20:04 enigma ntpd[1092]: listening on 192.168.3.1 Jul 27 19:20:04 enigma ntpd[1092]: ntp engine ready Jul 27 19:20:22 enigma ntpd[1092]: peer 81.210.250.102 now valid Jul 27 19:20:22 enigma ntpd[1092]: peer 89.25.11.9 now valid Jul 27 19:20:23 enigma ntpd[1092]: peer 212.244.104.2 now valid Jul 27 19:20:25 enigma ntpd[1092]: peer 139.143.5.30 now valid Jul 27 19:20:26 enigma ntpd[1092]: peer 130.60.75.60 now valid Jul 27 19:20:27 enigma ntpd[1092]: peer 213.239.212.133 now valid Jul 27 19:20:30 enigma ntpd[1092]: peer 66.180.136.186 now valid Jul 27 22:21:26 enigma ntpd[1091]: adjusting local clock by 101.912042s Jul 27 19:24:18 enigma ntpd[1092]: ntp engine exiting Jul 27 22:24:18 enigma ntpd[1091]: Terminating Jul 27 22:24:18 enigma ntpd[1431]: listening on 192.168.3.1 Jul 27 19:24:18 enigma ntpd[1431]: ntp engine ready Jul 27 19:24:37 enigma ntpd[1431]: peer 213.239.212.133 now valid Jul 27 19:24:38 enigma ntpd[1431]: peer 212.244.104.2 now valid Jul 27 19:24:39 enigma ntpd[1431]: peer 89.25.11.9 now valid Jul 27 19:24:39 enigma ntpd[1431]: peer 209.11.160.7 now valid Jul 27 19:24:41 enigma ntpd[1431]: peer 130.60.75.60 now valid Jul 27 19:24:43 enigma ntpd[1431]: peer 81.210.250.102 now valid Jul 27 19:24:44 enigma ntpd[1431]: peer 66.180.136.186 now valid Jul 27 19:25:45 enigma ntpd[1431]: peer 89.25.11.9 now invalid Jul 27 22:26:08 enigma ntpd[1430]: adjusting local clock by 101.742480s Jul 27 19:26:24 enigma ntpd[1431]: peer 130.60.75.60 now invalid Jul 27 19:26:54 enigma ntpd[1431]: peer 81.210.250.102 now invalid Jul 27 22:29:46 enigma ntpd[1430]: adjusting local clock by 101.681414s Jul 27 22:32:30 enigma ntpd[1430]: adjusting local clock by 101.532742s Jul 27 19:34:59 enigma ntpd[1431]: peer 82.225.138.2 now valid Jul 27 22:35:57 enigma ntpd[1430]: adjusting local clock by 101.413649s Jul 27 19:36:58 enigma ntpd[1431]: peer 89.25.11.9 now valid Jul 27 19:37:14 enigma ntpd[1431]: peer 130.60.75.60 now valid Jul 27 19:37:57 enigma ntpd[1431]: peer 81.210.250.102 now valid Jul 27 22:38:35 enigma ntpd[1430]: adjusting local clock by 101.265187s -- best regards, Aleksey V. Kunitskiy my public GPG/PGP key: http://www.alexey-kv.org.ua/pubkey.asc
pgp2G3Ioaw1qy.pgp
Description: PGP signature
