[ntp:questions] Re: ntpd local synchronization fails?
wilhelm.greiner at web.de
Tue Nov 15 09:09:22 UTC 2005
* Tom Smith <smith at cag.zko.hp.com> schrieb:
> Wilhelm Greiner wrote:
> > * Harlan Stenn <stenn at ntp.isc.org> schrieb:
> > [root at ntp log]# ntpq -p
> > remote refid st t when poll reach delay offset jitter
> > ==============================================================================
> > LOCAL(0) LOCAL(0) 6 l 50 64 377 0.000 0.000 0.015
> > *192.168.1.9 192.168.100.5 2 m 2 64 377 0.015 -21.714 16.686
> It has syncronized to the lower stratum (real) server. That's what
> it's supposed to do.
It _should_ synchronize to the 192.168.100.5 Server, right.
> Were you thinking that if it is not synchronized to the local clock,
> the local clock would not be set? That's not the case. The local
> clock is always set UNLESS NTP is synchronized to the local clock.
> If this is only a client, it shouldn't have the local clock configured
> as a server in the first place.
It is A Multicast Client and a Unicast Server, yes it acts as Server too.
Problem iss that it doesnt change the time, when i, for example, set
via date the Time to 10 Minutes in the future, then start ntpd.
It doesnt, also after a day or so, set the correct time.
Im searching for Entries like "time set -0.042078 s" but i only
found "time set 0.000000 s\nsynchronisation lost" in the messages log.
Nothing more, its the last message then.
Can it be that the jumps are to high for ntpd/Linux Kernel?
It is a satellite Link with high delay.
The ntpd looks it _serves_ the correct Time, but it doesnt set the
In the posting above i forgot to show the config:
# Multicast Addresse
# lokale Hardware Uhr als Fallback
fudge 127.127.1.0 stratum 6
# Pakete sind verzoegert unterwegs
# Authentifizierungs Schluessel
More information about the questions