Re: [chrony-users] Clock selection algorithm |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-users] Clock selection algorithm
- From: chrony-users@xxxxxxxxx
- Date: Fri, 11 Mar 2022 18:16:25 +0100
- Dkim-signature: v=1; a=rsa-sha256; c=simple/simple; d=pe1chl.nl; s=pe1chl; t=1647018986; bh=HHNRg8jk/YAKeFO15ESHYarar7LmqoVcj4pCu6SAFzg=; h=Date:Subject:To:References:From:In-Reply-To:From; b=e+B61zKHiV2e2Tl7VBzNDWKtexcchPRltGmPJ5oJmOZDF5uHXu35Pa7kYvYsd3Z0H g3Qlfrg5QF+MrVUB678zmDwIS1zO+Rkaq7TxPUsvTQKXNSBp7gVeHDxv+XEBE9ihwX /Owhyhbt9Rm7XMmRofvBep6gYvUblDB/saZU8g74fcdxvfG9FH1UPfpjG7f987cu2s TV6hX+6GhHggDlhCQZ7VisNejZH/urRQ6xRonvGUQSfJ/Q88BA4PD4Xw+NUtdxBL8Y LXjds/Bkz8tb/7BO0l7bT+SWHrzx8WEUct38k7PHlHgJM5oYvVvd7/aniRiR4qIvW0 S6daYFmUXqItw==
- Organization: PE1CHL
I have changed the logging config like this:
# tunable parameters
driftfile /var/lib/chrony/ntp.drift
logdir /var/log/ntpstats
-log statistics measurements tracking tempcomp
+log refclocks
i.e. I was logging some other things but I wasn't really using that.
After restarting chrony (I tried this on two different systems) I have not
yet seen the problem re-occur. Looking in the refclocks logs I only see
some offsets of the e-03 order during the first minutes after startup,
not thereafter.
I will monitor the situation further to see if there it happens again.
PS: there are some issues with this mailinglist making it troublesome in
this era of SPF and DMARC.
1. it sends copies of the mail back to the submitter
2. it sends out mails with a From: header containing the original submitter's
e-mail address.
That is not really feasible anymore. It would be better when the mailinglist
sends out mail messages with a From: address referring to an address on the
mailinglist server and mentioning the submitter only in the Full Name.
On 3/7/22 10:33, Miroslav Lichvar wrote:
> On Thu, Mar 03, 2022 at 07:23:30PM +0100, chrony-users@xxxxxxxxx wrote:
>> But sometimes, probably due to interrupt latency, the offset of the PPS refclock has
>> some spikes (e.g. spiking to 1 millisecond) and in this situation the PPS clock
>> is sometimes marked as an outlier (x) because all the NTP refclocks are closer to the
>> system time than this PPS sample is. Chrony selects an NTP refclock and increases
>> the stratum. It spends some time (like 5-10 minutes) tracking the NTP servers before
>> it reselects the PPS source. This then alerts our monitoring system.
> 1 millisecond is a lot for an interrupt delay. If you enable the
> refclocks log, how many subsequent samples do you see impacted? If
> it's not too many, you could simply increase the polling interval and
> let the median filter take care of the outliers.
>
> If that doesn't work and you want to force chronyd to keep the PPS
> refclock selected, you can set a larger delay for the refclock (e.g.
> delay 0.005) to make it overlap with the other sources and avoid the
> falseticker status.
>
--
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.