Re: [chrony-users] [Question] chronyc tracking shows large offset

[ Thread Index | Date Index | More chrony.tuxfamily.org/chrony-users Archives ]


On Wed, Nov 05, 2025 at 04:41:06PM +0800, zc z wrote:
> I ran a script to record chronyc -n tracking output every 5 seconds. When I
> unplugged the network cable and waited for 20 hours, I observed that the
> Leap Status remained Normal. At that time, the rootdelay was 1.00000238
> ms and root dispersion was 1.338544011 s. The accumulated estimated error
> exceeded 1.6 seconds (maxdistance), yet the Leap Status did not change
> to Not synchronized.

maxdistance is for source selection. It doesn't change anything about
the local clock. (A root distance of 1ms/2 + 1.3s is not larger than
1.6 seconds.)

> Could you please clarify why the Leap Status remains Normal under these
> conditions? How long does it take for the Leap Status to change, or how can
> I configure it to detect anomalies, such as a network disconnection, and
> switch to Not synchronized?

It will not change. Once the clock is synchronized, it stays
synchronized. That's how NTPv4 clients are supposed to work. It's up
to you to decide what root distance is acceptable for you. If you need
to detect network problems, you should check reachability reported by
chronyc sources.

-- 
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.


Mail converted by MHonArc 2.6.19+ http://listengine.tuxfamily.org/