Check HTTP Path
I am attempting to set our Check HTTP Path to /ping or /ping/. It appears that when you change it and hit save that it doesn't indicate an error but also never saves either.
Is there a reason why this doesn't work? We made the assumption that the configuration change had been accepted but when we go back to check it hasn't been updated at all. Consequently a change on / has left our server inaccessible for nearly 6 hours.
Can you tell us how to change this setting and for the setting to hold?
Many thanks
RobL
1 Reply
You can run the command with a -v for verbose mode, which should supply you with additional output to tell you where the failure is occurring. It sounds like you're using the GUI version of Nagios (NagiosXI), and there is an article from Nagios here describing different causes and solutions for this behavior. Otherwise, if you're using the command line and experiencing these issues, I have some suggestions below that may be helpful along with additional resources.
If the configuration file is not saving:
- Ensure your text editor (nano, vim, etc) is working properly and saving the file
- Check and make sure there are no other applications or services overwriting the file
If check_http is not operating properly when /ping is set:
- Verify your configurations - this StackOverflow post might be helpful when checking your parameters
- Make sure Nagios has the correct file path to your web server
We also have a guide available here for installing Nagios and its associated plug-ins that may help. The Nagios documentation site may help too, as well as this comprehensive Linux Academy blog post which describes each line in the configuration files for Nagios.