Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Bug#826695: chrony stopped working
93 views
Skip to first unread message
David Lawyer
Jun 7, 2016, 9:20:03 PM6/7/16
to
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
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
Vincent Blut
Jun 8, 2016, 12:00:08 PM6/8/16
to
Hi David,
On Tue, Jun 07, 2016 at 06:36:13PM -0700, David Lawyer wrote:
>Package: chrony
>Version: 1.31.1
Note that this version isn’t part of any supported Debian version.
>
>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.
Indeed, the above shows sources to which connectivity has been lost
("^?"). "10y" means there were no samples received from these sources.
Being able to receive ICMP Echo Reply is one thing, receiving UDP
messages from NTP sources is another one. Are you behind a firewall?
>
>------------------------------------------------------------------
>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 shows that chronyd is in local mode. It is used when the
“local” directive is set in the configuration file and chronyd is unable
to get time from an external source.
>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".
For this to work, you have to set the “manual” directive in the
configuration file, or to use the “manual” command from chronyc.
>If I try to use the hwclock program to correct the time it says it has
>no method of access to the hardware clock.
Which kernel are you using? Does it provide RTC support?
Could you please sent logs that chrony sends to syslog while starting or
restarting it?
>
>So why isn't it working? I'm running Debian 4.2.3 on an old Pentium I PC.
That’s an unknown Debian version.
> David Lawyer
Cheers,
Vincent
On Tue, Jun 07, 2016 at 06:36:13PM -0700, David Lawyer wrote:
>Package: chrony
>Version: 1.31.1
Note that this version isn’t part of any supported Debian version.
>
>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.
("^?"). "10y" means there were no samples received from these sources.
Being able to receive ICMP Echo Reply is one thing, receiving UDP
messages from NTP sources is another one. Are you behind a firewall?
>
>------------------------------------------------------------------
>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
“local” directive is set in the configuration file and chronyd is unable
to get time from an external source.
>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".
configuration file, or to use the “manual” command from chronyc.
>If I try to use the hwclock program to correct the time it says it has
>no method of access to the hardware clock.
restarting it?
>
>So why isn't it working? I'm running Debian 4.2.3 on an old Pentium I PC.
> David Lawyer
Cheers,
Vincent
Kirill Trofimov
Apr 14, 2018, 11:40:04 AM4/14/18
to
Hello, can you try:
1. check status of chronyd
2. run ‘chronyc online’
3. run ‘chronyc burst 5/10’
4. show output from ‘chronyc sources -v’ ?
I hope that help you.
1. check status of chronyd
2. run ‘chronyc online’
3. run ‘chronyc burst 5/10’
4. show output from ‘chronyc sources -v’ ?
I hope that help you.
stephen williams
Jun 10, 2020, 6:50:03 PM6/10/20
to
Poslal jsem vám tento dopis před měsícem, ale nejsem si jistý, jestli jej máte, neslyšel jsem od vás, tak jsem to napsal znovu. Jsem pan Stephen Williams, předkládám tuto nabídku v souvislosti se smrtí mého zesnulého klienta, který zemřel při strašlivé autonehodě s rodinou na cestě z blízkého města tady v mé zemi a zanechal obrovské množství peněz v bance. Když jsem nenašel jeho příbuzné, rozhodl jsem se vás kontaktovat. Kontaktujte mě prostřednictvím této e-mailové adresy
Pozdravy,
Pan Williams ...
Pozdravy,
Pan Williams ...
Calhun Delph
Jul 27, 2020, 4:10:03 AM7/27/20
to
Roy Charles
Dec 2, 2020, 7:40:04 AM12/2/20
to
Did you receive my first message?
0 new messages