"Connection refused" with check_tcp and derivates

[Marc Powell]

On Jul 30, 2009, at 10:02 AM, shacky wrote:

>> Not without an example host, service and command definition. Without
>> those, we'd be randomly guessing. All we can say at this point is  
>> what
>> you're running on the command line is not what you've told nagios to
>> run.
>
> Oh, sorry. This is what you asked for:
>
> commands.cfg:
>
> # 'check_tcp' command definition
> define command{
>        command_name    check_tcp
>        command_line    $USER1$/check_tcp -H $HOSTADDRESS$ -p $ARG1$  
> $ARG2$
>        }
>
> # 'check_pop' command definition
> define command{
>        command_name    check_pop
>        command_line    $USER1$/check_pop -H $HOSTADDRESS
>        }

I'm sure you mean $HOSTADDRESS$ here. $HOSTADDRESS is a shell  
environment variable, likely NULL. $HOSTADDRESS$ is a nagios macro for  
the host's address which is what you want.

--
Marc


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
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