Toon's clock is 2 minutes behind
Posted: Wed Aug 22, 2018 8:28 pm
Suddenly Toon's clock is 2 minutes behind, restart Toon and restart router doesn't solve this problem. Does anyone have a different solution?
Hans
Hans
Domotica - Home Automation Forum
https://www.domoticaforum.eu/
Thanx, changing the time server in chrony.conf solved the problem. Remarkably, the config was in accordance with the root manual.marcelr wrote:Two checks:
Is your toon connected to the internet?
If not, connect it.
Is Toons chronyd up and running, and connecting to a time server?
If not start it, and check whether the chronyd is connected to a time server (the rooting manual gives an example), lately I 've been using 0.nl.pool.ntp.org successfully.
Code: Select all
# ntpq -p www.nist.gov
dualstack.mc-12555-1019789594.us-east-1.elb.amazonaws.com: timed out, nothing received
***Request timed out
It's marcelr. Yes I can.TheHogNL wrote:@MarcelC can you change the manual?
Used the exact contents of the chrony.conf mentioned in above link, but still get errors / warnings if I look in /var/log/messages (see below). Any clues?Toonz wrote:Have you updated /etc/chrony.conf as described here: viewtopic.php?f=87&t=11449&p=85791&hili ... onf#p85791 ?
And reboot probably
Code: Select all
Aug 30 12:25:50 eneco-001-286065 daemon.info chronyd[1247]: chronyd version 1.27 starting
Aug 30 12:25:50 eneco-001-286065 daemon.info chronyd[1247]: Linux kernel major=2 minor=6 patch=36
Aug 30 12:25:50 eneco-001-286065 daemon.info chronyd[1247]: hz=100 shift_hz=7 freq_scale=1.00000000 nominal_tick=10000 slew_delta_tick=833 max_tick_bias=1000 shift_pll=2
Aug 30 12:25:50 eneco-001-286065 daemon.err chronyd[1247]: Could not open IPv6 NTP socket : Address family not supported by protocol
Aug 30 12:25:50 eneco-001-286065 daemon.err chronyd[1247]: Could not open IPv6 command socket : Address family not supported by protocol
Aug 30 12:25:51 eneco-001-286065 daemon.info chronyd[1247]: Frequency 4.413 +/- 0.074 ppm read from /var/lib/chrony/chrony.drift
Aug 30 12:25:51 eneco-001-286065 daemon.info chronyd[1247]: System's initial offset : 138.716520 seconds slow of true (step)
Aug 30 12:28:10 eneco-001-286065 daemon.warn chronyd[1247]: Could not open dump file /var/lib/chrony/185.92.220.131.dat
Aug 30 12:28:10 eneco-001-286065 daemon.warn chronyd[1247]: Could not open dump file /var/lib/chrony/95.211.212.5.dat
Aug 30 12:28:10 eneco-001-286065 daemon.warn chronyd[1247]: Could not open dump file /var/lib/chrony/213.109.127.82.dat
Aug 30 12:28:10 eneco-001-286065 daemon.warn chronyd[1247]: Could not open dump file /var/lib/chrony/193.169.139.87.dat
A few chrony restarts indeed removed the errors. Thanks!TheHogNL wrote:Just noticed that the chrony implementation on the toon is somewhat buggy. If it connects to a new time server which is has never connected to, it will not sync to it (giving that error dump file message). With pool.ntp.org the server will change between a lot of pool servers. Just restart chrony a few times and it will create the necessary files for it to sync properly.
Check with "chronyc sources -v"
Did you try a reboot?MyZ wrote:How do I restart chrony?
Can you post the content of the chrony file ?MyZ wrote:Yes a couple of times