CCM unable to apply configuration
Posted: Thu Apr 25, 2019 3:19 am
Hi,
I have an odd problem applying configuration in NagiosXI CCM. We are currently running 5.5.11.
When I click 'Apply Configuration' we get the following two error messages:
To aid debugging, I went through and renamed every service with the name _multiple_host to something more meaningful for each. This is now fine if I got to Config File Management, Delete, Write, Verify and Restart. However Apply Configuration still fails. I also tried disabling all services except a single localhost ping check. Still we get the same message.
To me, it looks as if we have some old configuration state stuck somewhere. I did also try a reboot, which did not work.
Does anyone know a way to either clear this or steps to see how we can stop config files reverting so we can step in and find out what is causing this error?
I have an odd problem applying configuration in NagiosXI CCM. We are currently running 5.5.11.
When I click 'Apply Configuration' we get the following two error messages:
The _multiple_hosts.cfg dates back from one Nagios updates we did a few years ago, where a lot of service checks ended up with that config name. For this particular error, we could not see any issue with line 1096, but it appears that what ever file generated this error reverted back to the original when it failed, as per the first message.An error occurred while attempting to apply your configuration to Nagios Core. Monitoring engine configuration files have been rolled back to their last known good checkpoint.
Error: Service has no hosts and/or service_description (config file '/usr/local/nagios/etc/services/_multiple_hosts.cfg', starting on line 1096)
To aid debugging, I went through and renamed every service with the name _multiple_host to something more meaningful for each. This is now fine if I got to Config File Management, Delete, Write, Verify and Restart. However Apply Configuration still fails. I also tried disabling all services except a single localhost ping check. Still we get the same message.
To me, it looks as if we have some old configuration state stuck somewhere. I did also try a reboot, which did not work.
Does anyone know a way to either clear this or steps to see how we can stop config files reverting so we can step in and find out what is causing this error?