Monitoring-Portal

Source code

Error: Unexpected token or statement in file '/usr/local/nconf/static_cfg/resource.cfg' on line 24.

Source code

/usr/bin/icinga -v /etc/icinga/icinga.cfg

Source code

grep -r static_cfg /etc/icinga

Source code

# grep -r cfg_ . | grep -v "\#cfg_"
./icinga.cfg:# extension) in a particular directory by using the cfg_dir
./icinga.cfg:cfg_dir=/etc/icinga/modules
./icinga.cfg:# object configuration files (see the cfg_file and cfg_dir options above).
./icinga.cfg:cfg_dir=/etc/icinga/nconf
# find /etc/icinga/modules -type s #returns nothing
# find /etc/icinga/nconf -type s #returns nothing

Source code

#
# Static configuration files
#
# List of folders containing additional files that you would like to make editable within NConf (basic text editing).
# We call these files 'static files', because they are not generated by NConf.
# All folders listed here will be included in the output file, together with the generated config.
# We recommend you to copy your static files into the 'nconf/static_cfg' folder.
#
$STATIC_CONFIG = array("static_cfg");

# If security permits it, you could make your active Nagios configuration editable in NConf directly.
# We discourage users from doing this though, because there is a risk that they could accidentally damage their Nagios configuration.
#$STATIC_CONFIG = array("static_cfg", "/etc/nagios");

#
# Syntax checking for static config folders
# Static config will be treated as "global" config. Syntax checking will be run for each Collector / Monitor server.
# In a distributed monitoring setup, you might have to disable syntax checking, if you are getting errors that items don't exist on certain servers.
#
define('CHECK_STATIC_SYNTAX', 1);

Source code

ln -s /etc/icinga/resource.cfg /usr/local/nconf/static_cfg
setfacl -m user:apache:rw /etc/icinga/resource.cfg 
sed s/"'CHECK_STATIC_SYNTAX', 1"/"'CHECK_STATIC_SYNTAX', 0"/ -i /usr/local/nconf/config/nconf.php

Source code

# cat /etc/icinga/resource.cfg
###########################################################################
#
# RESOURCE.CFG - Sample Resource File for Icinga
#
# You can define $USERx$ macros in this file, which can in turn be used
# in command definitions in your host config file(s).  $USERx$ macros are
# useful for storing sensitive information such as usernames, passwords,
# etc.  They are also handy for specifying the path to plugins and
# event handlers - if you decide to move the plugins or event handlers to
# a different directory in the future, you can just update one or two
# $USERx$ macros, instead of modifying a lot of command definitions.
#
# The CGIs will not attempt to read the contents of resource files, so
# you can set restrictive permissions (600 or 660) on them.
#
# Icinga supports up to 32 $USERx$ macros ($USER1$ through $USER32$)
#
# Resource files may also be used to store configuration directives for
# external data sources like MySQL...
#
###########################################################################

# Sets $USER1$ to be the path to the plugins
$USER1$=/usr/local/nagios/libexec/

# Sets $USER2$ to be the path to event handlers
#$USER2$=/usr/local/nagios/libexec//eventhandlers

# Store some usernames and passwords (hidden from the CGIs)
#$USER3$=someuser
#$USER4$=somepassword

Source code

# grep -r cfg_ . | grep -v "\#cfg_"
./icinga.cfg:# extension) in a particular directory by using the cfg_dir
./icinga.cfg:cfg_dir=/etc/icinga/modules
./icinga.cfg:# object configuration files (see the cfg_file and cfg_dir options above).
./icinga.cfg:cfg_dir=/etc/icinga/nconf
# find /etc/icinga/modules -type s #returns nothing
# find /etc/icinga/nconf -type s #returns nothing