Re: RE: Re: [chrony-users] Chrony 3.1 refuses to sync with ntp server

[ Thread Index | Date Index | More Archives ]

On Wed, Nov 29, 2017 at 07:12:01AM -0800, Bill Unruh wrote:
> On Wed, 29 Nov 2017, Assaf Vainsencher wrote:
> > I'm not really sure but I think as long as chrony syncs with the NTP server that it's acceptable  for our needs.  That being said, could it be that both the NTP server (windows 2008R2) and the clients are on Vmware virtual machines?  If is there a setting for the vmware VM or chrony to improve the dispersion?  What's the downside of high dispersion?
> > 
> The downside is potentialy bad time. If the roundtrip for example is 5 sec and
> has a 2 sec asymmetry (1.5 sec up and 3.5 down) then your time will be off by
> a second, etc.(Your sneakernet deliverer stolls one way and runs the other).
> A better idea is to get a cheap Linux machine or bsd machine (eg a Raspberry
> Pi) and use it as your time delivery machine instead of bad Windows machines.

In this case it seems it was the root dispersion what caused the
source to be ignored, so rather than NTP messages spending too much
time in the network, the server (or its servers) has an unstable clock
or its update interval is too long.

Miroslav Lichvar

To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx 
with "unsubscribe" in the subject.
For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx 
with "help" in the subject.
Trouble?  Email listmaster@xxxxxxxxxxxxxxxxxxxx.

Mail converted by MHonArc 2.6.19+