Page 1 of 1

Re: [Nagios-devel] Unable to define empty check_command

Posted: Sun Jan 08, 2006 12:24 am
by Guest
On Sat, Jan 07, 2006 at 03:22:41PM -0600, Marc Powell wrote:
>
>
> > -----Original Message-----
> > From: [email protected] [mailto:nagios-devel-
> > [email protected]] On Behalf Of Dmitry Sivachenko
> > Sent: Saturday, January 07, 2006 9:25 AM
> > To: [email protected]
> > Subject: [Nagios-devel] Unable to define empty check_command
> >
> > Hello!
> >
> > We are using nagios 2.0b6.
>
> [chop]
>
> >
> > 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?
>
> Leave out the check_command entirely --
>
> define host {
> name h2
>
> register 0
> }
>
> Note that by specifying 'register 0' you are telling Nagios that this is
> a template to be applied against a real host definition and not an
> actual host definition itself. That really doesn't make much sense when
> you specify a 'name' parameter.
>


I am unable to entirely leave check_command parameter in the case when
I derive this host definition from another which did use check_command.

I want to be able to redefine check_command to empty value.





This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]