Package: chrony
Version: 1.31.1
The last statistics log is for March 15, 2016 and it's empty. chronyc
chronyc sources:
210 Number of sources = 4
MS Name/IP address Stratum Poll Reach LastRx Last sample
===============================================================================
^? b1-66er.matrix.gs 0 10 0 10y +0ns[ +0ns] +/- 0ns
^? propjet.latt.net 0 10 0 10y +0ns[ +0ns] +/- 0ns
^? ha82.smatwebdesign.com 0 10 0 10y +0ns[ +0ns] +/- 0ns
^? ntp.untangle.com 0 9 0 10y +0ns[ +0ns] +/- 0ns
The sources seem to frequently change by themselves. It's as if the
sources can't be reached so it keeps trying new ones, yet I can ping all
the sources shown here and on other tries. Note that 10y for 10 years ago
is not true. It likely never received any time data from these sources.
------------------------------------------------------------------
cronyc tracking:
Reference ID : 127.127.1.1 ()
Stratum : 10
Ref time (UTC) : Mon Jun 6 00:33:57 2016
System time : 0.000000001 seconds slow of NTP time
Last offset : +0.000000000 seconds
RMS offset : 0.000000000 seconds
Frequency : 5.857 ppm slow
Residual freq : +0.000 ppm
Skew : 0.000 ppm
Root delay : 0.000000 seconds
Root dispersion : 0.000001 seconds
Update interval : 0.0 seconds
Leap status : Not synchronised
The above look OK except the command "date" typed on the shell command line
shows a time that is 16 minutes slower than the actual time (checked by a
wristwatch set to time from the Inet). And I can't reset the hardware
clock with "settime" since I get "facility not enabled in daemon". If I
try to use the hwclock program to correct the time it says it has no
method of access to the hardware clock.
---------------------------------------------------------------
chrnyc activity:
200 OK
4 sources online
0 sources offline
0 sources doing burst (return to online)
0 sources doing burst (return to offline)
0 sources with unknown address
------------------------------------------------------------
Here's the start of the tracking log file (note the scew of exactly one
million):
==================================================================================================
Date (UTC) Time IP Address St Freq ppm Skew ppm Offset L Co
Offset sd Rem. corr.
==================================================================================================
2016-06-04 08:37:38 0.0.0.0 0 -5.857 1000000.000 0.000e+00 ? 0
0.000e+00 1.100e-16
==================================================================================================
Date (UTC) Time IP Address St Freq ppm Skew ppm Offset L Co
Offset sd Rem. corr.
==================================================================================================
2016-06-05 08:45:55 0.0.0.0 0 -5.857 1000000.000 0.000e+00 ? 0
0.000e+00 9.856e-17
==================================================================================================
Date (UTC) Time IP Address St Freq ppm Skew ppm Offset L Co
Offset sd Rem. corr.
==================================================================================================
2016-06-05 08:58:14 0.0.0.0 0 -5.857 1000000.000 0.000e+00 ? 0
0.000e+00 9.175e-17
==================================================================================================
-----------------------------------------------------------------------
I restarted chronyd with the -d flag and it only showed a couple of lines
and showed the skew to be 1 million seconds and not 0 as shown in
tracking. I did chrony>burst and nothing was shown on the terminal,
although if I do chronyc activity it does show the burst running for
awhile (a minute or two).
So why isn't it working? I'm running Debian 4.2.3 on an old Pentium I PC.
And I updated using aptitude in Nov. 2015 which might be about when
problems with chrony started (but I failed to investigate them then).
David Lawyer
