On 2/27/21 2:50 PM, Charlie Laub wrote:
If you run the command "date" (or whatever it is for your OS) on your machine,
is that approximately correct?
Via other NTP synchronization means prior to starting chronyd, the
system clock is properly set, and time was also set to within 250 ms. or
better.
-----Original Message-----
From: Aaron D. Gifford <synctimeg...@tambler.com>
Sent: Saturday, February 27, 2021 4:23 PM
To: chrony-users@chrony.tuxfamily.org
Subject: [chrony-users] Will it EVER synch and start serving?
I'm running Chrony version 4.0 on FreeBSD. And I just can't seem to ever get
chronyd to sync and start offering time services.
OUTPUT FROM chronyc tracking:
=============================
Reference ID : 00000000 ()
Stratum : 0
Ref time (UTC) : Thu Jan 01 00:00:00 1970 System time : 0.000000000
seconds fast 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
OUTPUT FROM chronyc sources -v:
===============================
Reference ID : 00000000 ()
.-- 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
===============================================================================
^- timesource-1.example.org 1 9 263 713 -160ms[ -160ms]
+/- 24ms
^- timesource-2.example.org 1 10 377 580 -152ms[ -152ms]
+/- 36ms
^- timesource-3.example.org 1 10 377 906 -151ms[ -151ms]
+/- 15ms
^- timesource-4.example.org 1 10 377 145 -144ms[ -144ms]
+/- 94ms
^- timesource-5.example.org 1 10 377 23m -149ms[ -149ms]
+/- 17ms
^- timesource-6-example.org 1 9 377 386 -146ms[ -146ms]
+/- 22ms
^- timesource-7.example.org 1 9 377 514 -148ms[ -148ms]
+/- 17ms
^- timesource-8.example.org 1 9 377 129 -152ms[ -152ms] +/- 9130us
^- ip6timesource.example.or> 1 10 377 266 -151ms[ -151ms]
+/- 11ms
OUTPUT FROM chronyc sourcestats:
================================
Name/IP Address NP NR Span Frequency Freq Skew Offset
Std Dev
==============================================================================
timesource-1.example.org 21 14 81m -0.745 0.654 -160ms 1257us
timesource-2.example.org 29 13 84m -1.115 0.637 -151ms 1141us
timesource-3.example.org 31 21 78m -0.661 0.579 -150ms 1179us
timesource-4.example.org 31 20 91m -0.418 0.802 -144ms 1486us
timesource-5.example.org 28 15 70m -0.920 1.205 -150ms 2296us
timesource-6-example.org 18 13 71m -0.322 1.660 -148ms 2290us
timesource-7.example.org 29 15 85m -0.758 0.436 -147ms 887us
timesource-8.example.org 21 13 80m -0.834 0.329 -149ms 536us
ip6timesource.example.or> 28 14 89m -1.174 0.642 -152ms 1136us
I've tried every tweak of my configuration I can think of, reverting to
the default chrony.conf that auto-installed from the FreeBSD chrony port
and adding my time sources. No luck!
I tried disabling half the sources (randomly picked), waited, no go.
Then disabling another random set of sources. No matter what the
sources remain reachable, but remain always "-" NOT COMBINED state.
Suggestions where to look?
Most puzzling is that my configuration used to work in earlier versions
of chrony.
Stumped,
Aaron Gifford
--
To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org
with "unsubscribe" in the subject.
For help email chrony-users-requ...@chrony.tuxfamily.org
with "help" in the subject.
Trouble? Email listmas...@chrony.tuxfamily.org.
