[ntp:questions] Can't get time to sync with local time server

Steve Kostecke kostecke at ntp.isc.org
Fri Dec 15 14:44:27 UTC 2006

On 2006-12-15, Richard B. Gilbert <rgilbert88 at comcast.net> wrote:

> Arty wrote:
> [---=| Quote block shrinked by t-prot: 67 lines snipped |=---]

Please trim the quoted material in your article.

>> As far as monitoring goes, i think i can just check to make sure my
>> stratum is not < 16 right ?
> Try "ntpq -p" at least thirty minutes after you start ntpd.

It is not necessary to wait thirty minutes before using ntpq. You will
begin to see information about your ntpd peer associations almost

The amount of time that it takes for ntpd to select a sys-peer (i.e.
become synced) depends on a number of factors. But, in general, a
sys-peer should be selected within about 8 minutes after ntpd starts.

If you are using 'iburst' on your server lines _and_ you "pre-set" your
system clock, by using ntpdate or ntpd -gq, before starting ntpd you
may see the '*' tally code next to your sys-peer (i.e. the chosen time
server) in as little as 15 - 30 seconds.

If you are not using 'iburst' and/or ntpd has to step the clock during
the initial setting you will not see the '*' tally code until ntpd has
been operating for about 8 minutes.

Once you see the '*' your ntpd is operating at the stratum of that peer
+1. If your sys-peer is at stratum 2 your ntpd is at stratum 3. And so

> "t" is type; "l" for local and "u" for ?? (maybe unknown)

unicast (i.e. the "normal" client <-> server association)

Steve Kostecke <kostecke at ntp.isc.org>
NTP Public Services Project - http://ntp.isc.org/

More information about the questions mailing list