problem with instance_name variable in ndomod.cfg

[Marc Powell]

Hi!

I don't use ndoutils but I think I can help. See comments below --

> -----Original Message-----
> From: nagios-users-bounces at lists.sourceforge.net [mailto:nagios-users-
> bounces at lists.sourceforge.net] On Behalf Of Roger
> Sent: Wednesday, October 10, 2007 6:21 PM
> To: Nagios Users mailinglist
> Subject: [Nagios-users] problem with instance_name variable in
ndomod.cfg
> 
> I'm trying to integrate NDOutils into my Nagios 2.9 CentOS setup, I'm
> getting a weird error when I add the following two lines in my
> nagios.cfg file, per the README in NDOutils.
> 
> ********* /etc/nagios.cfg *****************
> 
> #per README in NDOutils
> broker_module=/usr/bin/ndomod.o
> config_file=/etc/nagios/ndomod.cfg
> #config_file OR cfg_file ?
> 
> ********************************************
> 
> nagios -v /etc/nagios/nagios.cfg gives me:
> 
> "Error in configuration file '/etc/nagios/nagios.cfg' - Line 230
> (UNKNOWN VARIABLE)"

Is line 230 the line beginning 'config_file...'? My reading of the
ndoutils README is that those should be on one line with the config_file
as an argument to ndomod.o --

broker_module=/usr/bin/ndomod.o config_file=/etc/nagios/ndomod.cfg

The only directive that nagios understands above is broker_module.
That's why you're seeing the other errors when you try to force nagios
to parse 'config_file' and 'instance_name' as regular nagios directives.
Those are only understood by ndomod.

--
Marc 

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
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