Nagios Core SEGV on AL2022

Support forum for Nagios Core, Nagios Plugins, NCPA, NRPE, NSCA, NDOUtils and more. Engage with the community of users including those using the open source solutions.
Post Reply
jmcpheters
Posts: 3
Joined: Wed Aug 24, 2022 2:13 pm

Nagios Core SEGV on AL2022

Post by jmcpheters »

I'm trying to test Nagios core on the Release Candidate for AWS Linux 2022, which is based on Centos 7. I followed the instructions at:

https://assets.nagios.com/downloads/nag ... entos7.pdf

SELinux has been disabled, and the expected users and groups exist:

[root@ip-10-16-3-149 nagios-plugins-2.3.3]# getenforce
Disabled
[root@ip-10-16-3-149 nagios-4.4.7]# make install-groups-users
Group nagios already exists
User nagios already exists

However, the nagios service will not start, but gets SEGV. See status output below.

[root@ip-10-16-3-149 nagios-4.4.7]# systemctl status nagios
× nagios.service - Nagios Core 4.4.7
Loaded: loaded (/usr/lib/systemd/system/nagios.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Wed 2022-08-24 19:06:38 UTC; 2min 57s ago
Docs: https://www.nagios.org/documentation
Process: 27639 ExecStartPre=/usr/local/nagios/bin/nagios -v /usr/local/nagios/etc/nagios.cfg (code=exited, status=0/SUCCESS)
Process: 27640 ExecStart=/usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg (code=exited, status=0/SUCCESS)
Process: 27646 ExecStopPost=/usr/bin/rm -f /usr/local/nagios/var/rw/nagios.cmd (code=exited, status=0/SUCCESS)
Main PID: 27641 (code=exited, status=254)
CPU: 129ms

Aug 24 19:06:35 ip-10-16-3-149.us-west-2.compute.internal nagios[27641]: qh: echo service query handler registered
Aug 24 19:06:35 ip-10-16-3-149.us-west-2.compute.internal nagios[27641]: qh: help for the query handler registered
Aug 24 19:06:35 ip-10-16-3-149.us-west-2.compute.internal nagios[27641]: wproc: Successfully registered manager as @wproc with query handler
Aug 24 19:06:35 ip-10-16-3-149.us-west-2.compute.internal nagios[27641]: wproc: Registry request: name=Core Worker 27642;pid=27642
Aug 24 19:06:35 ip-10-16-3-149.us-west-2.compute.internal nagios[27641]: wproc: Registry request: name=Core Worker 27643;pid=27643
Aug 24 19:06:35 ip-10-16-3-149.us-west-2.compute.internal nagios[27641]: wproc: Registry request: name=Core Worker 27644;pid=27644
Aug 24 19:06:35 ip-10-16-3-149.us-west-2.compute.internal nagios[27641]: wproc: Registry request: name=Core Worker 27645;pid=27645
Aug 24 19:06:36 ip-10-16-3-149.us-west-2.compute.internal nagios[27641]: Caught SIGSEGV, shutting down...
Aug 24 19:06:36 ip-10-16-3-149.us-west-2.compute.internal systemd[1]: nagios.service: Main process exited, code=exited, status=254/n/a
Aug 24 19:06:38 ip-10-16-3-149.us-west-2.compute.internal systemd[1]: nagios.service: Failed with result 'exit-code'.

Please advise.
jmcpheters
Posts: 3
Joined: Wed Aug 24, 2022 2:13 pm

Re: Nagios Core SEGV on AL2022

Post by jmcpheters »

This is a known issue:

https://github.com/NagiosEnterprises/na ... issues/861

Discussed work arounds resolved the issue. A proper fix is expected in a future release.
jmcpheters
Posts: 3
Joined: Wed Aug 24, 2022 2:13 pm

Re: Nagios Core SEGV on AL2022

Post by jmcpheters »

This is a known issue:

https://github.com/NagiosEnterprises/na ... issues/861

Discussed work arounds resolved the issue. A proper fix is expected in a future release.
SohamMaoor
Posts: 7
Joined: Fri May 20, 2022 8:00 am

Re: Nagios Core SEGV on AL2022

Post by SohamMaoor »

I've also checked the permissions (my apache is running with user apache and group nagios) on /usr/lib/nagios/cgi/, /usr/share/nagios and /usr/lib64/nagios (everything is in the group nagios). I've also checked the files status.dat and objects.cache in /var/nagios/ .
Post Reply