Nagios Support Forum

Hi lovely people,

I'm unable to run nagios on a server, I've tried to enable debugging to -1 in nagios.cfg but this is all it shows


Apr 28 15:10:56 spnagios systemd[1]: Starting LSB: Starts and stops the Nagios monitoring server...
Apr 28 15:10:56 spnagios nagios[3202]: Starting nagios: done.
Apr 28 15:10:56 spnagios systemd[1]: Started LSB: Starts and stops the Nagios monitoring server.
Apr 28 15:10:56 spnagios nagios[3226]: Nagios 4.4.7 starting... (PID=3226)
Apr 28 15:10:56 spnagios nagios[3226]: Local time is Thu Apr 28 15:10:56 AEST 2022
Apr 28 15:10:56 spnagios nagios[3226]: LOG VERSION: 2.0
Apr 28 15:10:56 spnagios nagios[3226]: qh: Socket '/usr/local/nagios/var/rw/nagios.qh' successfully initialized
Apr 28 15:10:56 spnagios nagios[3226]: qh: core query handler registered
Apr 28 15:10:56 spnagios nagios[3226]: qh: echo service query handler registered
Apr 28 15:10:56 spnagios nagios[3226]: qh: help for the query handler registered
Apr 28 15:10:56 spnagios nagios[3226]: wproc: Successfully registered manager as @wproc with query handler
Apr 28 15:10:56 spnagios nagios[3226]: wproc: Registry request: name=Core Worker 3228;pid=3228
Apr 28 15:10:56 spnagios nagios[3226]: wproc: Registry request: name=Core Worker 3229;pid=3229
Apr 28 15:10:56 spnagios nagios[3226]: wproc: Registry request: name=Core Worker 3232;pid=3232
Apr 28 15:10:56 spnagios nagios[3226]: wproc: Registry request: name=Core Worker 3231;pid=3231
Apr 28 15:10:56 spnagios nagios[3226]: wproc: Registry request: name=Core Worker 3233;pid=3233
Apr 28 15:10:56 spnagios nagios[3226]: wproc: Registry request: name=Core Worker 3230;pid=3230
Apr 28 15:10:57 spnagios nagios[3226]: Caught SIGSEGV, shutting down...

it does seem to work when i disable updates in nagios.cfg file

If I downgrade to the previous version it works fine.

Anyone else with the same problem?

Yes - We just tried to perform the update from 4.4.6 -> 4.4.7, after updating, the Nagios instance would start and Daemon would be SIGSEV Termed immediately after starting worker processes like yours.

We are running Ubuntu 20.04 LTS, and 4.4.6 has worked for months without issues.

We took your advice and edited the nagios.cfg and disabled check_for_updates and the service is now A-OK, other than red banner about not being warned about future updates. Well, this is the latest update since 2020 so not really concerned, but we check monthly anyways during our checks.

Pikmin wrote:Anyone else with the same problem?

Exact same problem here on Ubuntu 20.04.4 LTS.

Thanks for posting, I'm running Rocky Linux 8.5 (Green Obsidian)

When you disable updates directive in nagios config it works for you too?

Pikmin wrote:When you disable updates directive in nagios config it works for you too?

I did not test with "check_for_updates=0".

kylejb007 wrote:Yes - We just tried to perform the update from 4.4.6 -> 4.4.7, after updating, the Nagios instance would start and Daemon would be SIGSEV Termed immediately after starting worker processes like yours.

We are running Ubuntu 20.04 LTS, and 4.4.6 has worked for months without issues.

We took your advice and edited the nagios.cfg and disabled check_for_updates and the service is now A-OK, other than red banner about not being warned about future updates. Well, this is the latest update since 2020 so not really concerned, but we check monthly anyways during our checks.

Thanks for reporting this kylejb007

Hopefully will be fixed in the next version, might check github to see if anyone reported anything

EDIT: Someone beat me to it

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

Just for info - same issue using SLES15 SP3 - updated a couple of weeks ago and had to revert to 4.4.6 (before seeing workaround).

Will probably wait until fixed, keeping half an eye on - https://github-com.translate.goog/Nagio ... _tr_pto=sc

I've recompiled it with the patch and now working
https://github.com/NagiosEnterprises/na ... 96f9184197