Unable to define empty check_command
Dmitry Sivachenko
mitya at cavia.pp.ru
Sat Jan 7 16:25:17 CET 2006
Hello!
We are using nagios 2.0b6.
According to the manual for nagios-2.x at www.nagios.org:
(Host definition, the description of check_command):
-------------------------------------------------------------------
This directive is used to specify the short name of the command that should
be used to check if the host is up or down. Typically, this command would try
and ping the host to see if it is "alive". The command must return a status
of OK (0) or Nagios will assume the host is down. If you leave this argument
blank, the host will not be checked - Nagios will always assume the host is up.
This is useful if you are monitoring printers or other devices that are
frequently turned off. The maximum amount of time that the notification
command can run is controlled by the host_check_timeout option.
--------------------------------------------------------------------
We also found this feature (leaving check_command blank) very useful. But in
our configuration we have:
define host {
name h1
check_command check-host-alive
<...>
register 0
}
define host {
name h2
check_command
<...>
register 0
}
And nagios reports:
# nagios -v nagios.cfg
Nagios 2.0b6
Copyright (c) 1999-2005 Ethan Galstad (http://www.nagios.org)
Last Modified: 11-14-2005
License: GPL
Reading configuration data...
Error: Could not add object property in file '/usr/local/etc/nagios/templates.cfg' on line 21.
.....
Is it possible to allow one to define empty check_command to disable check
for host health as described in the manual?
Thanks in advance!
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
More information about the Developers
mailing list