'?' = unusable
Brian Cook <bcook-7C+AMPwA5wV9Og/VYhtI4QHE/[email protected]>
| Newsgroups | gmane.comp.time.chrony.user |
|---|---|
| Message-ID | <CAOyb_EwoLyzVvc334Dj5y7gYcLVFUgxFKN6UtTrRD-yNDs5kAQ@mail.gmail.com> |
I have tried to make the change to nts via cloudflare and I am confused by
the results that I see over time..
I don't see anything wrong, I just do not understand what I am seeing..
system running chrony is bare metal, 5.15.108 kernel
cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-5.15.108_1
root=UUID=78a6c88d-2e8c-435d-910e-4344fa420fd8 ro loglevel=4
mitigations=off intel_idle.max_cstate=1 cryptomgr.notests
intel_iommu=igfx_off no_timer_check noreplace-smp page_alloc.shuffle=1
rcupdate.rcu_expedited=1 tsc=reliable
chronyc tracking -v
Reference ID : A29FC87B (time.cloudflare.com)
Stratum : 4
Ref time (UTC) : Mon Apr 24 02:36:27 2023
System time : 0.000000091 seconds fast of NTP time
Last offset : -0.000036995 seconds
RMS offset : 0.000404463 seconds
Frequency : 3.774 ppm fast
Residual freq : -0.979 ppm
Skew : 8.642 ppm
Root delay : 0.013949345 seconds
Root dispersion : 0.347738832 seconds
Update interval : 64.8 seconds
Leap status : Normal
(this looks like cloudflare..)
chronyc sources -v
.-- Source mode '^' = server, '=' = peer, '#' = local clock.
/ .- Source state '*' = current best, '+' = combined, '-' = not combined,
| / 'x' = may be in error, '~' = too variable, '?' = unusable.
|| .- xxxx [ yyyy ] +/- zzzz
|| Reachability register (octal) -. | xxxx = adjusted
offset,
|| Log2(Polling interval) --. | | yyyy = measured
offset,
|| \ | | zzzz = estimated
error.
|| | | \
MS Name/IP address Stratum Poll Reach LastRx Last sample
===============================================================================
^? time.cloudflare.com 0 10 0 - +0ns[ +0ns] +/-
0ns
^- ohio.time.system76.com 2 10 0 545m -1165us[-1094us] +/-
32ms
^? clock.nyc.he.net 2 10 0 544m -15us[ -51us] +/-
35ms
(this does not say cloudflare..)
chronyc -N authdata
Name/IP address Mode KeyID Type KLen Last Atmp NAK Cook CLen
=========================================================================
time.cloudflare.com NTS 3 15 256 243m 0 0 2 100
ohio.time.system76.com NTS 5 15 256 122m 4 0 0 0
209.51.161.238 - 0 0 0 - 0 0 0 0
(this looks normal.. but)
last.. 243m? 122m?
(logs)
2023-04-24T02:32:04.25411 daemon.info: Apr 23 22:32:04 chronyd[29830]:
chronyd version 4.3 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP
+SCFILTER -SIGND +ASYNCDNS +NTS +SECHASH +IPV6 -DEBUG)
2023-04-24T02:32:04.25424 daemon.info: Apr 23 22:32:04 chronyd[29830]:
Frequency 6.527 +/- 1.230 ppm read from /var/lib/chrony/drift
2023-04-24T02:32:04.25427 daemon.info: Apr 23 22:32:04 chronyd[29830]:
Using right/UTC timezone to obtain leap second data
2023-04-24T02:32:08.74090 daemon.info: Apr 23 22:32:08 chronyd[29830]:
Selected source 162.159.200.123 (time.cloudflare.com)
2023-04-24T02:32:08.74092 daemon.info: Apr 23 22:32:08 chronyd[29830]:
System clock TAI offset set to 37 seconds
2023-04-24T02:46:10.21893 daemon.info: Apr 23 22:46:10 chronyd[29830]:
Source 162.159.200.123 replaced with 162.159.200.1 (time.cloudflare.com)
2023-04-24T03:22:48.43605 daemon.info: Apr 23 23:22:48 chronyd[29830]:
Source 162.159.200.1 replaced with 162.159.200.123 (time.cloudflare.com)
2023-04-24T05:40:39.71443 daemon.info: Apr 24 01:40:39 chronyd[29830]:
Source 162.159.200.123 replaced with 162.159.200.1 (time.cloudflare.com)
2023-04-24T08:32:38.69419 daemon.info: Apr 24 04:32:38 chronyd[29830]:
Source 162.159.200.1 replaced with 162.159.200.123 (time.cloudflare.com)
2023-04-24T11:24:47.06631 daemon.info: Apr 24 07:24:47 chronyd[29830]:
Source 162.159.200.123 replaced with 162.159.200.1 (time.cloudflare.com)
cat /etc/chrony.conf| egrep -v "^#|^\$"
ntsdumpdir /var/lib/chrony
ntstrustedcerts /etc/ssl/certs.pem
nosystemcert
nocerttimecheck 1
server time.cloudflare.com iburst nts (<- could not get away with no dns
nts?)
server ohio.time.system76.com iburst nts (<- could not get away with no dns
nts?)
authselectmode mix
server 209.51.161.238 iburst (<- I try to do ntp w/o dns in case no dns)
logchange 0.5
logdir /var/lib/chrony/
log measurements statistics tracking
driftfile /var/lib/chrony/drift
ntsdumpdir /var/lib/chrony/
rtcsync
makestep 1 -1
minsources 1 (<- I had to find a second nts clock.. )
leapsectz right/UTC
local stratum 5
clientloglimit 1048576
bindaddress 172.16.254.241
allow 172.16.0.0/16
allow 10.20.0.0/16
allow 10.120.0.0/16
allow 10.121.0.0/16
chronyc clients -n | wc -l
1502
Side note..
Rather than trying to 'dns hijack ntp'.. hijacking ntp seemed like a better
idea since I could nts sync.. and hopefully the two will never meet..
[image: image.png]
drill time.cloudflare.com
;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 21671
;; flags: qr rd ra ; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;; time.cloudflare.com. IN A
;; ANSWER SECTION:
time.cloudflare.com. 900 IN A 162.159.200.123
time.cloudflare.com. 900 IN A 162.159.200.1
;; AUTHORITY SECTION:
;; ADDITIONAL SECTION:
;; Query time: 2 msec
;; SERVER: 10.20.32.100
;; WHEN: Mon Apr 24 07:50:00 2023
;; MSG SIZE rcvd: 69
/v/l/chrony# ls -al
total 78924
drwxr-xr-x 2 chrony chrony 112 Apr 24 07:24 ./
drwxr-xr-x 15 root root 193 Nov 26 14:04 ../
-rw------- 1 chrony chrony 997 Apr 24 07:24 162.159.200.123.nts
-rw-r--r-- 1 chrony chrony 42 Apr 23 22:32 drift
-rw-r--r-- 1 chrony chrony 41353998 Apr 23 22:36 measurements.log
-rw-r--r-- 1 chrony chrony 34937487 Apr 23 22:36 statistics.log
-rw-r--r-- 1 chrony chrony 4467804 Apr 23 22:36 tracking.log
[I] root@void-10G-hs /v/l/chrony# cat 162.159.200.123.nts
NNC0
time.cloudflare.com
1682333423.3
162.159.200.123 123
3 15 2ECAF1C80EB6F4F70AEABFBED2A6BC747E297BDC78286204FEB767031AC060CF
1939F2B8A5FB546F63CAEE85345C2C54595BF26C1C6A11EF717BD11A1E883AB1
00465320BF526966709FA35CC551160EED40907B0C5505D6D71EC14B1417E8B95AE118A9156B5D2BA85128AD4D2079BE61138F08D0FC9A9189AE37354B762EF9FC7A682C4247EA4677B15A8E512C6BDB4E819F34572343B454EE611869AD3350F23200F1
0046532037FCCCAC1B2540B882E7C6960C01374F9FE52125D34755613D541EAB1CE22FED64F39DE7673676D686764F448EE81F1827CDCFE7B1228A2A2F48F861618100C80815817251FF6CFC88AB85E2EBA74E119C7A0E4D2D84D24E223DA5BF241BFA8C
004653207167C6CD0914BB29B14AC57B3F7799C4BE75DD2170143EDFF2DE5BF5DED4C6A866DBD4579DB006F13A6DA8B452FE79A550EE579959C5E100A2A94294955E96A55489075F5882443E9BF2A05A4B8883D58BDF2F078C434545D8941B1CF9F450F7
004653200F264A3EFBD34097E2825EA97A94D3483E5B7DBA2785243A487B01C1D6E0C21334CFA2BA8F18186A015976551B9BA422CFB62CE172CE070F6BCCEED81D3F66FE45D51635B878814C65412C20054056959A8BFF01E4378BE3E882852E6E638527
[I] root@void-10G-hs /v/l/chrony# tail -F 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-04-24 02:32:04 0.0.0.0 0 6.527 1.230 0.000e+00 ?
0 0.000e+00 -1.625e-16 1.000e+00 1.000e+00 1.500e+00
2023-04-24 02:32:08 162.159.200.123 4 6.527 1.230 -2.534e-05 N
1 7.827e-05 -2.366e-11 1.262e-02 8.119e-04 1.500e+00
2023-04-24 02:32:10 162.159.200.123 4 6.527 1.462 3.240e-04 N
1 7.803e-05 -8.038e-10 1.194e-02 8.087e-04 7.177e-03
2023-04-24 02:33:15 162.159.200.123 4 6.523 1.749 -1.013e-03 N
1 6.653e-04 1.432e-07 1.457e-02 1.420e-03 1.319e-02
2023-04-24 02:34:19 162.159.200.123 4 6.376 3.007 2.945e-04 N
1 1.873e-04 -1.983e-09 1.195e-02 8.936e-04 1.070e-02
2023-04-24 02:35:23 162.159.200.123 4 5.570 6.197 -3.761e-04 N
1 2.586e-04 3.946e-10 1.195e-02 1.693e-03 7.669e-03
2023-04-24 02:36:28 162.159.200.123 4 3.774 8.642 -3.700e-05 N
1 2.843e-04 9.881e-06 1.395e-02 9.498e-04 8.752e-03
^C⏎
[I]
root@void-10G-hs /v/l/chrony [SIGINT]# tail -F statistics.log
2023-04-24 02:32:15 3.134.129.152 1.300e-04 -1.460e-03 1.267e-04
-1.862e-05 5.060e-04 7.5e-03 4 0 3 0.00
2023-04-24 02:33:15 162.159.200.123 3.137e-04 -1.013e-03 6.653e-04
-1.249e-05 1.321e-04 1.2e-01 5 0 3 0.00
2023-04-24 02:33:15 209.51.161.238 5.329e-04 -5.954e-04 7.838e-04
-1.486e-05 1.558e-04 3.2e-03 5 0 4 0.00
2023-04-24 02:34:19 162.159.200.123 2.706e-04 2.945e-04 1.873e-04
-3.977e-06 1.546e-05 6.4e-02 6 0 4 0.00
2023-04-24 02:34:19 209.51.161.238 5.038e-04 -2.286e-05 4.150e-04
-1.018e-06 3.158e-05 8.8e-02 6 0 5 0.00
2023-04-24 02:35:23 162.159.200.123 2.869e-04 -3.761e-04 2.586e-04
-4.530e-06 1.119e-05 4.5e-02 7 0 5 0.00
2023-04-24 02:35:24 209.51.161.238 4.178e-04 8.426e-04 2.831e-04
2.422e-06 1.273e-05 8.3e-02 7 0 5 0.00
2023-04-24 02:35:28 3.134.129.152 1.379e-04 -1.116e-03 2.713e-04
-3.483e-06 1.796e-05 2.8e-02 5 0 3 0.00
2023-04-24 02:36:28 209.51.161.238 5.088e-04 7.719e-04 4.061e-04
1.735e-06 1.186e-05 5.4e-02 8 0 6 0.00
2023-04-24 02:36:28 162.159.200.123 3.061e-04 -3.699e-05 2.843e-04
-2.775e-06 7.926e-06 8.5e-02 8 0 6 0.00
^C⏎
[I]
root@void-10G-hs /v/l/chrony [SIGINT]# tail -F measurements.log
2023-04-24 02:32:15 3.134.129.152 N 2 111 111 1111 6 6 0.03
1.333e-03 2.108e-02 4.236e-05 1.541e-02 1.306e-02 81060F20 4B K K
2023-04-24 02:33:15 162.159.200.123 N 3 111 111 1111 6 6 0.00
1.182e-03 6.944e-03 6.083e-06 7.629e-03 7.477e-04 0AC40805 4B K K
2023-04-24 02:33:15 209.51.161.238 N 2 111 111 1111 6 6 0.00
6.100e-04 6.759e-03 1.731e-05 5.917e-02 1.648e-03 42DC097A 4B K K
2023-04-24 02:34:19 162.159.200.123 N 3 111 111 1111 6 6 0.00
-3.199e-04 4.259e-03 6.185e-07 7.690e-03 7.019e-04 0A820804 4B K K
2023-04-24 02:34:19 209.51.161.238 N 2 111 111 1111 6 6 0.00
-9.601e-05 4.627e-03 9.960e-07 5.917e-02 1.724e-03 42DC097A 4B K K
2023-04-24 02:35:23 162.159.200.123 N 3 111 111 1111 6 6 0.00
8.360e-04 6.556e-03 1.472e-07 7.401e-03 6.866e-04 0A8A080D 4B K K
2023-04-24 02:35:24 209.51.161.238 N 2 111 111 1111 6 6 0.00
-1.024e-03 4.430e-03 3.211e-07 5.917e-02 1.785e-03 42DC097A 4B K K
2023-04-24 02:35:28 3.134.129.152 N 2 111 111 1111 6 6 0.44
1.094e-03 2.259e-02 1.153e-05 1.541e-02 1.326e-02 81060F20 4B K K
2023-04-24 02:36:28 209.51.161.238 N 2 111 111 1111 6 6 0.00
5.132e-05 6.751e-03 1.327e-07 5.917e-02 1.846e-03 42DC097A 4B K K
2023-04-24 02:36:28 162.159.200.123 N 3 111 111 1111 6 6 0.00
-3.032e-04 5.969e-03 1.124e-07 7.980e-03 6.561e-04 0A840804 4B K K
^C⏎
[I]
root@void-10G-hs /v/l/chrony [SIGINT]# ls -al
total 78924
drwxr-xr-x 2 chrony chrony 112 Apr 24 07:24 ./
drwxr-xr-x 15 root root 193 Nov 26 14:04 ../
-rw------- 1 chrony chrony 997 Apr 24 07:24 162.159.200.123.nts
-rw-r--r-- 1 chrony chrony 42 Apr 23 22:32 drift
-rw-r--r-- 1 chrony chrony 41353998 Apr 23 22:36 measurements.log
-rw-r--r-- 1 chrony chrony 34937487 Apr 23 22:36 statistics.log
-rw-r--r-- 1 chrony chrony 4467804 Apr 23 22:36 tracking.log
Again, everything looks fine, but I am not sure why over time it says that
the chosen nts server is not usable..
Thank you in advance.
image.png
(image/png, 78.7 KB) - not displayed