I had a situation lately with a host that need up to date ntp servers. We had during the weekend a crash of our internet router. When everything came back to hte normal our application was still complaining about NTP.
We discovered that the ntp client took 9h to get sync. Here is the ntpd's logs :
Aug 19 15:31:15 host ntpd: kernel time sync status 0040 Aug 19 15:31:15 host ntpd: frequency initialized 97.149 PPM from /tmp/drift Aug 20 00:29:24 host ntpd: synchronized to 192.168.10.13, stratum 3 Aug 20 00:29:24 host ntpd: kernel time sync disabled 0001
When the issue occured here is the output of peers state :
# ntpq ntpq> peers remote refid st t when poll reach delay offset jitter ============================================================================== srv1 188.8.131.52 3 u 31 64 377 0.714 -685.16 6.388 srv2 184.108.40.206 3 u 5 64 377 0.652 -1385.7 12.165
Someone told me that I should use minpoll and maxpoll settings to solve this issue.
What should I do to avoid 9H NTP synchronisation ?