check_dig display error

[Marc Powell]

On Oct 16, 2008, at 11:07 AM, rick wrote:

> Nagios DISPLAY OUTPUT
> Host    Service  Status  Last Check            Duration
> xx.tx   DIG      WARNING 10-16-2008 10:25:28   0d 21h 23m 58s
> Attempt  Status Information
> 3/3 	 DNS WARNING - 0.072 seconds response time (ns.xx.net. 3600 IN  
> A xx.xx.8.2)

At a basic level, there is a discrepency between the record that's  
being checked here (ns.xx.net) and what you tested below (www.xx.net).  
That's a clue to your issue.

> Nagios command line output
> ./check_dig -H ns.xxx.net -l www.xx.net -T A -w 3.0  -c 5.0
> DNS OK - 0.039 seconds response time (www.xx.net.  3600 IN A
> xx.xx.179.67)|time=0.038771s;3.000000;5.000000;0.000000
>
> checkcommands.cfg
> # 'check_dig' command definition
> define command{
>         command_name    check_dig
>         command_line    $USER1$/check_dig -H $HOSTADDRESS$ -l $ARG1$  
> -T $ARG2$ -w 3.0 -c 5.0
>          }

> services.cfg
> # Service definition
> define service{
{chop}
>
>         check_command                   check_dig!ns.xx.net! 
> www.xx.net!A

$ARG1$ = ns.xx.net, $ARG2$ = www.xx.net, $ARG3$ = A

Final command run by nagios is --

/path/to/check_dig - H <address from host definition> -l ns.xx.net -T www.xx.net 
  -w 3.0 -c 5.0

You're trying to look up a record of type 'www.xx.net' for the  
hostname 'ns.xx.net'. It's not a valid record type so you get  WARNING  
from check_dig no matter what the response time is.

--
Marc


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
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