| RE: [chrony-users] [Question] chronyc tracking shows large offset |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: Bill Unruh <unruh@xxxxxxxxxxxxxx>, "chrony-users@xxxxxxxxxxxxxxxxxxxx" <chrony-users@xxxxxxxxxxxxxxxxxxxx>
- Subject: RE: [chrony-users] [Question] chronyc tracking shows large offset
- From: MUZZULINI Frank <Frank.MUZZULINI@xxxxxxxxxxxxxx>
- Date: Wed, 5 Nov 2025 10:28:58 +0000
- Accept-language: en-US
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=frequentis.com; dmarc=pass action=none header.from=frequentis.com; dkim=pass header.d=frequentis.com; arc=none
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector10001; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=/ufCFus9MoKmuz0fHkn0mKUOn51exxuKIVPDEsAq6/M=; b=YVX8p/mwiHfpZx0G5xzWXMfTAZMMCNEPrkxiUFvPthVQyGfodGDeU9bmIdMrY9X4jCF2+fMskEisbf0/iEHQ0ozd/8HkMTEsiV1HyqgGsd4zYHoVhQjVSNw7VWfVbks3fYOGJCyIBP5nLdAohp90QLeoxksupnjlngNifm9SyanBD/j+5QlhJ3KUzFdmg4FsXox4943ACtBwARzhUeW35Ak6wdqXH8vtA/2n403ieF+MclZuLvLI72KDejfddmmX9i9Gx0QzZsYhRHC2uYysnxWkBMThTlDPJX9RvWj163XHqYfoFEkHXzmT8ieunLcIYjmWZC66Ejpg7eltjsTJoQ==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector10001; d=microsoft.com; cv=none; b=ThXozow7WsC7QYkuiemzPMFyWpnUK3knA7x8KEn5BAmmBdDOcA+HqhPkP5kV+rpjaQ++jzkGzLnWx/VHS7YWOqO9IqxMym7h7Jd5O5slscx5oWPShJpXB3mEkn85RILQPBvN6o422Q1wVxW2awcq1VFb0i3qwBrRN+hBq05UORDJmPpcFn8ZA3f3G4sSEQ7EdXOLzNDHAEiKXcwcz0kJBlDZk+x+VGe4u+0GyW/hqsvJEorynbOHWiWauBfVTS5+i+/MgicGcc5J7n29H11FyScB48aqoGT+ToVTm/1QaYztQw+i2ynq2EiB7EAHfj6PiKlaprgFhcqc+IayjeYj6w==
- Authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=frequentis.com;
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=frequentis.com; s=FRQ1; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=/ufCFus9MoKmuz0fHkn0mKUOn51exxuKIVPDEsAq6/M=; b=q7VBV3L6ApSe3PSVc6dsONgdk71q3tKImaLemRIGU7Ky5ZYbXeGjecZ5 DyKYq9ij/HyB8SaCgwfK+B6UQ2gx2jHANVOkjuG/XNjzCTcm6vK1oRkw3 zw94hssV78lE/8kgqEzie//Y9MZCwNl6nJB+Jm9Y6ij4T585LqoCNhoOP w1IxzLLuaPnLckbs+SR5eLqP8d3dbqQI7DfC96BmGP98s3NJCGyzSNOQJ XpMXan+Jp39vHn7KaepsHj/v+4Ospj6zDeslf/YsdQmEXjqZpObUA/cjM 0cUJr2Bt2C0buWDkmgdGRNy5W+KFfY54tdDNPSrs20iOg/E0SyQnc+NEf A==;
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=frequentis.onmicrosoft.com; s=selector2-frequentis-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=/ufCFus9MoKmuz0fHkn0mKUOn51exxuKIVPDEsAq6/M=; b=E7A9yZX+CQ3BE3Ndvf6ql/1t1e/TfMnzfGYpen/RsUsmcNecKXlOsfTKep3Njpb42xefD4ZiEEEzDtv6CFiVqnc337+EZqHsavwQHKhdGReYGj0uIOy1czhxMb3LnH75/6yb6H6ypeE2MZfS3PxOvQkuqZwK1i9C37EsUei6pY4=
- Msip_labels: MSIP_Label_50bef7d4-e22d-4ab7-80f8-95d0deb51eea_ActionId=c5b705ec-660e-4e9e-9e69-3e26f7626172;MSIP_Label_50bef7d4-e22d-4ab7-80f8-95d0deb51eea_ContentBits=0;MSIP_Label_50bef7d4-e22d-4ab7-80f8-95d0deb51eea_Enabled=true;MSIP_Label_50bef7d4-e22d-4ab7-80f8-95d0deb51eea_Method=Standard;MSIP_Label_50bef7d4-e22d-4ab7-80f8-95d0deb51eea_Name=Frequentis General;MSIP_Label_50bef7d4-e22d-4ab7-80f8-95d0deb51eea_SetDate=2025-11-05T10:20:43Z;MSIP_Label_50bef7d4-e22d-4ab7-80f8-95d0deb51eea_SiteId=4a636d6a-7c5d-4373-a76b-698cfd77431f;MSIP_Label_50bef7d4-e22d-4ab7-80f8-95d0deb51eea_Tag=10, 3, 0, 1;
- Thread-index: AQHcTjaDNx5eCc8c3EmSOrVSNdt9J7Tj30Kw
- Thread-topic: [chrony-users] [Question] chronyc tracking shows large offset
I think zc doesn't understand what leap status is.
@ZC:
Leap status tells you whether a leap second has been announced, which probably won't happen for years to come.
If your system exceeds the configured maxdistance, the stratum value will change.
Good is stratum of the server + 1
Bad is stratum 16 or your configured local stratum, if you have configured one.
Btw, I hope you are using a local server. "minpoll 2 maxpoll 2" creates quite a lot of queries.
Regards,
Frank
-----Original Message-----
From: Bill Unruh <unruh@xxxxxxxxxxxxxx>
Sent: Wednesday, 5 November, 2025 10:28 AM
To: chrony-users@xxxxxxxxxxxxxxxxxxxx
Subject: Re: [chrony-users] [Question] chronyc tracking shows large offset
*EXTERNAL source*
Not sure what you think the problem is. The leap second notification is sent out by NIST I beleive, and the various sources will send it out as pat of the ntp packet. Change to leap second has nothing to do with your machine. If you unplug it, then there is no way your machine can know what the leapstatus is.
so why should it change it. Note also if your machine is unplugged it cannot know what the time is, except from itself.
William G. Unruh __|__Hagler Fellow, Distinguished |_Tel:UBC +1(604)822-3273
Physics&Astronomy _|__ Research Prof, IQSE |__ US +1(979)7399950
UBC, Vancouver,BC _|_ TAMU4242, 578 University Dr |_ unruh@xxxxxxxxxxxxxx Canada V6T 1Z1 ____|__College Stn, Tx, USA 77843 _|_www.theory.physics.ubc.ca I cannot reply to emails from outlook or hotmail or other microsoft domains.
On Wed, 5 Nov 2025, zc z wrote:
> [CAUTION: Non-UBC Email]
>
> version: chrony 4.4
>
> OS: Ubuntu 18.04
>
>
> I have a question regarding the “Leap Status” 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
>
>
>