[Question] chronyc tracking shows large offset
zc z <[email protected]> Wed, 5 Nov 2025 16:41:06 +0800
| Newsgroups | gmane.comp.time.chrony.user |
|---|---|
| Message-ID | <CAKCDRHV2vOrTdGQZQvdiJnj1L=mmB0k9myiX=4eHGdBHtE8rng@mail.gmail.com> |
--000000000000741be90642d4e9c2 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable version: chrony 4.4 OS: Ubuntu 18.04 I have a question regarding the =E2=80=9CLeap Status=E2=80=9D field in the = chronyc -n tracking command. My chrony.conf configuration is as follows: *server 192.168.46.99 iburst minpoll 2 maxpoll 2* *driftfile /var/lib/chrony/drift* *makestep 0.05 3* *maxdistance 1.6* 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. 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? Thank you for your help. Best regards --000000000000741be90642d4e9c2 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div><p>version: chrony 4.4</p><p>OS: Ubuntu 18.04</p><p><= br></p><p>I have a question regarding the =E2=80=9CLeap Status=E2=80=9D fie= ld in the=C2=A0chronyc -n tracking=C2=A0command.</p><p>My=C2=A0chrony.conf= =C2=A0configuration is as follows:</p></div><div><i>server 192.168.46.99 ib= urst minpoll 2 maxpoll 2</i></div><div><i>driftfile /var/lib/chrony/drift</= i></div><div><i>makestep 0.05 3</i></div><div><i>maxdistance 1.6</i></div><= div><br></div><div><p>I ran a script to record=C2=A0chronyc -n tracking=C2= =A0output every 5 seconds. When I unplugged the network cable and waited fo= r 20 hours, I observed that the Leap Status remained=C2=A0Normal. At that t= ime, the=C2=A0rootdelay=C2=A0was=C2=A01.00000238 ms=C2=A0and=C2=A0root disp= ersion=C2=A0was=C2=A01.338544011 s. The accumulated estimated error exceede= d 1.6 seconds (maxdistance), yet the Leap Status did not change to=C2=A0Not= synchronized.</p><p>Could you please clarify why the Leap Status remains= =C2=A0Normal=C2=A0under these conditions?=C2=A0How long does it take for th= e Leap Status to change, or how can I configure it to detect anomalies, suc= h as a network disconnection, and switch to Not synchronized?</p><p><br></p= ><p>Thank you for your help.</p><p></p><p>Best regards</p></div></div> --000000000000741be90642d4e9c2-- -- To unsubscribe email chrony-users-request-kWFZVVI9zxvPqho9SqqRMmD2FQJk+8+b@public.gmane.org with "unsubscribe" in the subject. For help email chrony-users-request-kWFZVVI9zxvPqho9SqqRMmD2FQJk+8+b@public.gmane.org with "help" in the subject. Trouble? Email [email protected]