Monitoring Engine fails to start after a configuration was n

This support forum board is for support questions relating to Nagios XI, our flagship commercial network monitoring solution.
Locked
vappukuttan
Posts: 52
Joined: Tue Mar 05, 2019 7:43 am

Monitoring Engine fails to start after a configuration was n

Post by vappukuttan »

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,
User avatar
pbroste
Posts: 1288
Joined: Tue Jun 01, 2021 1:27 pm

Re: Monitoring Engine fails to start after a configuration w

Post by pbroste »

Hello @vappukuttan

Thanks for reaching out, want to start out by reindexing the Core Config's

Reindex the Core Configuration Manager (CCM) configs
  • rm -rf /usr/local/nagios/etc/import/*
  • 1: Terminal command list all running /bin/nagios -> ps -aux | grep -E '/bin/nagios'
  • 2: Terminal command -> killall -9 nagios (or pkill nagios)
  • 3: Terminal command check to see if /bin/nagios processes are stopped ==> ps -aux | grep -E '/bin/nagios'
  • 4: Head over to the Nagios XI web console ==>
    Core Configuration Manager (CCM) ==>
    Config File Management ==> [Delete Files] ==> [Write Files] ==> [Verify Files]
  • 5: Core Configuration Manager (CCM) ==> Under Quick Tools ==> "Apply Configuration"
  • 6: Restart nagios.service by terminal command: systemctl restart nagios
  • [list]
  • Code: Select all

    systemctl restart nagios
[/list]

Verify that the host and services look good in pre-flight with no errors in core by:

  • Code: Select all

    /usr/local/nagios/bin/nagios -v /usr/local/nagios/etc/nagios.cfg

Please PM your updated system profile for us to review.

To send us your system profile.
  • Login to the Nagios XI GUI using a web browser.
  • Click the "Admin" > "System Profile" Menu
  • Click the "Download Profile" button
  • Save the profile.zip file and send via Private Message
Thanks,
Perry
vappukuttan
Posts: 52
Joined: Tue Mar 05, 2019 7:43 am

Re: Monitoring Engine fails to start after a configuration w

Post by vappukuttan »

Hello,

Thank you for your input, I will have to plan this out when its least impactful, let me try and get a window to do this and will update back.

Thank you,
Vinod
User avatar
pbroste
Posts: 1288
Joined: Tue Jun 01, 2021 1:27 pm

Re: Monitoring Engine fails to start after a configuration w

Post by pbroste »

Hello Vinod,

Thanks for following up and letting us know that you will be working on this in a later endeavor.

Please let us know if you have any further questions when you start working on this again,
Perry
Locked