Check_NTP issues

[Tiago Cruz]

Darren Dunham wrote:

> This machine is not responding.  It may not be running ntpd, or the
> communication may be blocked in some manner (restrictions on the server,
> firewall on the network, etc.)

Yes, the ntpd daemon is only listen no 127.0.0.1. I did a test, please look:

1- On host 10.0.0.91, in /etc/ntp.conf, I've added:
restrict 10.0.0.173 nomodify

2- On host 10.0.0.173, now I can run this command:

trinity:~# ntpq -p 10.0.0.91
      remote           refid      st t when poll reach   delay   offset 
  jitter
==============================================================================
10.0.0.91       .INIT.          16 u    -   64    0    0.000    0.000 
4000.00

3- Still on host 10.0.0.173, I re-synchronized with my NTP server (is 
the 10.0.0.91):

trinity:~# /etc/init.d/ntpdate restart
Running ntpdate to synchronize clock.

4- When I try compare my clock my the NTP server, I get this error:

  trinity:~# ./check_ntp -v -H 10.0.0.91
ntperr = 0
      remote           refid      st t when poll reach   delay   offset 
  jitter
No match!
==============================================================================
No match!
  10.0.0.91       .INIT.          16 u    -  256    0    0.000    0.000 
4000.00
No match!
Argument "(not parsed)" isn't numeric in abs at 
/.../bin-1.4.2/libexec/check_ntp line 355.
NTP WARNING: Desynchronized peer server found

You (list), know how can I solve this another problem?
Many thanks!


-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
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