check_ldap: Please specify the host name

Marc Powell marc at ena.com
Tue Jun 10 05:17:23 CEST 2008


On Jun 9, 2008, at 6:18 PM, Germán Gutiérrez wrote:

> (snip)
>>        command_line    $USER1$/check_nrpe!check_ldap -H $HOSTADDRESS 
>> $ -p $ARG1$ -b $ARG2$

Note that 'command_name check_ldap' was snipped.'

> (snip)
>> define service{
>>        use                            generic-service
>>        host_name                  server
>>        service_description       Ldap Status
>>        check_command           check_nrpe!check_ldap -H  
>> 192.168.100.80
>>        }
> $HOSTADDRESS$  will be replaced by "server"
> $ARG1$ will be replaced by 192.168.100.80
> and $ARG2$ will be empty.

Just to clear up any confusion, IFF the command at the top were named  
check_nrpe and the service above used it as a result, $HOSTADDRESS$  
would be the address from the host{} definition for 'server' (unknown  
to us), $ARG1$ would be 'check_ldap -H 192.168.100.80' and $ARG2$  
would be null.

The resulting command would have failed anyway for a number of reasons  
--

/path/to/plugins/check_nrpe!check_ldap -H <someaddress> -p check_ldap - 
H 192.168.100.80 -b

> looks like you need to pass proper parameters to the
> check_nrpe/check_ldap scripts.

More than that for sure.

--
Marc


-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.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





More information about the Users mailing list