Broken Services Post Update

[CameronWP]

Hi:

We recently upgraded to 5.11.1 and from Postgres to MySQL. We are now finding we can't update the configuration through CCM. For example, I tried to deactivate a host, I applied the configuration (it appears to have worked fine) and yet the host is still there. Also, there are numerous services that are showing in the UI that were valid pre-update but are now missing from CCM and reporting errors. We are also getting numerous errors in the nom.log as follows:

PHP Notice: DB is not connected in /usr/local/nagiosxi/html/includes/db.inc.php on line 399
PHP Notice: DB is not connected in /usr/local/nagiosxi/html/includes/db.inc.php on line 399
PHP Notice: DB is not connected in /usr/local/nagiosxi/html/includes/db.inc.php on line 399
PHP Notice: DB is not connected in /usr/local/nagiosxi/html/includes/db.inc.php on line 399
PHP Notice: Tried to execute an empty SQL query in /usr/local/nagiosxi/html/includes/db.inc.php on line 501

Thanks in advance for any light you can shed!

[CameronWP]

I should add:

1) Linux version is Rocky 8
2) 64-bit
3) Manual Installation
4) There are no special configurations on the system.

[CameronWP]

Hello, any input with this? Let me know if there is more I need to provide. Thanks!

[tgriep]

The PHP script is loading the reactor component that talks to an obsolete product called Nagios Reactor and that is causing the messages.
It can be moved from the XI system folders by running the following as root. It will make a backup in the /root folder.

mv /usr/local/nagiosxi/html/includes/components/reactoreventhandler /root

Also, there was another product called Nagios IM that causes the same message and to remove that if it exists on your server, run this as root.
mv /usr/local/nagiosxi/html/includes/components/nagiosim /root

Then check the log files to see if the "DB is not connected" messages are gone.

[CameronWP]

Awesome, thanks for that! Appears to have done the trick.

[jnbut]

The occurrence of the messages seems to stem from the PHP script loading the reactor component, which communicates with an outdated product called Nagios Reactor. To address this, you can execute the following command as root, which will relocate it from the XI system folders and create a backup in the /root directory:

mv /usr/local/nagiosxi/html/includes/components/reactoreventhandler /root

Moreover, a similar issue might arise from Nagios IM, another product. If it exists on your server, you can eliminate it by executing the following command as root:

mv /usr/local/nagiosxi/html/includes/components/nagiosim /root

After making these changes, assess the log files to confirm whether the "DB is not connected" messages have been resolved.