Subject: Re: ntp is very slow to be operational
To: Thierry Lacoste <th.lacoste@wanadoo.fr>
From: Quentin Garnier <cube@cubidou.net>
List: netbsd-help
Date: 10/24/2005 18:48:14
--7vLGWvOrvbSM0Ba8
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Oct 24, 2005 at 01:25:03PM +0200, Thierry Lacoste wrote:
> I'm trying to set up a NTP server on a sparc64 under 2.0.
> IIRC I already experienced some delay between startup of ntpd
> and it's availability. But here it is _very_ long.
>=20
> After booting the server,
> when I try 'ntpdate test' on a client I get this:
>=20
> 24 Oct 13:11:34 ntpdate[1658]: ntpdate 4.2.0-r Sun May  8 18:55:38 CEST 2=
005
> (1)
> Looking for host test and service ntp
> host found : test.miage.univ-paris12.fr
> [...]
> 194.214.13.2: Server dropped: strata too high
> server 194.214.13.2, port 123
> stratum 16, precision -17, leap 11, trust 000
> [...]
> 24 Oct 13:11:34 ntpdate[1658]: no server suitable for synchronization fou=
nd
>=20
> After about 10 minutes the fllowing messages appear on the server's conso=
le:
>=20
> Oct 24 13:08:28 test ntpd[270]: time reset +0.992103 s
> Oct 24 13:08:28 test ntpd[270]: kernel time sync disabled 0041
>=20
> Then after 10 more minutes ntpdate is OK:
> [...]
> stratum 3, precision -17, leap 01, trust 000
> refid [194.214.13.2], delay 0.02603, dispersion 0.00000
> transmitted 4, in filter 4
> reference time:    c707406e.57a493c8  Mon, Oct 24 2005 13:13:50.342
> originate timestamp: c70740b3.08e10cf5  Mon, Oct 24 2005 13:14:59.034
> transmit timestamp:  c70740b3.0b1feeb2  Mon, Oct 24 2005 13:14:59.043
> filter delay:  0.02611  0.02603  0.02603  0.02603
>          0.00000  0.00000  0.00000  0.00000
> filter offset: -0.00906 -0.00908 -0.00908 -0.00908
>          0.000000 0.000000 0.000000 0.000000
> delay 0.02603, dispersion 0.00000
> offset -0.009080
>=20
> 24 Oct 13:14:59 ntpdate[2002]: adjust time server 194.214.13.2 offset=20
> -0.009080 sec
>=20
> Any tip?

Ntpd is a complex beast which aims to keep track of time very
accurately.  That means it takes time to make sure it is properly
synchronised with the remote servers, and to guess the flaws (i.e.,
mostly the drift) of the internal clock.

And yes, that might take up as long as 10 minutes.

--=20
Quentin Garnier - cube@cubidou.net - cube@NetBSD.org
"When I find the controls, I'll go where I like, I'll know where I want
to be, but maybe for now I'll stay right here on a silent sea."
KT Tunstall, Silent Sea, Eye to the Telescope, 2004.

--7vLGWvOrvbSM0Ba8
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (NetBSD)

iQEVAwUBQ10QTtgoQloHrPnoAQJy9wf/QErKW3Kgihz3xhJkuhFLKVXV2a9/5JH9
8FnDBt8ei5Yz2wm2a4bVjSsyO96a4g/OpZTLMju7FGIjxf3ApvvdOPvCs2CY3NC0
J79r3beEiiLW73IIHoUOuc5coOcGqcprh47GmlfXyWcguqoVIAMFSBFE2KUaNhYI
XF8TL2dIsj4FvVdg6X3XZxMVgwDTdAo1Ec9FjwTcLczWj4o2pe9JL9s4k1yLE/+U
TcmfROZyIljTYc9KsNwIEnuL/CluuNsgOG5TwZCKdF1KFg9gWpyGlo335FY0GmQl
qyTIV3DSG/0FipMHcdLom1WpyvLBLc9vCVg8BpqEycyVCMAMQ1q/qg==
=A21I
-----END PGP SIGNATURE-----

--7vLGWvOrvbSM0Ba8--