[ntp:questions] Re: ntpd local synchronization fails?

Wilhelm Greiner wilhelm.greiner at web.de
Wed Nov 16 10:04:50 UTC 2005


* Wilhelm Greiner <wilhelm.greiner at web.de> schrieb:
>  Hi,
>  * Wilhelm Greiner <wilhelm.greiner at web.de> schrieb:
> >  Hi,
> >  * Danny Mayer <mayer at ntp.isc.org> schrieb:
> > >  Wilhelm Greiner wrote:
> > 
> > > > i have an ntp multicast Client running, but it fails
> > > > to synchronize his local clock, ntp as Service is
> > > > running and delivering the right time. Only the
> > > > local clock will not be set.
> > > > NTP Version 4.1.2 is running on Linux 2.6.12.
> > > > I cant use ntpd Version 4.2.x, there is a multicast
> > > > Client bug.
> > >  Not any more. Please upgrade to the latest ntp-dev snapshot. The fix
> > >  should be in there.
>   
>  I have now installed the latest dev-snapshot.
>  Multicast works exactly as with 4.1.x.
> 
>  ntpq -p:
>       remote           refid      st t when poll reach   delay   offset  jitter
> ==============================================================================
>   LOCAL(0)        LOCAL(0)         6 l   11   64  377    0.000    0.000   0.015
>  *192.168.1.9     192.168.100.5    2 m   16   64  377    0.015  -51.568  19.452
>   
>  But the Time on the 192.168.100.5 and also on 192.168.1.9 is absolutely
>  correct, the time on this machine ist NOT.
> 
>  It has the wrong time 600 sec in the future, i can see it via date and the
>  machine also delivers the wrong time, it is in 600 sec since 24 hours.
> 
>  Also i cant see any syslog messages since yesterday.
> 
>  I think this cant be an Linux Problem if it not only doesnt set the LOCAL
>  clock, it too delivers the wrong time.

As an test i have give an unicast connection to the same Server and it now
correcly say "-608582" as offset, and not "-51.568". (Same machine, same ntpd)
and sets the time correctly.

mfg Wilhelm




More information about the questions mailing list