In article <[EMAIL PROTECTED]> [EMAIL PROTECTED] writes: > >All machines talking to my main NTP node are giving errors back to the >Nagios check_ntp command. > >What's the best way to troubleshoot this? Any useful commands? > >-- >Here are some of the warnings from the pool of servers I have running: > >NTP WARNING: Offset 5.549596 sec > +/- 2 sec, jitter 9.111 msec >NTP WARNING: Offset 5.560099 sec > +/- 2 sec, jitter 9.534 msec >NTP WARNING: Offset 5.596052 sec > +/- 2 sec, jitter 10.068 msec > >When I run ntpq -p I get: >/usr/sbin/ntpq -p > >remote refid st t when poll reach delay offset jitter >============================================================================== >*toshi.keneli.or .GPS. 1 u 63 64 377 87.424 7.085 >1.970 >+dankulp.com ntp2-ext.schlun 3 u 2 64 377 81.263 9.698 >0.630 >+mx11.wtfo-guru. ntp-1.cns.vt.ed 3 u 80 64 376 77.466 8.761 >0.163
Well, I don't really know anything about Nagios, but it seems seriously confused in claiming that you have an offset of 5+ *seconds*, when in fact your ntpq output shows an offset of 7-10 *milli*seconds from your configured servers. Browsing the check_ntp.pl Nagios "plugin", which I guess is what is being used here, it seems it obtains the offset from the output of an invocation of *ntpdate* - which begs the question of "ntpdate towards what server?", since ntpdate can't really tell you anything about how your local ntpd is doing (it seems to use ntpq too, but not for the offset). The server that is used for the ntpdate query seems to be passed as an argument to the check_ntp.pl script, I have no idea how it is chosen - perhaps it is just querying a server whose time is way off? Anyway it seems clear that your problem is with Nagios, not with NTP, so you should probably take it to some other forum. --Per Hedeland [EMAIL PROTECTED] _______________________________________________ questions mailing list [email protected] https://lists.ntp.isc.org/mailman/listinfo/questions
