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.
-----Original Message----- From: Miroslav Lichvar <mlich...@redhat.com> Sent: Monday, January 2, 2023 12:00 To: chrony-users@chrony.tuxfamily.org Subject: RE: [EXTERNAL][chrony-users] chrony switch source issue CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe. On Thu, Dec 22, 2022 at 01:35:34PM +0000, Bernstein, Amit wrote: > But in case PHC source returns a failed status (for example -EIO) Chrony > will not switch the sources and will stay on PHC source for an infinite time Is it really infinite, or just taking longer that you would expect? https://chrony.tuxfamily.org/faq.html#_an_unreachable_source_is_selected -- Miroslav Lichvar -- To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org with "unsubscribe" in the subject. For help email chrony-users-requ...@chrony.tuxfamily.org with "help" in the subject. Trouble? Email listmas...@chrony.tuxfamily.org. -- To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org with "unsubscribe" in the subject. For help email chrony-users-requ...@chrony.tuxfamily.org with "help" in the subject. Trouble? Email listmas...@chrony.tuxfamily.org.
