-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Friday 2007-12-07 at 00:05 +1100, Basil Chupin wrote:
Carlos,
I haven't been paying too much attention to what you have written re the problem, what result do you get when you try setting the time manually, as root, from the command line? You know, the old
ntpdate -u <IP-address-of-time-server>
It works, of course. That's what I'm doing every time NTP quits. The problem is that NTP can't keep the system clock disciplined, it strays off as soon as NTP looses the network peers, and not a second or two, but several minutes. It seems a kernel problem, not an NTP problem. Look again the logs: 5 Dec 11:32:50 ntpd[28229]: synchronized to 194.238.48.2, stratum 2 5 Dec 11:32:50 ntpd[28229]: kernel time sync status change 0001 5 Dec 11:32:50 ntpd[28229]: system event 'event_sync_chg' (0x03) status 'leap_none, sync_ntp, 3 events, event_peer/strat_chg' (0x634) 5 Dec 11:32:50 ntpd[28229]: system event 'event_peer/strat_chg' (0x04) status 'leap_none, sync_ntp, 4 events, event_sync_chg' (0x643) 5 Dec 12:28:27 ntpd[28229]: offset -0.004594 sec freq 81.557 ppm error 0.004265 poll 7 5 Dec 12:49:02 ntpd[28229]: no servers reachable 5 Dec 12:58:24 ntpd[28229]: synchronized to 147.83.123.136, stratum 2 5 Dec 12:59:42 ntpd[28229]: time reset +4.674598 s At 12:49:02 it looses the network peer, and 10 minutes later it gets another, and finds it has to reset the clock by 4.6 seconds. A bit later: 5 Dec 12:59:42 ntpd[28229]: system event 'event_clock_reset' (0x05) status 'sync_alarm, sync_unspec, 7 events, event_peer/strat_chg' (0xc074) 5 Dec 12:59:42 ntpd[28229]: system event 'event_peer/strat_chg' (0x04) status 'sync_alarm, sync_unspec, 8 events, event_clock_reset' (0xc085) 5 Dec 13:00:02 ntpd[28229]: peer 147.83.123.136 event 'event_reach' (0x84) status 'unreach, conf, 2 events, event_reach' (0x8024) 5 Dec 13:00:31 ntpd[28229]: peer 194.238.48.2 event 'event_reach' (0x84) status 'unreach, conf, 2 events, event_reach' (0x8024) 5 Dec 13:00:44 ntpd[28229]: peer 193.138.215.60 event 'event_reach' (0x84) status 'unreach, conf, 2 events, event_reach' (0x8024) 5 Dec 13:01:52 ntpd[28229]: peer 213.251.176.72 event 'event_reach' (0x84) status 'unreach, conf, 2 events, event_reach' (0x8024) 5 Dec 13:06:26 ntpd[28229]: synchronized to 213.251.176.72, stratum 3 5 Dec 13:11:30 ntpd[28229]: synchronized to 194.238.48.2, stratum 2 5 Dec 13:24:13 ntpd[28229]: time reset +581.195037 s There, without loosing network fully, it has to reset the clock by 581 seconds, ie, 10 minutes error since less that an hour and a half after last reset! Ten minutes error! WTF is happening? :-/ - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHV/8gtTMYHG2NR9URArGmAJ9l1a0+/wW8vOIxo8AksQUn2W+kVgCdGUt9 7VFcK3QgyZzCvK8iWrTw8DA= =c7ys -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org