Nagios Support Forum

We currently have a dev and two production systems running Nagios XI 2024R1.1.5. These are on RedHat 8.10 and MySQL 8.0.36 until today when I upgraded the dev box to RHEL 9.5. We have a push from our business to move off MySQL 8.0.36 so I attempted an upgrade from the RedHat provided MySQL 8.0 to MySQL Community 8.4.4 obtained directly from Oracle.

The upgrade ran fine, generated a new ndo.so and deployed it, and everything starts. The only config change was to enable the mysql_native_password in the my.cnf.

I can see the flood of monitoring tasks running but nothing ever updates. All still have a last checked timestamp prior to the MySQL 8.4.4 upgrade. Under the Admin portion of the console all system component status show as green. However, clicking on Monitoring Engine Status, under there the monitoring engine shows as red. Clicking the button to start it issues the systemctl nagios start in the background but the process is already running so ultimately nothing happens.

I ran the reconfigure_nagios and repair_database scripts but neither helped. One interesting note is when I run the repair_database it goes through and 'fixes' a bunch of inodes. But if I run the script again immediately, it does the same thing and appears to be fixing a bunch of items again.

Has anyone encountered this before? Are there any reasons MySQL 8.4.4 would be incompatible with our version of Nagios XI?

Hi @rich.anderson,

Thanks for reaching out.

Did you stop the Nagios processes and MySQL before running the upgrade?

Are there any errors in the MySQL or XI log files?

Laura,

Thanks for replying. I decided to try it again today and finally got it working. Just for anyone searching in the future this is what I encountered:

When reinstalling NDO so that it builds with the updated mysql libraries...don't use 'install'. It seems to wipe out the pre-existing config and doesn't back it up. And in my case it ended up having incorrect password settings in the config.

Next issue was when running the ndo upgrade process. This kept all my username/passwords right for the database but then changed the path to the mysql.sock file for some reason. I set it back to the correct path and after that everything worked fine.

So basically it was just NDO issues.

Thanks!
Rich

Hi @rich.anderson,

Thanks for the update. I'm going to lock this thread and mark it resolved.