Marking Invalid because:
1. No thresholds were specified - specifying some kind of thresholds would
actually cause it to monitor properly.
2. Check_ntp is deprecated and both replacement plugins, check_ntp_peer and
check_ntp_time, should not show this weird behaviour.
** Changed in:
This was a feature since check_ntp had multiple possible possible
thresholds (-w/-c, -j/-k). Without any threshold specified it was not
checking anything besides receiving a response.
check_ntp_* does return critical on these cases and check_ntp is
deprecated and its behavior will not change.
--
** Changed in: nagios-plugins (Ubuntu)
Status: New = Confirmed
--
ntp check is worse than useless
https://bugs.launchpad.net/bugs/162389
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nagios-plugins in ubuntu.
--
I can't reproduce this on my desktop machine or on my nagios server.
I can; with up-to-date hardy:
# /usr/lib/nagios/plugins/check_ntp -H 127.0.0.1; echo $?
NTP OK: Offset unknown|
0
# ntpq -p
No association ID's returned
#
What version are you running (check_ntp -V)?
#
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
