[ntp:questions] NTP.log interpretation

GregL greg.leibfried at gmail.com
Fri Apr 18 23:33:35 UTC 2014

On Fri, Apr 18, 2014 at 3:15 PM, Jochen Bern <Jochen.Bern at linworks.de>wrote:

> Am I missing something, or will the setup described above (and assuming
> that the two servers disagree again) *force* your clients to do what you
> just called "the far greater problem"? Namely, being randomly split
> 50/50 between the two servers, not even *knowing* of the other one?
I think that is part of the reason I'm sanity checking.  I think if the
servers stay in sync... it's probably a non issue.  But that is the issue..
I've seen the havoc when one out of two servers is bad... and with the load
balancer, there's no guarantee I'm any better off.......

(FWIW, ntpd does the DNS resolution *once* when loading its config and
> works with the one IP obtained from then on, plans of implementing
> automatic rotation/selection of "pool" servers in future versions
> notwithstanding. And having potentially disagreeing NTP servers put
> behind a V*IP* load balancer is discouraged as well.)

**especially** considering that statement!   Hmmm....if that's the way ntpd
works, then I think the load balancer is worse than useless for ntp
clients... it could be disastrous, correct?

Thanks again for the feedback/advice... I think that re-examining the
configuration is even more important now.

I like the idea of one time server from a pool and the other from a gps
based source.


More information about the questions mailing list