Hi Mike,<div>here is another sample output I got for a server that seems to be perfectly sync'ed according to ntpq, the check_ntp_peer plugin now doesn't even report an offset in the debug logs.</div><div><br></div>
<div><div>[root@rapture ~]# /usr/local/nagios/libexec/check_ntp_peer -v -H xxx.xxx.xxx.xxx</div><div>0 candiate peers available</div><div>warning: no synchronization source found</div><div>warning: LI_ALARM bit is set</div>
<div>NTP CRITICAL: Server not synchronized, Offset unknown|</div><div>[root@rapture ~]# ntpq xxx.xxx.xxx</div><div>ntpq> peers</div><div> remote refid st t when poll reach delay offset jitter</div>
<div>==============================================================================</div><div> *xxx.xxx.xxx.xxx xxx.xxx.xxx.xxx 2 u 12 64 37 1.303 42.206 28.959</div><div>ntpq> q</div><div><br></div><div>
Elie</div><div><br></div><div><br><div class="gmail_quote">On Wed, Feb 17, 2010 at 10:52 AM, Michael Saldivar <span dir="ltr"><<a href="mailto:mike.saldivar@advocatecreditrepair.com">mike.saldivar@advocatecreditrepair.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div><div></div><div class="h5"><div class="gmail_quote">On Wed, Feb 17, 2010 at 5:55 AM, Elie Delorme <span dir="ltr"><<a href="mailto:elie@at-m.ca" target="_blank">elie@at-m.ca</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left:1px solid rgb(204, 204, 204);margin:0pt 0pt 0pt 0.8ex;padding-left:1ex">
<div>All servers I poll have the same ntp configuration, it looks like the plugin can't handle some offsets,</div><div>most of the time everything is fine, then I randomly get an "Offset unknown" for a server.</div>
<div><br></div><div>I found a couple references to a bug involving a leap second, but they were also saying that it should be corrected</div><div>in 1.4.12.</div><div><br></div><div>I have tried restarting the ntp service a couple times but it did not help a bit.</div>
<div>I also checked with ntpq and everything seems fine.</div><div><br></div><div>My version is 1.4.14 ( latest available on sourceforge):</div><div># /usr/local/nagios/libexec/check_ntp_time --help</div><div>check_ntp_time v1.4.14 (nagios-plugins 1.4.14)</div>
<div>Copyright (c) 2006 Sean Finney</div><div>Copyright (c) 2006-2008 Nagios Plugin Development Team</div><div> <<a href="mailto:nagiosplug-devel@lists.sourceforge.net" target="_blank">nagiosplug-devel@lists.sourceforge.net</a>></div>
<div><br></div><div>Here is the output I get when executing the plugin from the command line:</div><div># /usr/local/nagios/libexec/check_ntp_time -v -H xxx.xxx.xxx.xxx</div><div>sending request to peer 0</div><div>response from peer 0: offset -0.01565231133</div>
<div>sending request to peer 0</div><div>response from peer 0: offset -0.01617310685</div><div>sending request to peer 0</div><div>response from peer 0: offset -0.01564534893</div><div>sending request to peer 0</div><div>
response from peer 0: offset -0.01622254931</div><div>discarding peer 0: stratum=0</div><div>overall average offset: 0</div><div>NTP CRITICAL: Offset unknown|<br>
</div></blockquote></div><br></div></div>Have you checked the full time and date on these machines to make sure that they are actually correct? Do they have a firewall rule blocking external NTP calls?<br><br>-Mike<br>
<br>------------------------------------------------------------------------------<br>
SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,<br>
Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW<br>
<a href="http://p.sf.net/sfu/solaris-dev2dev" target="_blank">http://p.sf.net/sfu/solaris-dev2dev</a><br>_______________________________________________<br>
Nagiosplug-help mailing list<br>
<a href="mailto:Nagiosplug-help@lists.sourceforge.net">Nagiosplug-help@lists.sourceforge.net</a><br>
<a href="https://lists.sourceforge.net/lists/listinfo/nagiosplug-help" target="_blank">https://lists.sourceforge.net/lists/listinfo/nagiosplug-help</a><br>
::: Please include plugins version (-v) and OS when reporting any issue.<br>
::: Messages without supporting info will risk being sent to /dev/null<br>
<br></blockquote></div><br></div></div>