| RE: [chrony-users] chrony switch source issue |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: "chrony-users@xxxxxxxxxxxxxxxxxxxx" <chrony-users@xxxxxxxxxxxxxxxxxxxx>
- Subject: RE: [chrony-users] chrony switch source issue
- From: "Bernstein, Amit" <amitbern@xxxxxxxxxx>
- Date: Mon, 2 Jan 2023 14:42:59 +0000
- Accept-language: en-US
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=amazon.com; i=@amazon.com; q=dns/txt; s=amazon201209; t=1672670585; x=1704206585; h=from:to:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version:subject; bh=Pkp0NlwowvuwZawTad0HaBwo7eFOxY4MS6v0Ult5qxw=; b=c4GYlHjIxxFF+T2MUtihFGMn8t/Y+D/LO4UV8dHkeWYlpT8Mhuz894LO CZTfiRt6C1yPA/jLMYFALB4HmwNehsUdPtqNq4yYbagtPO00fnmHHlXdX M1Ty+AU7hINIq99gHQFa9aqpEWB3kQcYjAYAmD3/1swwj15imLUsxBpgk A=;
- Thread-index: AQHZHqUQ+cN2h2kmakakJUSnQXMNsq6LEe8AgAAfTYA=
- Thread-topic: [chrony-users] chrony switch source issue
Reproduced the issue for 60 minutes
$chronyc sources
MS Name/IP address Stratum Poll Reach LastRx Last sample
===============================================================================
#* PHC0 0 4 0 60m -126ns[ -150ns] +/- 87ns
^- gotoro.hojmark.net 2 9 377 38 +201us[ +201us] +/- 67ms
^- animine.org 2 8 375 242 +244us[ +244us] +/- 78ms
^- mx.ack512.net 2 9 377 45 +5665us[+5665us] +/- 104ms
^- t2.time.bf1.yahoo.com 2 9 377 35 +2039us[+2039us] +/- 38ms
$chronyc sourcestats
Name/IP Address NP NR Span Frequency Freq Skew Offset Std Dev
==============================================================================
PHC0 7 3 86 -0.000 0.010 -384ns 91ns
gotoro.hojmark.net 30 15 61m -0.002 0.513 -114us 786us
animine.org 9 3 23m -0.348 5.037 -184us 1153us
mx.ack512.net 30 19 61m +0.005 0.247 +5730us 354us
t2.time.bf1.yahoo.com 30 16 61m -0.128 0.497 +2168us 623us
$chronyc ntpdata
Remote address : 147.182.158.78 (93B69E4E)
Remote port : 123
Local address : 172.31.42.144 (AC1F2A90)
Leap status : Normal
Version : 4
Mode : Server
Stratum : 2
Poll interval : 9 (512 seconds)
Precision : -22 (0.000000238 seconds)
Root delay : 0.012817 seconds
Root dispersion : 0.029388 seconds
Reference ID : 4294446A ()
Reference time : Mon Jan 02 14:22:30 2023
Offset : -0.000200879 seconds
Peer delay : 0.062122691 seconds
Peer dispersion : 0.000000298 seconds
Response time : 0.000058441 seconds
Jitter asymmetry: +0.00
NTP tests : 111 111 1111
Interleaved : No
Authenticated : No
TX timestamping : Kernel
RX timestamping : Kernel
Total TX : 30
Total RX : 30
Total valid RX : 30
Remote address : 45.33.65.68 (2D214144)
Remote port : 123
Local address : 172.31.42.144 (AC1F2A90)
Leap status : Normal
Version : 4
Mode : Server
Stratum : 2
Poll interval : 8 (256 seconds)
Precision : -24 (0.000000060 seconds)
Root delay : 0.023727 seconds
Root dispersion : 0.037003 seconds
Reference ID : D9B4D1D6 ()
Reference time : Mon Jan 02 14:14:50 2023
Offset : -0.001283490 seconds
Peer delay : 0.068084300 seconds
Peer dispersion : 0.000000504 seconds
Response time : 0.000045053 seconds
Jitter asymmetry: +0.00
NTP tests : 111 111 1111
Interleaved : No
Authenticated : No
TX timestamping : Kernel
RX timestamping : Kernel
Total TX : 41
Total RX : 41
Total valid RX : 41
Remote address : 136.243.229.3 (88F3E503)
Remote port : 123
Local address : 172.31.42.144 (AC1F2A90)
Leap status : Normal
Version : 4
Mode : Server
Stratum : 2
Poll interval : 9 (512 seconds)
Precision : -24 (0.000000060 seconds)
Root delay : 0.011688 seconds
Root dispersion : 0.010681 seconds
Reference ID : ED11CC5F ()
Reference time : Mon Jan 02 14:36:46 2023
Offset : -0.005664820 seconds
Peer delay : 0.175706461 seconds
Peer dispersion : 0.000000135 seconds
Response time : 0.000018308 seconds
Jitter asymmetry: +0.00
NTP tests : 111 111 1111
Interleaved : No
Authenticated : No
TX timestamping : Kernel
RX timestamping : Kernel
Total TX : 30
Total RX : 30
Total valid RX : 30
Remote address : 72.30.35.88 (481E2358)
Remote port : 123
Local address : 172.31.42.144 (AC1F2A90)
Leap status : Normal
Version : 4
Mode : Server
Stratum : 2
Poll interval : 9 (512 seconds)
Precision : -25 (0.000000030 seconds)
Root delay : 0.000107 seconds
Root dispersion : 0.000763 seconds
Reference ID : 628B853E ()
Reference time : Mon Jan 02 14:25:43 2023
Offset : -0.002038691 seconds
Peer delay : 0.074150041 seconds
Peer dispersion : 0.000000099 seconds
Response time : 0.000008982 seconds
Jitter asymmetry: +0.00
NTP tests : 111 111 1111
Interleaved : No
Authenticated : No
TX timestamping : Kernel
RX timestamping : Kernel
Total TX : 30
Total RX : 30
Total valid RX : 30
chronyc selectdata
S Name/IP Address Auth COpts EOpts Last Score Interval Leap
=======================================================================
* PHC0 N ----- ----- 63m 1.0 -3745us +3744us N
D gotoro.hojmark.net N ----- ----- 185 1.0 -53ms +52ms N
D animine.org N ----- ----- 132 1.0 -69ms +73ms N
D mx.ack512.net N ----- ----- 191 1.0 -99ms +110ms N
D t2.time.bf1.yahoo.com N ----- ----- 182 1.0 -35ms +40ms N
Chrony tracking log also stucked from 13:38:02 until getting the log at 14:38:00
sudo tail -f /var/log/chrony/tracking.log
Date (UTC) Time IP Address St Freq ppm Skew ppm Offset L Co Offset sd Rem. corr. Root delay Root disp. Max. error
===================================================================================================================================
2023-01-02 13:36:10 0.0.0.0 0 12.590 0.019 0.000e+00 ? 0 0.000e+00 -7.960e-17 1.000e+00 1.000e+00 1.500e+00
2023-01-02 13:36:16 72.30.35.88 3 12.590 0.019 3.068e-03 N 4 2.286e-03 -5.357e-11 7.379e-02 1.479e-03 1.500e+00
2023-01-02 13:36:18 72.30.35.88 3 12.590 0.019 6.158e-05 N 4 2.509e-03 -5.500e-10 7.394e-02 1.123e-03 4.149e-02
2023-01-02 13:36:57 PHC0 1 12.590 0.020 -2.377e-03 N 1 5.802e-08 -4.352e-05 1.000e-09 9.177e-06 3.935e-02
2023-01-02 13:37:13 PHC0 1 12.575 0.042 -4.768e-07 N 1 2.422e-08 -5.427e-08 1.000e-09 9.445e-06 2.359e-03
2023-01-02 13:37:30 PHC0 1 12.560 0.021 -3.218e-07 N 1 3.419e-08 -1.873e-10 1.000e-09 9.819e-06 2.677e-05
2023-01-02 13:37:46 PHC0 1 12.556 0.016 -1.590e-07 N 1 5.516e-08 -1.407e-10 1.000e-09 6.239e-06 2.651e-05
2023-01-02 13:38:02 PHC0 1 12.556 0.011 -3.443e-08 N 1 5.891e-08 -1.177e-10 1.000e-09 1.465e-05 2.267e-05
-----Original Message-----
From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
Sent: Monday, January 2, 2023 14:42
To: chrony-users@xxxxxxxxxxxxxxxxxxxx
Subject: RE: [EXTERNAL][chrony-users] chrony switch source issue
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe.
On Mon, Jan 02, 2023 at 12:22:56PM +0000, Bernstein, Amit wrote:
> As both source timestamp (NTP and PHC) are very close to each other
> And according to chrony faq: "It will let the clock run free for as long as its estimated error (in terms of root distance) based on previous measurements is smaller than the estimated error of the second source, and there is still an interval which contains some measurements from both sources."
> Chrony should have replaced the source from PHC to NTP after no more than several msec, I have waited about an hour and still saw chrony getting stucked on PHC source.
Please post output from chronyc sources, sourcestats, ntpdata, selectdata.
--
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.
--
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.