Re: [chrony-users] Sources marked as falseticker which shouldn't be |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-users] Sources marked as falseticker which shouldn't be
- From: Yuezhen LUAN <eggcar.luan@xxxxxxxxx>
- Date: Tue, 7 Jan 2025 17:33:05 +0800
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1736242397; x=1736847197; darn=chrony.tuxfamily.org; h=content-transfer-encoding:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=02R10E2RkCM0y4hnUjHSSRqSbLF+dKrEJiM7N65WuXg=; b=L+llGlaD6ldZCp35rIQEuD9thRmXvStnAHwzkXKTazXG3wK30tyoJD9YyjC3vdNTac eK9ZhvDPEabFyVZiiII345UChOm+/1S8mZFV7vQdZbChWHeHNjTmlAMhp9+UV06Wp+fC V9/rPF2ug4Rvp17ntnZVnJHk9Bn1hSOKF5fgHLpq9ONMEwMKIQY8ITRhrwdWjjGK/tPE a/SUQmp+3XbHXW0sLSU3N8XGFpXS+NEprW81wlgDXntQ14egkm+RdIQp5b/bqiJpFBdq ibDKUZr9PgxtrkgzZuqVCaE4ND5QzYGmQ0GCOvIEdfJNBkySMz3B72txBC9RnEMcollD YaHg==
Thanks Miroslav, that explains the behavior, I'll try explain this to our SA.
We can solve this by increase the three server's dispersion to 10ms or larger
Miroslav Lichvar <mlichvar@xxxxxxxxxx> 于2025年1月7日周二 17:10写道:
>
> On Mon, Jan 06, 2025 at 06:12:53PM +0800, Yuezhen LUAN wrote:
> > But some of the chrony clients also mark B as falseticker, some marked B as
> > combined, some marked B as selectable but not combined, and all chrony
> > clients select C as current time source.
> >
> > Offset between B and C are small enough(currently 200us~300us). According
> > to selection algorithm, I think B shouldn't be falseticker? 'chronyc
> > selectdata -a -v' shows like this:
> >
> > [image: chronyc_selectdata.png]
>
> That output shows that the sources A and B don't have any overlap in
> their intervals and both overlap with C. This is a corner case in the
> chrony selection algorithm that IIRC is handled differently than in
> ntpd.
>
> That overlap between A and C is only about 30 microseconds. A small
> difference in the network delay, timestamping, etc could cause that
> overlap to disappear, which would make make B lose the falseticker
> status. That will also happen if A drifts further away from B and C.
>
> --
> 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.
>
--
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.