Nagios Support Forum

Hello

server redhat 9, upgraded nagiosxi from 2024R1.1.2 to 2024R1.3.4. Upgrade itself was succesful, no problems recorded. But after the upgrade nagios.service will not start.
systemctl status nagios.service
× nagios.service - Nagios Core 4.5.3
Loaded: loaded (/usr/lib/systemd/system/nagios.service; enabled; preset: disabled)
Active: failed (Result: exit-code) since Wed 2025-02-26 13:20:25 EET; 3s ago
Duration: 45ms
Docs: https://www.nagios.org/documentation
Process: 2686 ExecStartPre=/usr/local/nagios/bin/nagios -v /usr/local/nagios/etc/nagios.cfg (code=exited, status=0/SUCCESS)
Process: 2687 ExecStart=/usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg (code=exited, status=0/SUCCESS)
Process: 2695 ExecStopPost=/bin/rm -f /usr/local/nagios/var/rw/nagios.cmd (code=exited, status=0/SUCCESS)
Main PID: 2688 (code=exited, status=254)
CPU: 24ms

Feb 26 13:20:23 nagiosxiserver nagios[2688]: ndomod registered for contact data'
Feb 26 13:20:23 nagiosxiserver nagios[2688]: ndomod registered for contact notification data'
Feb 26 13:20:23 nagiosxiserver nagios[2688]: ndomod registered for acknowledgement data'
Feb 26 13:20:23 nagiosxiserver nagios[2688]: ndomod registered for state change data'
Feb 26 13:20:23 nagiosxiserver nagios[2688]: ndomod registered for contact status data'
Feb 26 13:20:23 nagiosxiserver nagios[2688]: ndomod registered for adaptive contact data'
Feb 26 13:20:23 nagiosxiserver nagios[2688]: Event broker module '/usr/local/nagios/bin/ndomod.o' initialized successfully.
Feb 26 13:20:23 nagiosxiserver nagios[2688]: Caught SIGSEGV, shutting down...
Feb 26 13:20:23 nagiosxiserver systemd[1]: nagios.service: Main process exited, code=exited, status=254/n/a
Feb 26 13:20:25 nagiosxiserver systemd[1]: nagios.service: Failed with result 'exit-code'.

nagios.log, messages or any other log does not report any errors. So what could i check? mysql is running, ndo2db is running, the server is secondary nagios holding like 7 hosts, so it has no load or memory usage and it has tons of free memory available.

Ok, so forum had similar issues posted, i followed these. I had ndo2 in use, upgraded to ndo3 and after that did the nagiosxi version upgrade again. The result is kind of a mix of success and fail. First off. the ndo3 install is success, thou in the end there is a warning that could not connect via root in localhost.
In /usr/local/nagios/etc/nagios.cfg new ndo is used now, nagios starts. Now there is an error that says:
NDO-3: Unable to connect to mysql. Configuration may be incorrect or database may have temporarily disconnected.
I check the config, indeed /usr/local/nagios/etc/ndo.cfg ndoutils password is blank, i change that, restart services. Now in logs:

