Plugin output discrepancy Nagios 2.0b4 (RHEL3 RPM)

[Marc Powell]

> -----Original Message-----
> From: Scott, Casey [mailto:Casey.Scott at wizards.com]
> Sent: Monday, September 19, 2005 1:57 PM
> To: Marc Powell; nagios-users at lists.sourceforge.net
> Subject: RE: [Nagios-users] Plugin output discrepancy Nagios 2.0b4
(RHEL3
> RPM)

> > > checkcommands.cfg
> > >
> > > define command{
> > >         name            check_temptraxe
> > >         command_name    check_temptraxe
> > >         command_line    $USER1$/check_temptraxe -H $HOSTADDRESS$
-p
> > > $ARG1$ -w $ARG2$ -c $ARG3$
> > >         }

> 
> I don't know how the check_command was removed from the original post.
> This is the relevant hosts.cfg entry. Should I be assigning parameter
> values in there as well? E.g.  check_command  check_temptraxe!1!75!80

Yes since the command definition above is expecting them. Since $ARG1$,
$ARG2$ and $ARG3$ are null at best, Nagios is trying to execute
'check_temptraxe -H 10.1.1.85 -p -w -c' using the definition below,
which is incorrect. 

> 
> define host {
> use                            generic-host
> host_name                      temptrax
> alias                          Datacenter Temperature Probes
> address                         10.1.1.85
> check_command                  check_temptraxe
> max_check_attempts             10
> notification_interval          120
> notification_period            24x7
> notification_options           d,u,r
> }

--
Marc


-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. 
Download it for free - -and be entered to win a 42" plasma tv or your very
own Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
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