| [chrony-users] Surprising result of connectivity failure |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Subject: [chrony-users] Surprising result of connectivity failure
- From: Watson Ladd <watson@xxxxxxxxxxxxxx>
- Date: Thu, 13 Feb 2020 16:22:36 -0800
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cloudflare.com; s=google; h=mime-version:from:date:message-id:subject:to; bh=BopNmE+tqVvawvKQr0wXiZVH6UBnkYmph1gTWGrHxaw=; b=oTlsE6AcrC6QNCn96tPu7vaN/a9LyuENSRxtJdRJp3YTEzwJyNPjHWWpdvJ/cc8/P4 XitOjjFYkuzDvcsWrxDej7011ynCAIlLHpRRRyoA2McSpb0e+8imHZHvV/E8CVF2FSVv r7pXk+mzrme1L8zef7JrjVuMhYN8LPvxdL26Q=
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.
I'm sure this behavior was correct, but trying to understand why it
happens. From my admittedly cursory perusal of the source code, I
would think that a server ends up elected or all servers are declared
falsetickers. But this doesn't seem to be what happens.
Sincerely,
Watson Ladd
--
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.