thanks alot! this helps a bunch, and with the other recommendations to add a fourth server, and to make sure as many of them are as close in netspace as possible renders a great solution.
i'm proud that I can ask the lists and get a solution almost every time, -the community rocks! -karlski > Per Hedeland wrote: >> >> 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?", > > Towards the server where the monitored service runs on. Every nagios check > is > associated to a host, there are no host-independent services. > >> 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). > > ntpdate -q localhost > > would do that (and might be used, when Nagios monitors localhost). > Please note: I don't know either why the original check_ntp author chose > ntpdate > to query the offset and didn't use ntpq by default. I suppose that's > historical > development baggage. > > But I know that check_ntp didn't work correctly, because I supplied > patches to > the Nagios project to repair it. They were folded in last week or so. With > these > patches, Nagios monitoring works for me and several others who had > problems as well. > > Cheers, > Joachim > > -- > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > Joachim Schrod Email: [EMAIL PROTECTED] > Roedermark, Germany > > _______________________________________________ > questions mailing list > [email protected] > https://lists.ntp.isc.org/mailman/listinfo/questions > _______________________________________________ questions mailing list [email protected] https://lists.ntp.isc.org/mailman/listinfo/questions
