| 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: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Date: Mon, 17 Feb 2020 09:25:00 +0100
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1581927908; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=d8o8qXVqQZukLlqkK7jFKiyw0mGXlPdxsO5Jb+HdL0g=; b=LXTRwlno6jqZlwUbvEW4SOEcY2qTC9OSJAHxyNDc1shFIf8TFc1ELUdKsx5LN4pt/6RCG1 8HyKY5pEHhj/RSGuZ/lGAmMPe9ETB04wQipLTCuMo4mVgsZ4vh9AlYx5dNz17gBBPmRxhk NliwQ9GBdhA4dgIFC+AzoZmYuUUBkFI=
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.
--
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.