[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

nptd not changing time.



I'm running ntpd on OpenBSD 3.6-release with default config. The
daemon is running and finding a big time difference, but it's not
changing the time. Here is a partial log entry:

Dec  2 11:39:59 Jesu ntpd[20331]: adjusting local clock by -566.282920s
Dec  2 11:44:02 Jesu ntpd[20331]: adjusting local clock by -565.378171s
Dec  2 11:45:18 Jesu ntpd[9153]: peer 200.30.141.26 now invalid
Dec  2 11:45:34 Jesu ntpd[9153]: peer 200.30.141.26 now valid
Dec  2 11:45:37 Jesu ntpd[9153]: peer 217.204.244.146 now invalid
Dec  2 11:45:52 Jesu ntpd[9153]: peer 217.204.244.146 now valid
Dec  2 11:47:33 Jesu ntpd[20331]: adjusting local clock by -564.486513s
Dec  2 11:51:04 Jesu ntpd[20331]: adjusting local clock by -563.626742s
Dec  2 11:53:12 Jesu ntpd[9153]: peer 200.141.215.161 now invalid
Dec  2 11:53:55 Jesu ntpd[9153]: peer 200.141.215.161 now valid
Dec  2 11:54:03 Jesu ntpd[20331]: adjusting local clock by -562.794721s

Is ntpd not changing the time because it's already off by such a wide
margin (almost 10 minutes)? I don't understand the "now invalid" and
"now valid" messages, above.

I searched the archives of this list, and found someone who said (1)
that ntpd tries to set the correct time when it's first run, even when
there's a big difference, and (2) that perhaps rdate should be used
the very first time, if there's a big difference. Maybe this is
required -- but if that's the case, why the log entries, above?

I've read the manuals for ntpd and ntpd.conf, and there's nothing that
applies to this problem.