We have implemented a NTP sync check in all of the NRDS checks that we are
rolling out right now but I've run into a bit of a snag.
I am getting returns of 'Offset Unknown' on all clients. It appears to only
happen for a short period of time (30 min or so) and then it will clear its
self up for a bit but the issue will always return.
>From the client that is reporting the unknown offset, I can run the following:
# ./check_ntp_time -H localhost
NTP CRITICAL: Offset unknown|
# ./check_ntp_time -V
check_ntp_time v1.4.16 (nagios-plugins 1.4.16)
# ntpdc -p
remote local st poll reach delay offset disp
=======================================================================
=LOCAL(0) 127.0.0.1 10 64 17 0.00000 0.000000 0.96858
*timeserver1 xxx.xxx.xxx.xxx 2 64 17 0.00098 4.956048 0.00580
# /usr/local/nagios/libexec/check_ntp_time -v -H localhost
sending request to peer 0
response from peer 0: offset -2.777669579e-07
sending request to peer 0
response from peer 0: offset -2.161832526e-07
sending request to peer 0
response from peer 0: offset -4.009343684e-07
sending request to peer 0
response from peer 0: offset -1.987209544e-07
discarding peer 0: stratum=0
overall average offset: 0
NTP CRITICAL: Offset unknown|
In my searches, I noticed a number of people reporting the same issue with the
supposed solution being to update your Nagios plugins to 1.4.13. I have done
so and am now running 1.4.16 without any change in the service check.
Also, I am unable to check a remote NTP server from these clients as they do
not have access to the outside world.
It has been suggested that the stratum=0 may be the culprit, but I'm not sure
of my options here.
Any help would be greatly appreciated.
Jan
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Nagios-users mailing list
Nagios-users@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
