> Le 13 déc. 2017 à 08:57, Mike Cook <[email protected]> a écrit : > > <snip>
> ntpq: read: Connection refused > Wed Dec 13 06:50:30 UTC 2017 > associd=0 status=c016 leap_alarm, sync_unspec, 1 event, restart, > version="ntpd [email protected] Tue Dec 12 08:45:23 UTC 2017 (1)", > processor="armv7l", system="Linux/3.8.13-bone47", leap=11, stratum=16, > precision=-19, rootdelay=0.000, rootdisp=0.030, refid=INIT, > reftime=00000000.00000000 Thu, Feb 7 2036 6:28:16.000, > clock=dddb4c36.78d0e3a5 Wed, Dec 13 2017 6:50:30.471, peer=0, tc=3, > <============= > mintc=3, offset=0.000000, frequency=-31.917, sys_jitter=0.000000, > clk_jitter=0.002, clk_wander=0.000, leapsec=201701010000, > expire=201706280000 > Wed Dec 13 06:36:12 UTC 2017 > associd=0 status=c615 leap_alarm, sync_ntp, 1 event, clock_sync, > version="ntpd [email protected] Tue Dec 12 08:45:23 UTC 2017 (1)", > processor="armv7l", system="Linux/3.8.13-bone47", leap=11, stratum=16, > precision=-19, rootdelay=0.000, rootdisp=0.000, refid=STEP, > reftime=00000000.00000000 Thu, Feb 7 2036 6:28:16.000, > clock=dddb48dc.1ed39583 Wed, Dec 13 2017 6:36:12.120, peer=9799, tc=4, > <************** > mintc=3, offset=0.000000, frequency=-31.917, sys_jitter=0.001907, > clk_jitter=0.002, clk_wander=0.000, leapsec=201701010000, > expire=201706280000 I forgot to mention: The fact that the system clock has been updated via -g even though the server config cannot be validated ( leap=11) may explain why when the OP stopped NTP and was able to restart it immediately after without the issue as the servers clock was now very close to the correct time. An argument for executing ntpdate before starting ntpd? "The power of accurate observation is commonly called cynicism by those who have not got it. » George Bernard Shaw _______________________________________________ questions mailing list [email protected] http://lists.ntp.org/listinfo/questions
