Hello,
I am using nagios-plugins version 1.4.15 on a vmware machine running on ESX 4.0. Time is working perfectly on the vmware machine, but the nagios check “check_ntp_time” returns a offset 0 randomly. The result is a NTP CRITICAL warning.
When the check works ok, it returns a NTP OK with offset 0.0006. Bottumline is when the offset is exactly 0 there is a NTP CRITICAL warning. When the offset is, for example 0.0006 (with numbers behand the dot), then the check returns a NTP OK.
Example of good check (what’s the line “overall average offset: -0.004927828209”):
:/usr/local/nagios/libexec # ./check_ntp_time -H ntpserv -w 2 -c 3 -v
sending request to peer 0
response from peer 0: offset -0.004927828209
sending request to peer 0
response from peer 0: offset -0.002302596462
sending request to peer 0
response from peer 0: offset -0.002287493728
sending request to peer 0
response from peer 0: offset -0.002308015944
overall average offset: -0.004927828209
NTP OK: Offset -0.004927828209 secs|offset=-0.004928s;2.000000;3.000000;
Example of a bad check (what’s the line “overall average offset: 0”) :
:/usr/local/nagios/libexec # ./check_ntp_time -H ntpserv -w 2 -c 3 -v
sending request to peer 0
re-sending request to peer 0
re-sending request to peer 0
response from peer 0: offset -0.0006234658649
sending request to peer 0
response from peer 0: offset -0.0007095236797
sending request to peer 0
response from peer 0: offset -0.0006647066912
sending request to peer 0
response from peer 0: offset -0.0006637415499
discarding peer 0: stratum=0
overall average offset: 0
NTP CRITICAL: Offset unknown|