Your message dated Tue, 26 May 2009 13:56:07 +0200
with message-id <[email protected]>
and subject line Re: [Pkg-nagios-devel] Bug#509589: check_ntp: wrong output for
host with both A and AAAA record
has caused the Debian Bug report #509589,
regarding check_ntp: wrong output for host with both A and AAAA record
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
509589: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=509589
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: nagios-plugins-basic
Version: 1.4.5-1etch1
Severity: normal
Hi,
Please consider this:
$ host -t any lipton.aai.niif.hu
lipton.aai.niif.hu A 193.225.14.195
lipton.aai.niif.hu AAAA 2001:738:0:701:80:C1E1:EC3:0
$ /usr/lib/nagios/plugins/check_ntp -H lipton.aai.niif.hu -v
sending request to peer 0
sending request to peer 1
response from peer 1: offset -2.680183388e-05
sending request to peer 1
response from peer 1: offset -1.871510176e-05
sending request to peer 1
response from peer 1: offset 3.834080417e-06
sending request to peer 1
response from peer 1: offset -3.614556044e-05
re-sending request to peer 0
re-sending request to peer 0
re-sending request to peer 0
re-sending request to peer 0
re-sending request to peer 0
re-sending request to peer 0
overall average offset: nan
NTP OK: Offset nan secs|offset=nan
This isn't serious, since one uses IP addresses anyway, but still a bug.
Sure the client doesn't respond to IPv6 packets, but its offset isn't NaN.
Regards,
Feri.
-- System Information:
Debian Release: 5.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
--- End Message ---
--- Begin Message ---
Version: 1.4.12-1
Hi Ferenc,
On Tuesday 23 December 2008, Ferenc Wagner wrote:
> Please consider this:
>
> $ host -t any lipton.aai.niif.hu
> lipton.aai.niif.hu A 193.225.14.195
> lipton.aai.niif.hu AAAA 2001:738:0:701:80:C1E1:EC3:0
> $ /usr/lib/nagios/plugins/check_ntp -H lipton.aai.niif.hu -v
> sending request to peer 0
> sending request to peer 1
> response from peer 1: offset -2.680183388e-05
> sending request to peer 1
> response from peer 1: offset -1.871510176e-05
> sending request to peer 1
> response from peer 1: offset 3.834080417e-06
> sending request to peer 1
> response from peer 1: offset -3.614556044e-05
> re-sending request to peer 0
> re-sending request to peer 0
> re-sending request to peer 0
> re-sending request to peer 0
> re-sending request to peer 0
> re-sending request to peer 0
> overall average offset: nan
> NTP OK: Offset nan secs|offset=nan
>
> This isn't serious, since one uses IP addresses anyway, but still a bug.
> Sure the client doesn't respond to IPv6 packets, but its offset isn't NaN.
upstream reported[1] that this should be fixed with 1.4.12 (git commit
34cfb0c1034a6b3289e9aca567fd2393126aa80a). Could you please check the package
from lenny? If you still has problems, feel free to reopen the bug.
Thanks and with kind regards, Jan.
[1]
http://sourceforge.net/tracker/index.php?func=detail&aid=2550224&group_id=29880&atid=397597
--
Never write mail to <[email protected]>, you have been warned!
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GIT d-- s+: a- C+++ UL++++ P+ L+++ E- W+++ N+++ o++ K++ w--- O M V- PS PE
Y++ PGP++ t-- 5 X R tv- b+ DI- D++ G++ e++ h-- r+++ y+++
------END GEEK CODE BLOCK------
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
