[ntp:questions] No syncro

Steve Kostecke kostecke at ntp.isc.org
Fri Feb 16 15:55:45 UTC 2007


On 2007-02-16, Juan C. Gonzalez <jcgonzalez at ono.com> wrote:

> I have update ntpd, now I have version 4.2.4.

<snip>

> #ntpdate emaddns1.endesa.es
> 16 Feb 09:18:51 ntpdate[7929]: step time server 172.29.8.4 offset
> 92.118018 sec

This means that the NTP port (123/UDP) is open between your ntpd and
that remote time-server.

> # /usr/local/bin/ntpd -g
>
> # ps fax|grep ntpd
>  7932 ?        Ss     0:00 /usr/local/bin/ntpd -g
>
> # ntptrace
> localhost: stratum 16, offset -0.000074, synch distance 0.00046
> 73.78.73.84:    *Timeout*

If you ran ntptrace immediately after starting ntpd you did it much too
soon. Please allow your ntpd to run for about 10 or 15 minutes before
posting data about it.

> # ntpq -p
>      remote           refid      st t when poll reach   delay
> offset  jitter
>==============================================================================
> endesa.endesa.e emball601.endes  2 u   51   64    1    1.011
> 11914.6   0.002
> emaddns3.endesa .INIT.          16 u    -   64    0    0.000
> 0.000   0.000

It looks like your ntpd is still within the first poll period. So you
didn't wait long enough. Please allow your ntpd to run for about 10 or
15 minutes before posting data about it.

You should see the number in the reach column at the end of each poll
period. And, after enough sucessful polls of your remote time servers,
ntpd will select a sys_peer and mark it the the "*" tally code in left
column.

If you want to speed up ntpd's initial sync you must append 'iburst' to
your server lines.

> ntpq> rv
> status=c011 sync_alarm, sync_unspec, 1 event, event_restart,
> version="ntpd 4.2.4 at 1.1437 Wed Feb 14 08:29:41 UTC 2007 (1)",
> processor="i686", system="Linux/2.6.5-7.244-smp", leap=11, stratum=16,
> precision=-19, rootdelay=0.000, rootdispersion=1.110, peer=0,
> refid=INIT, reftime=00000000.00000000  Thu, Feb  7 2036  7:28:16.000,
> poll=6, clock=c97fe7c5.1e61672d  Fri, Feb 16 2007  9:20:21.118,
> state=1,
> offset=0.000, frequency=0.000, jitter=0.002, noise=0.002,
> stability=0.000

You didn't wait long enough. Please allow your ntpd to run for about 10
or 15 minutes before posting data about it.

Remember, it takes time to determine the correct time.

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




More information about the questions mailing list