1740578760] NDO-3: ndo_return = 1 (Table 'nagios.nagios_timeperiod_exceptions' doesn't exist)
[1740578760] NDO-3: ndo_write_timeperiod_exceptions(ndo-startup.c:771): Unable to prepare statement
[1740578760] NDO-3: ndo_return = 1 (Table 'nagios.nagios_timeperiod_exclusions' doesn't exist)
[1740578760] NDO-3: ndo_write_timeperiod_exclusions(ndo-startup.c:683): Unable to prepare statement
[1740578760] NDO-3: ndo_return = 1 (Unknown column 'retain_status_information' in 'field list')
[1740578760] NDO-3: ndo_write_contacts(ndo-startup.c:972): Unable to prepare statement
[1740578760] NDO-3: ndo_write_contacts() failed. Disabling NDO.
[1740578760] NDO-3: NDO startup thread failed at ndo_write_object_config() - disabling NDO.
[1740578760] NDO-3: Ended contact_status thread

In nagios webui all the services are green, but if i ran any checks, then the last check time is not updating nor the data is changing of the check result. So what is the best course of update path? For now, i did rollback.

Nagios may be crashing due to ndomod.o, try disabling this module in nagios.cfg,Monkey Mart check NDOUtils, or reinstall NDOUtils to fix it.

Thats not it. As i mentioned, i upgraded to ndo3 and in nagios cfg i have ndo3 module enabled instead of ndo2. Im guessing that the ndo upgrade didnt create some tables/databases to mysql needed for ndo3 and that is why the proccess dies. Any ideas what to try?

server redhat 9, upgraded nagiosxi from 2024R1.1.2 to 2024R1.4.1
Ok, so what i tried more
1) Stop nagios
2) download nagios 2024R1.1.2, extract it.
3) Went to ndo folder, extract it.
4) mysql -u root -ppassword nagios </tmp/nagiosxi/subcomponents/ndo/ndo-3.1.0/db/upgrade-from-3.0.6.sql
mysql -u root -ppassword nagios </tmp/nagiosxi/subcomponents/ndo/ndo-3.1.0/db/upgrade-from-3.0.7.sql
mysqlcheck -f -r -u root -ppassword --databases nagios
5) Enable ndo 3, restart nagios

At this point nagios 2024R1.1.2 was working nice with ndo3. Then started nagios upgrade from command line. The update was success, no errors were recorded.
But after the upgrade nagios process would not start, only log that is given is:
[1741599488] Caught SIGSEGV, shutting down...
[1741599488] Caught SIGTERM, shutting down...

All the logs are error free.
systemctl status nagios
× nagios.service - Nagios Core 4.5.3
Loaded: loaded (/usr/lib/systemd/system/nagios.service; enabled; preset: disabled)
Active: failed (Result: exit-code) since Mon 2025-03-10 11:41:40 EET; 29s ago
Duration: 673ms
Docs: https://www.nagios.org/documentation
Process: 3734 ExecStartPre=/usr/local/nagios/bin/nagios -v /usr/local/nagios/etc/nagios.cfg (code=exited, status=0/SUCCESS)
Process: 3735 ExecStart=/usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg (code=exited, status=0/SUCCESS)
Process: 3762 ExecStopPost=/bin/rm -f /usr/local/nagios/var/rw/nagios.cmd (code=exited, status=0/SUCCESS)
Main PID: 3736 (code=exited, status=254)
CPU: 85ms

Mar 10 11:41:40 nagiosxiserver nagios[3736]: wproc: Registry request: name=Core Worker 3739;pid=3739
Mar 10 11:41:40 nagiosxiserver nagios[3736]: wproc: Registry request: name=Core Worker 3737;pid=3737
Mar 10 11:41:40 nagiosxiserver nagios[3736]: wproc: Registry request: name=Core Worker 3740;pid=3740
Mar 10 11:41:40 nagiosxiserver nagios[3736]: Event broker module '/usr/local/nagios/bin/ndo.so' initialized successfully.
Mar 10 11:41:40 nagiosxiserver nagios[3736]: Warning: Host 'testserver' has no default contacts or contactgroups defined!
Mar 10 11:41:40 nagiosxiserver nagios[3736]: Successfully launched command file worker with pid 3742
Mar 10 11:41:40 nagiosxiserver nagios[3736]: Caught SIGSEGV, shutting down...
Mar 10 11:41:40 nagiosxiserver systemd[1]: nagios.service: Main process exited, code=exited, status=254/n/a
Mar 10 11:41:40 nagiosxiserver nagios[3742]: Caught SIGTERM, shutting down...
Mar 10 11:41:40 nagiosxiserver systemd[1]: nagios.service: Failed with result 'exit-code'.

And now im totally out of ideas

Hi @elinagios,

I would put in a support ticket on this one. The support techs can dig in with you in a way we can't on the Forum.

Aaron