Page 1 of 1

Upgrade 3.5 to 4.0 parsing errors

Posted: Mon Oct 07, 2013 5:43 am
by Blackbit
Hi all,

after upgrading my Nagios from 3.5 to 4.0 i get the error "Error processing object config files" without any further information. Even checking the configuration files with /usr/local/nagios/bin/nagios -v -v /usr/local/nagios/etc/nagios.cfg doesn't tell me what's set up wrong. All depcrecates and obsoleted functions mentioned on http://nagios.sourceforge.net/docs/nagi ... tsnew.html are removed, or corrected. I double-checked the file format (encoding, tabs, etc.).

How can i debug such a problem?

Regards,
David

Re: Upgrade 3.5 to 4.0 parsing errors

Posted: Mon Oct 07, 2013 9:15 am
by slansing
Can you run the configuration verification and show us the output? Where were you getting that error from, restarting nagios? Use only one "-v" when verifying:

Code: Select all

/usr/local/nagios/bin/nagios -v /usr/local/nagios/etc/nagios.cfg

Re: Upgrade 3.5 to 4.0 parsing errors

Posted: Mon Oct 07, 2013 9:21 am
by Blackbit
Of course i can post that, but as i said, it doesn't help anything :(

# /usr/local/nagios/bin/nagios -v /usr/local/nagios/etc/nagios.cfg

Code: Select all

Nagios Core 4.0.0
Copyright (c) 2009-present Nagios Core Development Team and Community Contributors
Copyright (c) 1999-2009 Ethan Galstad
Last Modified: 09-20-2013
License: GPL

Website: http://www.nagios.org
Reading configuration data...
   Read main config file okay...
   Error processing object config files!


***> One or more problems was encountered while processing the config files...

     Check your configuration file(s) to ensure that they contain valid
     directives and data defintions.  If you are upgrading from a previous
     version of Nagios, you should be aware that some variables/definitions
     may have been removed or modified in this version.  Make sure to read
     the HTML documentation regarding the config files, as well as the
     'Whats New' section to find out what has changed.

Re: Upgrade 3.5 to 4.0 parsing errors

Posted: Mon Oct 07, 2013 3:45 pm
by sreinhardt
Well, let's verify a few things, since it seems to have issues with the nagios.cfg directly.

Code: Select all

ll /usr/local/nagios/etc/nagios.cfg
grep -i 'nag' /etc/group 

su nagios
cat /usr/local/nagios/etc/nagios.cfg