[ntp:questions] ntp clients out of sync with server
naihong at gmail.com
naihong at gmail.com
Tue Oct 28 21:22:39 UTC 2008
I know 127.127.1.0 should appear in any clients' configure file. But
without this statement, the display from ntpq -p, only display the
client out of sync with server. I mean tally '*' is missing from
server, I did not know which time the client followed. So add
127.127.1.0, just make sure the client sync to its own clock. At
beginning, I just follow previous posts, use the simplest
configuration for orphan mode
driftfile "C:\Program Files\NTP\etc\ntp.drift"
tos orphan 10
driftfile "C:\Program Files (x86)\NTP\etc\ntp.drift"
server 10.200.98.51 iburst
But this doesn't work. The clients cannot follow server's time after
about one day running.
On Oct 28, 12:33 pm, Steve Kostecke <koste... at ntp.org> wrote:
> On 2008-10-28, naih... at gmail.com <naih... at gmail.com> wrote:
> > ... time island ...
> > I select the orphan mode. After the server and clients start up. At
> > first, the clents can sync to server's clock. But after 1 day, all 3
> > clients begin to sync to its local clock, not the server.
> > The output of ntpq -p is,
> > remote refid st t when poll reach delay offset jitter
> > ===============================================================
> > 10.200.98.51 127.0.0.1 5 u 105 256 377 0.299 -1.886 0.591
> > *LOCAL(0) .LOCL. 12 l 23 64 377 0.000 0.000 0.001
> > The ntp.conf on server is,
> > driftfile "C:\Program Files\NTP\etc\ntp.drift"
> > tos orphan 5
> > The ntp.conf on all 3 clients is(except the drift file location),
> > driftfile "C:\Program Files (x86)\NTP\etc\ntp.drift"
> > server 10.200.98.51 iburst
> > server 127.127.1.0
> > fudge 127.127.1.0 stratum 12
> The "clients" should not be using the Undisciplined Local Clock.
> > logconfig = all
> > logfile "C:\Program Files (x86)\NTP\etc\ntp.log"
> > statsdir "C:\Program Files (x86)\NTP\etc\log\"
> > statistics loopstats peerstats clockstats
> > filegen loopstats file loopstats type day enable
> > filegen peerstats file peerstats type day enable
> > filegen clockstats file clockstats type day enable
> > At beginning, the configuration file on client has only first 2 lines,
> > the lines from server 127.127.1.0 were added for debugging purpose.
> That is a misuse of the Undisciplined Local Clock.
> > The same thing happened two years ago, on different computer hardware.
> > At that time,I select undiscipline clock on server, and want 5 clients
> > sync to server. But after days running, the clients out of sync with
> > server, chasing their own clock. So I have to disable ntpd, and add
> > ntpdate to crond to sync the time by force.
> > Could any one give me some clues on this issue.
> Don't use the Undisciplined Local Clock on any ntpd which does not serve
> time to others.
> Steve Kostecke <koste... at ntp.org>
> NTP Public Services Project -http://support.ntp.org/
More information about the questions