We have a server running ntpd, using pool.ntp.org as time server.
On Sunday, an unusually large time correction caused ntpd to stop.
Could this be a glitch with pool.ntp.org? The other strange thing is
that there seems to be no ntpd activity between 6:47 and 13:38.
Anybody seen anything like this before?
Using: ntp-simple 1:4.2.0a+stable-2sarge1
Thanks
Here's the last few ntpd entries from the log:
Sep 18 04:23:29 large ntpd[1179]: time reset +0.143371 s
Sep 18 04:27:51 large ntpd[1179]: synchronized to LOCAL(0), stratum 10
Sep 18 04:29:59 large ntpd[1179]: synchronized to 62.52.109.76, stratum 2
Sep 18 04:58:00 large ntpd[1179]: time reset -0.244132 s
Sep 18 05:02:19 large ntpd[1179]: synchronized to LOCAL(0), stratum 10
Sep 18 05:04:30 large ntpd[1179]: synchronized to 62.52.109.76, stratum 2
Sep 18 05:56:06 large ntpd[1179]: time reset -0.135224 s
Sep 18 06:00:23 large ntpd[1179]: synchronized to LOCAL(0), stratum 10
Sep 18 06:01:28 large ntpd[1179]: synchronized to 62.52.109.76, stratum 2
Sep 18 06:21:58 large ntpd[1179]: time reset +0.140344 s
Sep 18 06:26:19 large ntpd[1179]: synchronized to LOCAL(0), stratum 10
Sep 18 06:34:56 large ntpd[1179]: synchronized to 62.52.109.76, stratum 2
Sep 18 06:47:55 large ntpd[1179]: synchronized to LOCAL(0), stratum 10
Sep 18 13:38:41 large ntpd[1179]: synchronized to 62.52.109.76, stratum 2
Sep 18 13:42:16 large ntpd[1179]: time correction of 2598 seconds
exceeds sanity limit (1000); set clock manually to the correct UTC time.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
