[Nagiosplug-devel] [ nagiosplug-Bugs-1204541 ] check_ntp returns Critical when offset = 0.000000

[SourceForge.net]

Bugs item #1204541, was opened at 2005-05-18 16:48
Message generated for change (Settings changed) made by sghosh
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=397597&aid=1204541&group_id=29880

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Parsing problem
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Kenny Raby (kraby)
>Assigned to: Subhendu Ghosh (sghosh)
Summary: check_ntp returns Critical when offset = 0.000000

Initial Comment:
Debian sarge system:  check_ntp (nagios-plugins 1.4) 1.20

Occasionally when checking the NTP on the server on
which Nagios is running I get (IP Address obsured):

NTP CRITICAL: server x.x.x.x, stratum 4, offset
0.000000, delay 0.02565

I think these are the lines in the code:

    203         # An offset of 0.000000 with an error
is probably bogus. Actually,
    204         # it's probably always bogus, but let's
be paranoid here.
    205         if ($offset == 0) { undef $offset;}
    206 
    207         $ntpdate_error = defined ($offset) ?
$ERRORS{"OK"} : $ERRORS{"CRITICAL"};
    208         print "ntperr = $ntpdate_error \n" if
$verbose;

In this case I do not beleive the offset of 0.000000 is
bogus. 

The first part of the output with a -v is:

server x.x.x.x, stratum 3, offset 0.000000, delay 0.02563
ntperr = 2 
18 May 13:39:23 ntpdate[23726]: adjust time server
x.x.x.x offset 0.000000 sec
ntperr = 2 

Since these "CRITICAL" failures cause false alerts for
me I just commented out line 205 




----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=397597&aid=1204541&group_id=29880