| Re: [chrony-users] chrony switch source issue |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-users] chrony switch source issue
- From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Date: Mon, 2 Jan 2023 13:42:02 +0100
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1672663325; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=5UHL6/1wJqvLGnzcsVl0MMslzCEZmufYV1dY5IclnSs=; b=W7jPUwRR59HI06bMsI58n1FOzaGjTUEyXww+YC/YG4MEjfFoEe9XkZR0AnlanbqT0tnDJL lJtRdjEk4O0S2pRN6ZrpF7iu0TtRJlgwA5uqHC/u9hDVvqtw6lJZSIc5CGBKzqOnIvnpbw 06Ca7X+HaX4hcRVcHtIsUtitEOPM8wQ=
On Mon, Jan 02, 2023 at 12:22:56PM +0000, Bernstein, Amit wrote:
> As both source timestamp (NTP and PHC) are very close to each other
> And according to chrony faq: "It will let the clock run free for as long as its estimated error (in terms of root distance) based on previous measurements is smaller than the estimated error of the second source, and there is still an interval which contains some measurements from both sources."
> Chrony should have replaced the source from PHC to NTP after no more than several msec, I have waited about an hour and still saw chrony getting stucked on PHC source.
Please post output from chronyc sources, sourcestats, ntpdata,
selectdata.
--
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.