Re: Help with check_ntp_time v1.4.15
Werner Flamme <[email protected]>
| Newsgroups | gmane.network.nagios.plugins |
|---|---|
| Message-ID | <[email protected]> |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ken edgar [12.07.2012 23:39]: > I have an interesting situation in which check_ntp_time is > returning "NTP CRITICAL: No response from NTP server". This is odd > because the NTP server is reachable from the host which is getting > time from it successfully. > > Here is an example of the plug-in failing to contact the server, > and ntpdate running an updating time successfully. > > [root@stripedmarlin ~]# > /opt/app/nagios/nagios_plugins/current/libexec/check_ntp_time -t 30 > -H ext-timekeeper.schoolspecialty.com -w 1 -c 2 NTP CRITICAL: No > response from NTP server [root@stripedmarlin ~]# ntpdate > ext-timekeeper.schoolspecialty.com12 Jul 16:36:29 ntpdate[6233]: > adjust time server 10.14.99.68 offset -0.003131 sec > > Do you have any suggestions as to what may be going on? This is a > RHEL 5.8 x86_64 VM. When problems on RHEL occur, there is always SELinux as a suspect ;-). Did you check it? Regards, Werner - -- -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlAIAhMACgkQk33Krq8b42P0mwCeM5DChnHi7Ns0nTu06mJpDH4T Cs8AnA8WMdQ0oDtMOxvsdnL4X/qhaJEd =qu+9 -----END PGP SIGNATURE----- ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Nagiosplug-help mailing list Nagiosplug-help-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org https://lists.sourceforge.net/lists/listinfo/nagiosplug-help ::: Please include plugins version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null