Re: [Nagios-users] check_ntp_peer parsing error

2013-07-01 Thread Marc Haber
On Sat, Jun 29, 2013 at 04:01:55PM +0200, Holger Weiß wrote:
 JFTR:
 * Marc Haber mh+nagios-us...@zugschlus.de [2013-06-26 21:22]:
  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,00, stratum=-1, truechimers=6| 
  jitter=-1,00;10,00;20,00;0,00 stratum=-1;2;2;0;16 
  truechimers=6;0;0;0
 
 This is probably caused by a bug in Force10 switches mentioned here:
 
 http://news.ntppool.org/2013/06/ipv6-monitoring-problems-for-g.html
 
 Due to that bug, the check_ntp_peer requests got duplicated on their way
 to the server, and the server therefore sent multiple responses per
 request.  check_ntp_peer then stumbled over those duplicated responses.
 That's a bug, I'll fix it later today.
 
 Thanks to Marc for providing tcpdump output and for his help with
 tracking the issue down.

This was really fun to investigate. Thanks for help ans inspiration.

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@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

Re: [Nagios-users] check_ntp_peer parsing error

2013-06-29 Thread Holger Weiß
JFTR:

* Marc Haber mh+nagios-us...@zugschlus.de [2013-06-26 21:22]:
 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,00, stratum=-1, truechimers=6| 
 jitter=-1,00;10,00;20,00;0,00 stratum=-1;2;2;0;16 
 truechimers=6;0;0;0

This is probably caused by a bug in Force10 switches mentioned here:

http://news.ntppool.org/2013/06/ipv6-monitoring-problems-for-g.html

Due to that bug, the check_ntp_peer requests got duplicated on their way
to the server, and the server therefore sent multiple responses per
request.  check_ntp_peer then stumbled over those duplicated responses.
That's a bug, I'll fix it later today.

Thanks to Marc for providing tcpdump output and for his help with
tracking the issue down.

Holger

--
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


[Nagios-users] check_ntp_peer parsing error

2013-06-26 Thread Marc Haber
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,00, stratum=-1, truechimers=6| 
jitter=-1,00;10,00;20,00;0,00 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.8911.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  1778.0543.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.702 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 candidatesys_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.peersys_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@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