| Re: [chrony-users] Surprising result of connectivity failure |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-users] Surprising result of connectivity failure
- From: Watson Ladd <watson@xxxxxxxxxxxxxx>
- Date: Tue, 18 Feb 2020 14:53:46 -0800
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cloudflare.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=CNemR8mdYYMK670u96fQe5E1RIWHkL2vzu0uXVHDEbc=; b=h8LCY7jqQwybxU45LsB5KxWNCh3+nIWh7q6Nx/owBI+RkYv/Z3koexeCwlUw57D5pB tKVJEk3u1FmZDt4oYYaxFmyMRy00KLLu4KK4T+uyDhNzNRhzqbIAopOJjaHOcSi+Pnbj WdMIKXIVWIfjCU5GaE3EXh76J7xkhbnl7AmcU=
On Mon, Feb 17, 2020 at 12:25 AM Miroslav Lichvar <mlichvar@xxxxxxxxxx> wrote:
>
> On Thu, Feb 13, 2020 at 04:22:36PM -0800, Watson Ladd wrote:
> > Dear chrony-users,
> >
> > I'm writing because of a mysterious occurrence a few weeks ago: a few
> > of our stratum 1 sources were unreachable, and chrony did not
> > synchronize the clock, despite reachable servers. The synchronization
> > distance continued to rise, until the servers were available again and
> > one was elected.
>
> Did the other sources have comparable root distance to the servers
> that become unreachable? chronyd will not immediately reselect to a
> significantly worse source. It waits until the estimate of the local
> clock error becomes comparable to the sources that are available.
So I sadly only have chronyc sources output, not chronyc ntpstats that
would help me answer this question definitively. From the data I have
it seems as though one unaffected stratum 1 was a short distance away,
but I'll keep this in mind and revise our internal documentation to
remember this for the future.
Sincerely,
Watson
--
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.