| Re: [chrony-users] Bug report: `maxslewrate` violation by chrony |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-users] Bug report: `maxslewrate` violation by chrony
- From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Date: Tue, 6 Dec 2022 09:47:23 +0100
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1670316446; 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=U2oIaMHynFDJxgguY9mGrqSxYukL/wOutEVZ1YRv3xA=; b=QyFh16n2Tkq4Sqie+95VIZro1QJAtEUlFrE3e0AxR9lhfWQpGHlb/AS+FqMHH36Rclhv3w xLYTaj0yjvbPjyZpfsePiSKOW3QxJQ6zokVNyZ7hUEnupkJXcmfORKK1Cbc7Yfdwt2NaPr YJcUB834DjhDFrdk1EDw5pPEp3EBBPk=
On Mon, Dec 05, 2022 at 05:14:10PM -0800, Adam Snaider wrote:
> Hi folks,
>
> I wanted to report a bug. We use chrony for time synchronization and we
> have a strict requirement that forces us to limit the slew rate to no more
> than 250ppm. We noticed that in some conditions, chrony exceeds this limit
> by >10x. I've collected an strace that shows chrony is indeed the culprit
> as it is calling the clock_adjtime syscall with the tick and frequency set
> to 9980 and -140765 which corresponds to roughly -2002ppm.
The values passed to clock_adjtime() correct both the estimated
frequency error (drift) and phase error (slew). What frequency do you
see reported in the tracking log when this happens?
If I understand your test correctly, you are simulating an unstable
clock, which could be measured as a large frequency offset.
If you need to limit the sum of the two, you will need to set also
the maxdrift option.
--
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.