Re: ntp problem
On Tue, 24 Jun 2014, Darac Marjal wrote:
. . .
ntp_gettime() error 5 is, according to the man page, "TIME_ERROR (clock
not synchronised". So, in that case, look to your ntpd. Run "ntpq -p" to
see the status of your peers and/or "ntpq -c assoc" for more details.
The information there can be complex, so feel free to paste the results
here :)
thank you Darac for your reply. Here is the requested information
==> ntpq -p
remote refid st t when poll reach delay offset jitter
==============================================================================
outbound-smtp.n 192.93.2.20 2 u 53 64 377 29.858 -189901 2903.84
solsocog.de 131.188.3.222 2 u 28 64 377 32.191 -190155 2883.27
merlin.ensma.fr 192.93.2.20 2 u 46 64 377 30.728 -189979 2843.02
loin.ploup.net 213.251.128.249 2 u 48 64 377 28.665 -189960 2854.50
oods.roflcopter 195.83.222.27 2 u 16 64 377 24.955 -190301 2868.25
excalibur.exsv. 194.57.169.1 3 u 27 64 377 25.564 -190194 2918.50
==> ntpq -c assoc
ind assid status conf reach auth condition last_event cnt
===========================================================
1 26514 9044 yes yes none reject reachable 4
2 26515 9014 yes yes none reject reachable 1
3 26516 901a yes yes none reject sys_peer 1
4 26517 902a yes yes none reject sys_peer 2
5 26518 901a yes yes none reject sys_peer 1
6 26519 9014 yes yes none reject reachable 1
the offset, jitter and condition values values seems rather bad,
but have an idea about the possible cause?
the drift is now about 3 minutes, and even without ntpd, I suppose that the internal clock
can't have a so big drift I'll try stopping ntpd to see what happens.
best regards,
--
Pierre Frenkiel
Reply to: