[ntp:questions] No syncro

David Woolley david at djwhome.demon.co.uk
Fri Feb 16 21:54:03 UTC 2007

In article <1171614276.639806.269320 at h3g2000cwc.googlegroups.com>,
Juan C. Gonzalez <jcgonzalez at ono.com> wrote:

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

> endesa.endesa.e emball601.endes  2 u   51   64    1    1.011
> 11914.6   0.002

> poll=6, clock=c97fe7c5.1e61672d  Fri, Feb 16 2007  9:20:21.118,

You seem to have lost almost 12 seconds (not, of course 12 thousand - you
should completely ignore the response that suggested that these values
are seconds) in only a few minutes.  As well as making sure that allow
ntpd to stabilise before trying to diagnose, you should fix this problem
before running ntpd.  ntpd cannot cope with more than somewhat under 30ms
per minute.  12 seconds in about that time is unsupportable.

(Alternatively you have time servers that don't agree with each other,
which means one or all of them are broken.  The normal way of achieving this
is to make them all agree with UTC.)

More information about the questions mailing list