| Re: [chrony-users] Will it EVER synch and start serving? |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
On 3/1/21 1:43 PM, Bryan Christianson wrote:
<<snip>>
You could try using a pool of servers that are known to be ok, (eg pool.ntp.org) if you are not doing that already. You have not said anything about the servers you are currently using. i.e are they LAN devices or over the internet?
<<snip>>
Great idea! I'll try it.
New CONFIG:
driftfile /var/db/chrony/drift
ratelimit interval 3 burst 8
cmdport 0
bindaddress IP.AD.DR.ESS
bindacqaddress IP.AD.DR.ESS
bindaddress IPV6:ADDR:ESS::5
bindacqaddress IPV6:ADDR:ESS::5
server 0.pool.ntp.org
server 1.pool.ntp.org
server 2.pool.ntp.org
server 3.pool.ntp.org
.... wait for some time after restarting chronyd ...
chronyc tracking OUTPUT:
========================
Reference ID : 00000000 ()
Stratum : 0
Ref time (UTC) : Thu Jan 01 00:00:00 1970
System time : 0.000000035 seconds slow of NTP time
Last offset : +0.000000000 seconds
RMS offset : 0.000000000 seconds
Frequency : 23.521 ppm slow
Residual freq : +0.000 ppm
Skew : 0.000 ppm
Root delay : 1.000000000 seconds
Root dispersion : 1.000000000 seconds
Update interval : 0.0 seconds
Leap status : Not synchronised
chronyc sources -v OUTPUT:
==========================
.-- 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.richiemcintosh.com 2 8 377 41 -217ms[ -217ms]
+/- 75ms
^- clock.xmission.com 1 8 377 245 -221ms[ -221ms] +/-
9381us
^- tempest.benjojo.co.uk 1 8 377 236 -225ms[ -225ms]
+/- 72ms
^- ntp.speculation.org 2 8 377 249 -220ms[ -220ms]
+/- 38ms
chronyc sourcestats -v OUTPUT:
==============================
.- Number of sample points in measurement set.
/ .- Number of residual runs with same sign.
| / .- Length of measurement set (time).
| | / .- Est. clock freq error (ppm).
| | | / .- Est. error in
freq.
| | | | / .- Est.
offset.
| | | | | | On the -.
| | | | | | samples. \
| | | | | | |
Name/IP Address NP NR Span Frequency Freq Skew Offset
Std Dev
==============================================================================
time.richiemcintosh.com 24 12 36m -0.249 1.882 -217ms 1374us
clock.xmission.com 25 12 34m -0.840 1.286 -221ms 946us
tempest.benjojo.co.uk 25 15 34m -2.373 4.092 -227ms 2851us
ntp.speculation.org 24 15 34m -0.883 1.315 -220ms 1023us
chronyc selectdata -v OUTPUT:
=============================
.-- State: N - noselect, M - missing samples, d/D - large distance,
/ ~ - jittery, w/W - waits for others, T - not trusted,
| x - falseticker, P - not preferred, U - waits for update,
| S - stale, O - orphan, + - combined, * - best.
| Effective options ------. (N - noselect, P - prefer
| Configured options -. \ T - trust, R - require)
| Auth. enabled (Y/N) -. \ \ Offset interval --.
| | | | |
S Name/IP Address Auth COpts EOpts Last Score Interval Leap
=======================================================================
W time.richiemcintosh.com N ----- ----- 0 1.0 -275ms -160ms N
W clock.xmission.com N ----- ----- 203 1.0 -230ms -212ms N
W tempest.benjojo.co.uk N ----- ----- 195 1.0 -298ms -152ms N
W ntp.speculation.org N ----- ----- 206 1.0 -258ms -182ms N
Hmmm, I though I waited long enough that by now it should have picked a
source and synched as a stratum 3 server. Looks like the same problem
I'm having with my preferred sources. All NTP pool sources are stuck in
"W" "waits for others" state, despite what appears to be good
connectivity and active responses to NTP queries. *sigh*
Ideas?
Stumped,
Aaron out.
--
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.