On Saturday, 01 December 2007 17:07:45 -0600, Marc Powell wrote: > > check_command: [...] 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.
> > Error: Host check command '(null)' specified for host 'sparky' is
> > not defined anywhere!
> > I'm missing something from the documentation?
> No, it's just awkward wording. You need to leave the line out
> entirely; don't even specify the keyword 'check_command' within the
> host definition.
Oh, well. In addition to it, I've deleted the line "use linux-server" to
avoid to use the check-host-alive command in the template definition.
This is my host definition:
define host{
host_name sparky
alias nagios server
address 127.0.0.1
max_check_attempts 10
icon_image base/sun40.gif
statusmap_image base/sun40.gd2
contact_groups nagios admins
notification_period sysadmin_time
}
I didn't get errors after Nagios restart, but it continue displaying the
host in down state, yet.
Thanks for your response, Marc.
Regards,
Daniel
--
Daniel Bareiro - System Administrator
Fingerprint: BFB3 08D6 B4D1 31B2 72B9 29CE 6696 BF1B 14E6 1D37
Powered by Debian GNU/Linux Etch - Linux user #188.598
signature.asc
Description: Digital signature
------------------------------------------------------------------------- SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
_______________________________________________ Nagios-users mailing list [email protected] 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
