Upgrade from 2024R1.1.5 to 2024R1.3.4 failed

[steph007]

Hi,

Recently I have upgraded from NDO2 to NDO3 my Nagios XI. You can find the detail under that forum thread:
viewtopic.php?t=76115
But after updating my production Nagios XI from 2024R1.1.5 to 2024R1.3.4 it NEVER WORKED! See the detail below.


Test system:
I did that because I first encounter a problem while update to Nagios XI version 2024R1.3.2 for my test system who was at 2024R1.1.5. You can find the detail under that forum thread:
viewtopic.php?t=76010
The problem was the version of NDO2DB that was not supporting the most recent version of Nagios XI. So, for my test system I have updated to NDO2DB 2.1.4. After seeing it was working, I decide to upgrade to NDO3 (it was recommended into the forum thread because NDO2 is not more actively maintains). I did not have any problem updating to NDO3 on my test system. So, on my test system, I don't use anymore NDO2 (systemctl disable ndo2db).

PROD:
On my prod system, I did not upgrade to NDO2DB 2.1.4 because I have upgraded directly to NDO3. So, from 2024R1.1.5, I have upgraded to NDO3 while staying at 2024R1.1.5. All went well. I leave it like this for 1 week to make sure all was staying good.
Today I have tried to update that prod to 2024R1.3.4 but it DID NOT WORK. The upgrade was seemed to be good (Nagios XI Upgrade Complete!), but the monitoring engine never started and in the nagios.log, it finished with this:
[Tue Feb 25 11:17:40 2025] Caught SIGSEGV, shutting down...
[Tue Feb 25 11:17:40 2025] Caught SIGTERM, shutting down...
When I tried to start manually (service nagios start), was still finished like this:
[Tue Feb 25 11:17:40 2025] Caught SIGSEGV, shutting down...
[Tue Feb 25 11:17:40 2025] Caught SIGTERM, shutting down...

[Ariel19]

It could be an NDO3 error or a conflict after upgrading. Try the following steps:

1. Check logs: See error details in /var/log/nagios/nagios.log and journalctl -xe.Retro Bowl
2. Check DB connection: Use mysql -u <ndo_user> -p -h <ndo_host> to check the connection.
3. View core dump: Run coredumpctl list to find SIGSEGV error.
4. Reinstall NDO3: Use yum reinstall nagiosxi-ndo3.
5. Revert to the previous version: If the error persists, rollback to 2024R1.1.5 and try again.

[steph007]

I have try again, but this time to go on version xi-2024R1.2.2 for trying with the next step after my actual 2024R1.1.5 version.
Nothing better!
I have check what you have suggest to check, but don't saw evidence of problem other than this in nagios.log:
[Tue Mar 11 14:42:46 2025] NDO-3: Ended contact_status thread
[Tue Mar 11 14:42:46 2025] Caught SIGSEGV, shutting down...
[Tue Mar 11 14:42:46 2025] Caught SIGTERM, shutting down...

[steph007]

By looking at the log, I have found this. could it be related to the upgrade problem?
Upgrading NDO...
UPGRADE: NDO is being upgraded...
mysql: [Warning] Using a password on the command line interface can be insecure.
UPGRADE: NDO manually downgraded -- skipping

[steph007]

Hi,

Probably because before I was using NDO2 before recently changing to NDO3, the NDO3 was not upgrade automatically while updating from 2024R1.1.5 to 2024R1.3.4. So, I did the update and then manually update NDO3 to version 3.1.1.

You can close this thread.

Note
On RedHat 8, there is no /usr/bin/python, only /usr/bin/python3. So, because I'm using python to monitor Windows servers, I had to created an sim link to /usr/bin/python.