Nagios Support Forum

Hi,

After upgrade Nagios from 2024R1.1.5 to 2024R1.3.2, Nagios does do the starting but hit "Caught SIGSEGV, shutting down..." just after "Event broker module '/usr/local/nagios/bin/ndomod.o' initialized successfully"

Note
I'm still using NDO2 for some reasons.

This is the complete message:
[Tue Jan 7 15:57:09 2025] Nagios 4.5.3 starting... (PID=28690)
[Tue Jan 7 15:57:09 2025] Local time is Tue Jan 07 15:57:09 EST 2025
[Tue Jan 7 15:57:09 2025] LOG VERSION: 2.0
[Tue Jan 7 15:57:09 2025] qh: Socket '/usr/local/nagios/var/rw/nagios.qh' successfully initialized
[Tue Jan 7 15:57:09 2025] qh: core query handler registered
[Tue Jan 7 15:57:09 2025] qh: echo service query handler registered
[Tue Jan 7 15:57:09 2025] qh: help for the query handler registered
[Tue Jan 7 15:57:09 2025] wproc: Successfully registered manager as @wproc with query handler
[Tue Jan 7 15:57:09 2025] wproc: Registry request: name=Core Worker 28691;pid=28691
[Tue Jan 7 15:57:09 2025] wproc: Registry request: name=Core Worker 28692;pid=28692
[Tue Jan 7 15:57:09 2025] wproc: Registry request: name=Core Worker 28693;pid=28693
[Tue Jan 7 15:57:09 2025] wproc: Registry request: name=Core Worker 28694;pid=28694
[Tue Jan 7 15:57:09 2025] wproc: Registry request: name=Core Worker 28695;pid=28695
[Tue Jan 7 15:57:09 2025] wproc: Registry request: name=Core Worker 28696;pid=28696
[Tue Jan 7 15:57:09 2025] ndomod: NDOMOD 2.1.3 (2017-04-13) Copyright (c) 2009 Nagios Core Development Team and Community Contributors
[Tue Jan 7 15:57:09 2025] ndomod: Successfully connected to data sink. 0 queued items to flush.
[Tue Jan 7 15:57:09 2025] ndomod registered for process data
[Tue Jan 7 15:57:09 2025] ndomod registered for log data'
[Tue Jan 7 15:57:09 2025] ndomod registered for system command data'
[Tue Jan 7 15:57:09 2025] ndomod registered for event handler data'
[Tue Jan 7 15:57:09 2025] ndomod registered for notification data'
[Tue Jan 7 15:57:09 2025] ndomod registered for comment data'
[Tue Jan 7 15:57:09 2025] ndomod registered for downtime data'
[Tue Jan 7 15:57:09 2025] ndomod registered for flapping data'
[Tue Jan 7 15:57:09 2025] ndomod registered for program status data'
[Tue Jan 7 15:57:09 2025] ndomod registered for host status data'
[Tue Jan 7 15:57:09 2025] ndomod registered for service status data'
[Tue Jan 7 15:57:09 2025] ndomod registered for adaptive program data'
[Tue Jan 7 15:57:09 2025] ndomod registered for adaptive host data'
[Tue Jan 7 15:57:09 2025] ndomod registered for adaptive service data'
[Tue Jan 7 15:57:09 2025] ndomod registered for external command data'
[Tue Jan 7 15:57:09 2025] ndomod registered for aggregated status data'
[Tue Jan 7 15:57:09 2025] ndomod registered for retention data'
[Tue Jan 7 15:57:09 2025] ndomod registered for contact data'
[Tue Jan 7 15:57:09 2025] ndomod registered for contact notification data'
[Tue Jan 7 15:57:09 2025] ndomod registered for acknowledgement data'
[Tue Jan 7 15:57:09 2025] ndomod registered for state change data'
[Tue Jan 7 15:57:09 2025] ndomod registered for contact status data'
[Tue Jan 7 15:57:09 2025] ndomod registered for adaptive contact data'
[Tue Jan 7 15:57:09 2025] Event broker module '/usr/local/nagios/bin/ndomod.o' initialized successfully.
[Tue Jan 7 15:57:09 2025] Caught SIGSEGV, shutting down...

Do you have a idea of where I should check to fix this?

Hi @steph007,

Do you know the original version of XI that was installed? I am also curious why you still have NDO2.

You can use these instructions to upgrade to NDO 3.

Please let us know if this resolves your issue.

The orignal version is few years ago! I cannot remember.

We use NDO2 because support asked to use. After NDO3 was released, I had a lot of problem that was required to return to NDO2.

Hi @steph007,

In that case, this is probably not a simple fix, so I would suggest opening a support ticket.

UPDATE: Support does now recommend upgrading to NDO3, because the original issues have been resolved. Otherwise, you can try the NDO 2 upgrade instructions @danderson posted.

You will have to upgrade your ndoutils version, I believe you will have 2.1.3, which is incompatible with nagios core versions 4.5.0 and above, so you will need to install ndoutils version 2.1.4. This is available on the github website. There are some XI specific patches required, here's an example of how to upgrade to the new version. Although I would like to clarify, we strongly recommend you go through the process of upgrading to NDO 3 to ensure that your system is as up to date as it can be. NDO 2 is no longer actively maintained and will experience issues that are not present in NDO 3.

Be sure to make backups / snapshots and let me know if these instructions work for you

Thank you for the information.

For my information, with Nagios XI 2024R1.1.5, with version of Nagios Core it was? Because it was working at Nagios XI 2024R1.1.5.

I will check for your solution if it's work on my test system. For NDO3, on my test system, I know it's working because it was once NDO3 has bee launched. The problem was with my 1000+ Hosts, my real monitoring server. If now you said it should be good, I would prefer to go on NDO3 of course and not rely on NDO2.

On my actual monitoring system version Nagios XI 2024R1.1.5 the Nagios Core version is 4.4.13
On my updated system Nagios XI 2024R1.3.2 the Nagios Core version is 4.5.3

So, first, I will try to update NDO to see if it's work.

Update NDO is now finished with this exit. Normal the error about the DB?
mysql: [Warning] Using a password on the command line interface can be insecure.
Current database version: 3.0.7
Unknown current version: 3.0.7. Unable to upgrade at ./upgradedb line 93.
UPGRADE: POST-UPGRADE: NDOUtils post upgraded OK.
UPGRADE: NDOUtils upgraded OK.

The version ion NDO is now:
NDO2DB 2.1.4
Copyright (c) 2009 Nagios Core Development Team and Community Contributors
Copyright (c) 2005-2008 Ethan Galstad
Last Modified: 2024-08-01
License: GPL v

The Monitoring Engine is now OK

Thank you! I will now see if I want to try with NDO3.

Hi @steph007,

The error is just mysql complaining and it is just a warning, so you can ignore it.

I'm glad things are looking up. Please let us know how the NDO upgrade goes.

I have finally upgrade to NDO3, all went good with the information given in another thread of this forum.

Thank you, you can lock this thread.