I have a linux box, set up with two ntp servers to sync. This box in case, was extremely out of sync (61 seconds) before it was forced sync. The following outputs are 1 hour after this sync. When checking the ntpq,
ntpq> peers
remote refid st t when poll reach delay offset jitter
==============================================================================
x192.168.[redacted] .MDM. 1 u 113 256 377 0.513 13.120 1.843
x192.168.[redacted] .MDM. 1 u 115 128 377 2.689 0.618 1.230
Both are set to falsetickers!
ntpq> assoc
ind assID status conf reach auth condition last_event cnt
===========================================================
1 13191 91d4 yes yes none falsetick reachable 13
2 13192 91d4 yes yes none falsetick reachable 13
What has led the time choosing algorithm to set both as false, and how can I fix it?
UPDATE!
I have rerun the commands above and got new status:
ntpq> assoc
ind assID status conf reach auth condition last_event cnt
===========================================================
1 13191 91d4 yes yes none falsetick reachable 13
2 13192 96d4 yes yes none sys.peer reachable 13
ntpq> pe
remote refid st t when poll reach delay offset jitter
==============================================================================
x192.168.[red] .MDM. 1 u 241 256 377 0.513 13.120 1.396
*192.168.[red] .MDM. 1 u 114 256 377 2.671 0.567 0.710
ntpq
output above. Something is clearly up with your servers, which is probably not helpingntpd
take them seriously. (And by the way, setting the stratum is not generallyntp.conf
's job, save for stratum-1 servers who will be told about their directly-attached stratum-0 source.)