I am stuck on 3.0rc2 because of a change that seemed to have been made
between 3.0rc2 and rc3 with regards to the behavior for parsing
configuration lines that end with a backslash. The problem is
described in a post to nagios-devel back in February/2008 by Tobias
Klausmann ( schwarzvogel.de>) and I have copied it to
the end of this message for reference.
I have just downloaded 3.0.4 to see if this problem has been resolved
and it still remains. I was able to upgrade from Nagios 2.x to 3.0rc2
at the beginning of the year without issue but cannot upgrade past
3.0rc2 because of this behavior with the backslashes at the end of
config lines.
[nagios@licorice nagios-3.0.4]$ /usr/local/nagios-dev/bin/nagios -v
/usr/local/nagios-dev/etc/nagios.cfg
Nagios 3.0.4
Copyright (c) 1999-2008 Ethan Galstad (http://www.nagios.org)
Last Modified: 10-15-2008
License: GPL
Reading configuration data...
Error: Unexpected token or statement in file
'/usr/local/nagios-dev/etc/objects/services/serviceext/EXCH02.cfg' on
line 4.
***> 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.
Inspecting serviceext/EXCH02.cfg shows the problem is with line 2
which is commented out but ends with a backslash. If I remove the
offending backslash, the configuration parser will complain about a
line further down that also is commented-out and also ends with a
backslash. I've added the line numbers below for clarity for the
object with the first offending backslash.
1.
2. # ExtInfo for EXCH02, Disk S:\Restore\
3. define serviceextinfo{
4. host_name EXCH02
5. icon_image dot.png' border="0"> schwarzvogel.de