Open christrotter opened 9 years ago
Yeah, OMD's preference is to put user overrides into the nagios.cfg:
# Please do not change settings here. Copy the variables
# you want to override to ../nagios.cfg and edit them there.
# Settings in nagios.cfg have always precedence.
So dere ya go!
Hi there Chris, sorry for the late reply.
Thank you for doing all the troubleshooting for me. :) I think the right way to go would be to try and detect omd and ignore if we can't find the log_file key in the nagios config. I should be able to add this over the weekend.
Hey,
In Debian 8.0 nagios is installed under /etc/nagios3/ added it manually but it would be great if you could include that too.
Hi, may I ask how we can workaround this issue? My OMD server does not have internet access. Now, i am getting the same issue when installing graphios by issuing "python setup.py install".
Any update is highly appreciated.
I get this:
So I edited setup.py: (see omd path)
Ran it again: python setup.py install
So it's something in here:
Checking that nagios.cfg file - it's OMD-generated:
So it's expecting to see something...but OMD uses conf.d and nagios.d for configs. I suspect you could just put stuff straight in here... (the OMD documentation appears a little pieced-together - initially mentions OMD 1.2x, later on mentions OMD 5.6...)
Guessing this function is actually what's failing...
I'll play around, see if I can get it working - will update.
Update: Oh yeah, here's the folder structure if you were curious: