Hosts where frequently turned off

[Andreas Ericsson]

Chrigi Hartmann wrote:
>>>And what is whit my second problem? when I define the command
>>>check_dummy and the host like in your example, then nagios would not
>>>start. i have the error: 
>>>Host check command 'check_dummy!0' specified
>>>for host 'wkst13.lan.webmeischter.ch' is not defined anywhere!
>>>
>>
>>Read the docs. You can't specify arguments for host-checks in Nagios 
>>1.x. It's available in 2.x though, so you might want to upgrade. In
>>2.0 you also have the option to force host-checks even if no services
>>have failed.
> 
> I read the docs! But I have not found a description for the difference
> of the checkcommand.cfg and the command.cfg file ;-(  And it is not
> logical for me, why my 'check_dummy' command is not working fine. a
> other check like check_http is registred with the same shema like my
> check_dummy... 
> 

The name of the file has nothing to do with it. What I meant was that 
host object definitions can't pass arguments to their check_command.

When you specify check_dummy!0 as check_command for a host, nagios goes 
looking for a command_name of check_dummy!0, instead of check_dummy 
where it can replace the $ARG1$ macro with 0 (which is the first 
argument). Just don't use exclamation points in check_command for hosts.

> Thx for your reply ;)
> 

You're welcome.

> Chrigi Hartmann

-- 
Andreas Ericsson                   andreas.ericsson at op5.se
OP5 AB                             www.op5.se
Lead Developer


-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
_______________________________________________
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