Check_ntp_time problem

[Claudio Kuenzler]

Why are you using different NTP servers?

On server 1 you use:
/usr/lib/nagios/plugins/check_ntp_time -H 192.168.50.7 -v

On server 2 you use:
/usr/lib64/nagios/plugins/check_ntp_time -H 192.168.50.2 -v


Localhost always works as this is the emergency fail-back for ntp.


On Tue, Apr 3, 2012 at 6:15 PM, Luc MAIGNAN <luc.maignan at winxpert.com>wrote:

> Hi,
>
> on a server 1, the plugin works well by specifying its own address :
>
> /usr/lib/nagios/plugins/check_ntp_time -H 192.168.50.7 -v
> sending request to peer 0
> response from peer 0: offset -0,0005108481273
> sending request to peer 0
> response from peer 0: offset -6,853620289e-05
> sending request to peer 0
> response from peer 0: offset -2,743146615e-05
> sending request to peer 0
> response from peer 0: offset -2,787803533e-05
> overall average offset: -0,0005108481273
> NTP OK: Décalage -0,0005108481273
> secs|offset=-0,000511s;60,000000;120,000000;
>
>
> on a second, it doesn't work :
>
> /usr/lib64/nagios/plugins/check_ntp_time -H 192.168.50.2 -v
> sending request to peer 0
> re-sending request to peer 0
> re-sending request to peer 0
> re-sending request to peer 0
> re-sending request to peer 0
> re-sending request to peer 0
> re-sending request to peer 0
> NTP CRITICAL: No response from NTP server
>
>
> But a request on localhost seems to work :
>
> /usr/lib64/nagios/plugins/check_ntp_time -H localhost -v
> sending request to peer 0
> response from peer 0: offset -4,291534424e-06
> sending request to peer 0
> response from peer 0: offset -2,002716064e-05
> sending request to peer 0
> response from peer 0: offset -2,062320709e-05
> sending request to peer 0
> response from peer 0: offset -1,752376556e-05
> sending request to peer 1
> re-sending request to peer 1
> re-sending request to peer 1
> re-sending request to peer 1
> re-sending request to peer 1
> re-sending request to peer 1
> re-sending request to peer 1
> discarding peer 1: stratum=0
> overall average offset: -4,291534424e-06
> NTP OK: Décalage -4,291534424e-06
> secs|offset=-0,000004s;60,000000;120,000000;
>
>
>
> The configuration of ntpd daemon are strictly the same on both servers.
>
> Has anyone an idea to help me ?
>
> Best regards
>
>
> ------------------------------------------------------------------------------
> Better than sec? Nothing is better than sec when it comes to
> monitoring Big Data applications. Try Boundary one-second
> resolution app monitoring today. Free.
> http://p.sf.net/sfu/Boundary-dev2dev
> _______________________________________________
> Nagios-users mailing list
> Nagios-users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nagios-users
> ::: Please include Nagios version, plugin version (-v) and OS when
> reporting any issue.
> ::: Messages without supporting info will risk being sent to /dev/null
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20120403/c2a1055a/attachment.html>
-------------- next part --------------
------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second 
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
-------------- next part --------------
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null