[prev in list] [next in list] [prev in thread] [next in thread]
List: nagios-users
Subject: Re: [Nagios-users] check_ntp_time offset unknown
From: Giles Coochey <giles () coochey ! net>
Date: 2013-06-18 15:35:03
Message-ID: 51C07E27.7000400 () coochey ! net
[Download RAW message or body]
[Attachment #2 (multipart/signed)]
[Attachment #4 (multipart/alternative)]
On 14/06/2013 15:10, Bennett, Jan wrote:
>
> 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.
>
>
I get this shortly after a NTP client has booted up. Once NTP has been
running for a while it goes away.
--
Regards,
Giles Coochey, CCNP, CCNA, CCNAS
NetSecSpec Ltd
+44 (0) 7983 877438
http://www.coochey.net
http://www.netsecspec.co.uk
giles@coochey.net
[Attachment #7 (text/html)]
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 14/06/2013 15:10, Bennett, Jan
wrote:<br>
</div>
<blockquote
cite="mid:E11B0F59D3334D469B36FCA07490BA8C186E67EF@NTTAEXMB01.ntta.local"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<meta name="Generator" content="Microsoft Word 12 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal">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.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">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.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">From the client that is reporting the
unknown offset, I can run the following:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span
style="font-size:9.0pt;font-family:"Courier
New";color:seagreen;background:white">#
./check_ntp_time -H localhost</span><span
style="font-size:9.0pt;font-family:"Courier
New";color:seagreen"><br>
<span style="background:white">NTP CRITICAL: Offset unknown|</span><br>
<span style="background:white"># ./check_ntp_time -V</span><br>
<span style="background:white">check_ntp_time v1.4.16
(nagios-plugins 1.4.16)</span><br>
<span style="background:white"># ntpdc -p</span><br>
<span style="background:white"> remote \
local
st poll reach delay offset \
disp</span><br>
<span style="background:white">=======================================================================</span><br>
<span style="background:white">=LOCAL(0) \
127.0.0.1
10 64 17 0.00000 0.000000 \
0.96858</span><br> <span style="background:white">*timeserver1
xxx.xxx.xxx.xxx 2 64 17 \
0.00098 4.956048 0.00580<o:p></o:p></span></span></p> <p \
class="MsoNormal"><span style="font-size:9.0pt;font-family:"Courier
New";color:seagreen;background:white">#
/usr/local/nagios/libexec/check_ntp_time -v -H localhost</span><span
style="font-size:9.0pt;font-family:"Courier
New";color:seagreen"><br>
<span style="background:white">sending request to peer 0</span><br>
<span style="background:white">response from peer 0: offset
-2.777669579e-07</span><br>
<span style="background:white">sending request to peer 0</span><br>
<span style="background:white">response from peer 0: offset
-2.161832526e-07</span><br>
<span style="background:white">sending request to peer 0</span><br>
<span style="background:white">response from peer 0: offset
-4.009343684e-07</span><br>
<span style="background:white">sending request to peer 0</span><br>
<span style="background:white">response from peer 0: offset
-1.987209544e-07</span><br>
<span style="background:white">discarding peer 0: stratum=0</span><br>
<span style="background:white">overall average offset: 0</span><br>
<span style="background:white">NTP CRITICAL: Offset \
unknown|<o:p></o:p></span></span></p> <p class="MsoNormal"><span
style="font-size:9.0pt;font-family:"Courier
New";color:seagreen;background:white"><o:p> </o:p></span></p>
<p class="MsoNormal">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.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Also, I am unable to check a remote NTP
server from these clients as they do not have access to the
outside world.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">It has been suggested that the stratum=0
may be the culprit, but I’m not sure of my options \
here.<o:p></o:p></p> <p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Any help would be greatly appreciated.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<br>
</div>
</blockquote>
I get this shortly after a NTP client has booted up. Once NTP has
been running for a while it goes away.<br>
<pre class="moz-signature" cols="72">--
Regards,
Giles Coochey, CCNP, CCNA, CCNAS
NetSecSpec Ltd
+44 (0) 7983 877438
<a class="moz-txt-link-freetext" \
href="http://www.coochey.net">http://www.coochey.net</a> <a \
class="moz-txt-link-freetext" \
href="http://www.netsecspec.co.uk">http://www.netsecspec.co.uk</a> <a \
class="moz-txt-link-abbreviated" \
href="mailto:giles@coochey.net">giles@coochey.net</a> </pre>
</body>
</html>
["smime.p7s" (application/pkcs7-signature)]
------------------------------------------------------------------------------
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
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic