Monitoring Engine fails to start after a configuration was n
Posted: Fri Nov 05, 2021 9:05 am
Hello,
Monitoring Engine fails to start after a configuration was not applied. I have Nagios XI 5.8.6 .
Yesterday, I created a copy of an existing service, was planning to change it to add a new service. Then decided not to based on some missing pieces that I needed to figure out. So I deleted the new service that I was creating. This made all the services under that host show as "not applied" within CCM. I have done this in the past, so I left it the way it was and did not apply the configuration cause nothing changed or needed to be updated.
Around midnight, the Nagios XI backup runs, and during that time, Nagios XI restarts itself, last night, it errored and the "Monitoring Engine" showed red. Within the logs, it showed information about that host services and that something was incorrect. I applied the configuration and it restarted the "monitoring engine" successfully.
Is this a bug in the newer versions?
Also, is there a check/monitor I can put to verify if the "Monitoring engine" is not running and send out notification. I am guessing it would have be a cron job on the server to do this.
Thank you,
Monitoring Engine fails to start after a configuration was not applied. I have Nagios XI 5.8.6 .
Yesterday, I created a copy of an existing service, was planning to change it to add a new service. Then decided not to based on some missing pieces that I needed to figure out. So I deleted the new service that I was creating. This made all the services under that host show as "not applied" within CCM. I have done this in the past, so I left it the way it was and did not apply the configuration cause nothing changed or needed to be updated.
Around midnight, the Nagios XI backup runs, and during that time, Nagios XI restarts itself, last night, it errored and the "Monitoring Engine" showed red. Within the logs, it showed information about that host services and that something was incorrect. I applied the configuration and it restarted the "monitoring engine" successfully.
Is this a bug in the newer versions?
Also, is there a check/monitor I can put to verify if the "Monitoring engine" is not running and send out notification. I am guessing it would have be a cron job on the server to do this.
Thank you,