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
-Original Message-
From: Bill Unruh [mailto:un...@physics.ubc.ca]
Sent: Tuesday, November 28, 2017 9:14 PM
To: chrony-users@chrony.tuxfamily.org
Subject: [External] RE: Re: [chrony-users] Chrony 3.1 refuses to sync with ntp
server
On Tue, 28 Nov 2017, Assaf Vainsencher wrote:
Thank you. I
On Tue, 28 Nov 2017, Assaf Vainsencher wrote:
Thank you. I confirmed that using maxdistance 16 fixed the issue we're seeing.
Looks like our root dispersion is just over 10 which is why we were seeing the
issue with the default setting in version 3.1.
Off topic, but I am really surprized
: Tuesday, November 28, 2017 1:52 PM
To: chrony-users@chrony.tuxfamily.org
Subject: [External] Re: [chrony-users] Chrony 3.1 refuses to sync with ntp
server
On Tue, Nov 28, 2017 at 06:10:29PM +, Assaf Vainsencher wrote:
> We recently updated from RHEL 7.3 to RHEL 7.4 which updated chr
