[Nagiosplug-help] Check_dig returning warning state incorrectly

Hans Engelen engelenh at gmail.com
Fri Sep 23 09:33:02 CEST 2005


Hi all,
 I have some problems with the check_dig plugin.
 See here :
 [root at nagios plugins]# ./check_dig -H 10.10.10.1 <http://10.10.10.1> -l
host.domain.name <http://host.domain.name> -w 0.100 -c 0.250 -a
10.10.10.10<http://10.10.10.10>
DNS OK - 0.020 seconds response time
(host.domain.name<http://host.domain.name>.
1200 IN A 10.10.10.10 <http://10.10.10.10>)|time=0.020128s
;0.100000;0.250000;0.000000

[root at nagios plugins]# ./check_dig -H 10.10.10.1 <http://10.10.10.1> -l
host.domain.name <http://host.domain.name> -w 0.100 -c 0.250 -a
10.10.10.10<http://10.10.10.10>
DNS WARNING - 0.024 seconds response time
(host.domain.name<http://host.domain.name>.
1200 IN A 10.10.10.10 <http://10.10.10.10>)|time=0.023646s
;0.100000;0.250000;0.000000
 [root at nagios plugins]# ./check_dig -H 10.10.10.1 <http://10.10.10.1> -l
host.domain.name <http://host.domain.name> -w 0.100 -c 0.250 -a
10.10.10.10<http://10.10.10.10>
DNS OK - 0.020 seconds response time
(host.domain.name<http://host.domain.name>.
1200 IN A 10.10.10.10 <http://10.10.10.10>)|time=0.020145s
;0.100000;0.250000;0.000000
 As you can see the second time the check returned a WARNING state and I
can't for the life of me figure out why.
I am using the plugin from the most recent set (i.e. 1.4.2) now but had the
problem with 1.4.1 also.
 Dig output (no options)

; <<>> DiG 9.2.4 <<>>
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 1645
;; flags: qr rd ra; QUERY: 1, ANSWER: 13, AUTHORITY: 0, ADDITIONAL: 12

;; QUESTION SECTION:
;. IN NS

;; ANSWER SECTION:
. 18332 IN NS k.root-servers.net <http://k.root-servers.net>.
. 18332 IN NS l.root-servers.net <http://l.root-servers.net>.
. 18332 IN NS m.root-servers.net <http://m.root-servers.net>.
. 18332 IN NS a.root-servers.net <http://a.root-servers.net>.
. 18332 IN NS b.root-servers.net <http://b.root-servers.net>.
. 18332 IN NS c.root-servers.net <http://c.root-servers.net>.
. 18332 IN NS d.root-servers.net <http://d.root-servers.net>.
. 18332 IN NS e.root-servers.net <http://e.root-servers.net>.
. 18332 IN NS f.root-servers.net <http://f.root-servers.net>.
. 18332 IN NS g.root-servers.net <http://g.root-servers.net>.
. 18332 IN NS h.root-servers.net <http://h.root-servers.net>.
. 18332 IN NS i.root-servers.net <http://i.root-servers.net>.
. 18332 IN NS j.root-servers.net <http://j.root-servers.net>.

;; ADDITIONAL SECTION:
k.root-servers.net <http://k.root-servers.net>. 70733 IN A
193.0.14.129<http://193.0.14.129>
l.root-servers.net <http://l.root-servers.net>. 46102 IN A
198.32.64.12<http://198.32.64.12>
m.root-servers.net <http://m.root-servers.net>. 46102 IN A
202.12.27.33<http://202.12.27.33>
b.root-servers.net <http://b.root-servers.net>. 18332 IN A
192.228.79.201<http://192.228.79.201>
c.root-servers.net <http://c.root-servers.net>. 46102 IN A
192.33.4.12<http://192.33.4.12>
d.root-servers.net <http://d.root-servers.net>. 46102 IN A
128.8.10.90<http://128.8.10.90>
e.root-servers.net <http://e.root-servers.net>. 58134 IN A
192.203.230.10<http://192.203.230.10>
f.root-servers.net <http://f.root-servers.net>. 70733 IN A
192.5.5.241<http://192.5.5.241>
g.root-servers.net <http://g.root-servers.net>. 59934 IN A
192.112.36.4<http://192.112.36.4>
h.root-servers.net <http://h.root-servers.net>. 60834 IN A
128.63.2.53<http://128.63.2.53>
i.root-servers.net <http://i.root-servers.net>. 46102 IN A
192.36.148.17<http://192.36.148.17>
j.root-servers.net <http://j.root-servers.net>. 70733 IN A
192.58.128.30<http://192.58.128.30>

;; Query time: 2 msec
;; SERVER: 10.10.10.1#53(10.10.10.1 <http://10.10.10.1>)
;; WHEN: Fri Sep 23 18:21:09 2005
;; MSG SIZE rcvd: 433

I tried going back to the version in plugins 1.3.1 but unless I am mistaken
that version does not allow you to set warning and critical values for how
long the dns takes to respond. This is something I need though since on rare
occasions (cough) one of the Windows boxes running DNS gets a little ... ehm
... sluggish. A situation which impacts performance all around for scores of
applications.

Incidentally I am running all this on a Quad-CPU smp kernel 2.6.9 Red Hat EL
4 box. Scanning through recent messages that seems to be important too.

Any suggestions are welcome.

 Cheers,

Hans Engelen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-plugins.org/archive/help/attachments/20050923/8cb12064/attachment.html>


More information about the Help mailing list