check_ntp_peer parsing error
Marc Haber
mh+nagios-users at zugschlus.de
Wed Jun 26 21:22:36 CEST 2013
Hi,
I have a system running Debian oldstable with Nagios-Plugins 1.4.15. A
few weeks ago, my check_ntp_peer checks have started acting up:
$ /usr/lib/nagios/plugins/check_ntp_peer --hostname=2001:1b18:f:4::2 --warning 3 --critical 5 --jwarn 10 --jcrit 20 --twarn 2: --tcrit 3: --swarn 2 --scrit 2 -v
3 candidate peers available
synchronization source found
Getting offset, jitter and stratum for peer e20a
parsing offset from peer e20a: error: unable to read server offset response.
parsing jitter from peer e20a: error: unable to read server jitter/dispersion response.
parsing stratum from peer e20a: error: unable to read server stratum response.
NTP CRITICAL: Offset unknown, jitter=-1,000000, stratum=-1, truechimers=6| jitter=-1,000000;10,000000;20,000000;0,000000 stratum=-1;2;2;0;16 truechimers=6;0;0;0
The server itself is reachable and gives plausible answers:
$ ntpq -c pe 2001:1b18:f:4::2
remote refid st t when poll reach delay offset jitter
==============================================================================
+ptbtime1.ptb.de .PTB. 1 u 17 64 177 26.891 1.663 1.340
+ptbtime2.ptb.de .PTB. 1 u 14 64 177 27.015 -0.286 1.271
-ns1.customer-re 192.53.103.104 2 u 18 64 177 8.054 3.469 0.835
-130.149.220.2 130.133.1.10 2 u 20 64 177 21.243 -0.139 1.154
*ntp0.rrze.ipv6. .GPS. 1 u 19 64 177 21.170 -5.249 1.345
-stratum2-2.NTP. 129.70.130.70 2 u 15 64 177 21.216 -2.147 1.039
$ ntpq -c associations 2001:1b18:f:4::2
ind assid status conf reach auth condition last_event cnt
===========================================================
1 57862 943a yes yes none candidate sys_peer 3
2 57863 9424 yes yes none candidate reachable 2
3 57864 9324 yes yes none outlyer reachable 2
4 57865 9324 yes yes none outlyer reachable 2
5 57866 963a yes yes none sys.peer sys_peer 3
6 57867 9324 yes yes none outlyer reachable 2
$
This behavior does not happen with all of my check_ntp_peer checks. I
have not yet found out under which circumstances this behavior happens.
For your reference, I have currently opened the ntp server on the IPv6
address listed above for in-depth queries from anywhere.
What is going wrong? Is this a bug with check_ntp_peer?
Greetings
Marc
--
-----------------------------------------------------------------------------
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Mannheim, Germany | lose things." Winona Ryder | Fon: *49 621 31958061
Nordisch by Nature | How to make an American Quilt | Fax: *49 621 31958062
------------------------------------------------------------------------------
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 at 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
More information about the Users
mailing list