Nagios Support Forum

old nagios plugins version="2.3.3"
new nagios plugins version"2.4.0"

old nagios core version = "2.4.6"
new nagios core version = "2.4.7"

platform is CentOS Stream 8.

after finishing installation, web GUI warns

"Error: Could not read host and service status information!"

sudo journalctl -u nagios.service

Sep 30 10:16:27 vg-nagios-01 nagios[96184]: qh: Socket '/usr/local/nagios/var/rw/nagios.qh' successfully initialized Sep 30 10:16:27 vg-nagios-01 nagios[96184]: qh: core query handler registered Sep 30 10:16:27 vg-nagios-01 nagios[96184]: qh: echo service query handler registered Sep 30 10:16:27 vg-nagios-01 nagios[96184]: qh: help for the query handler registered Sep 30 10:16:27 vg-nagios-01 nagios[96184]: wproc: Successfully registered manager as @wproc with query handler Sep 30 10:16:27 vg-nagios-01 nagios[96184]: wproc: Registry request: name=Core Worker echatspin echatrandom 96187;pid=96187 Sep 30 10:16:27 vg-nagios-01 nagios[96184]: wproc: Registry request: name=Core Worker 96189;pid=96189 Sep 30 10:16:27 vg-nagios-01 nagios[96184]: wproc: Registry request: name=Core Worker 96186;pid=96186 Sep 30 10:16:27 vg-nagios-01 nagios[96184]: wproc: Registry request: name=Core Worker 96188;pid=96188 Sep 30 10:16:28 vg-nagios-01 nagios[96184]: Caught SIGSEGV, shutting down..

nagios

Hi Wilnar,

There was an issue in Nagios Core 4.4.7 where the update check was causing a crash on some distributions.

There are two options that should work pretty well for you:

1) Nagios Core 4.4.8 was released a couple of days ago, which shouldn't ever crash during the update check. You're welcome to try upgrading directly to that version.

2) If you'd really prefer to stay on Core 4.4.7, one known-good workaround is to disable update checks for the moment, i.e. go into nagios.cfg and set check_for_updates to 0.

Let me know if those options don't work or if you have any other concerns.
-Sebastian Wolf

Nagios Core: 4.4.7

It was running fine up to this afternoon when I updated from 4.4.6. I have tried rebooting as well with no success.

The main omegle.2yu.co web page loads, but complains it can't get the process status. When I check the status on the server:

# systemctl status nagios
● nagios.service - Nagios Core 4.4.7
Loaded: loaded (/lib/systemd/system/nagios.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Thu 2022-04-14 15:35:03 PDT; 11min ago
Docs: https://www.nagios.org/documentation
Process: 448 ExecStartPre=/usr/local/nagios/bin/nagios -v /usr/local/nagios/etc/nagios.cfg (code=exited, status=0/SUCCESS)
Process: 499 ExecStart=/usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg (code=exited, status=0/SUCCESS)
Process: 790 ExecStopPost=/usr/bin/rm -f /usr/local/nagios/var/rw/nagios.cmd (code=exited, status=0/SUCCESS)
Main PID: 503 (code=exited, status=254)
CPU: 105ms

Apr 14 15:35:01 nag nagios[503]: qh: echo service query handler registered
Apr 14 15:35:01 nag nagios[503]: qh: help for the query handler registered
Apr 14 15:35:01 nag nagios[503]: wproc: Successfully registered manager as @wproc with query handler
Apr 14 15:35:01 nag nagios[503]: wproc: Registry request: name=Core Worker 510;pid=510
Apr 14 15:35:01 nag nagios[503]: wproc: Registry request: name=Core Worker 513;pid=513
Apr 14 15:35:01 nag nagios[503]: wproc: Registry request: name=Core Worker 511;pid=511
Apr 14 15:35:01 nag nagios[503]: wproc: Registry request: name=Core Worker 512;pid=512
Apr 14 15:35:01 nag nagios[503]: Caught SIGSEGV, shutting down...
Apr 14 15:35:01 nag systemd[1]: nagios.service: Main process exited, code=exited, status=254/n/a
Apr 14 15:35:03 nag systemd[1]: nagios.service: Failed with result 'exit-code'.
The Nagios Log:

[1649975701] Nagios 4.4.7 starting... (PID=503)
[1649975701] Local time is Thu Apr 14 15:35:01 PDT 2022
[1649975701] LOG VERSION: 2.0
[1649975701] qh: Socket '/usr/local/nagios/var/rw/nagios.qh' successfully initialized
[1649975701] qh: core query handler registered
[1649975701] qh: echo service query handler registered
[1649975701] qh: help for the query handler registered
[1649975701] wproc: Successfully registered manager as @wproc with query handler
[1649975701] wproc: Registry request: name=Core Worker 510;pid=510
[1649975701] wproc: Registry request: name=Core Worker 513;pid=513
[1649975701] wproc: Registry request: name=Core Worker 511;pid=511
[1649975701] wproc: Registry request: name=Core Worker 512;pid=512
[1649975701] Caught SIGSEGV, shutting down...
Checking config...

# bin/nagios -v etc/nagios.cfg

Nagios Core 4.4.7
Copyright (c) 2009-present Nagios Core Development Team and Community Contributors
Copyright (c) 1999-2009 Ethan Galstad
Last Modified: 2022-04-14
License: GPL

Website: https://www.nagios.org
Reading configuration data...
Read main config file okay...
Read object config files okay...

Running pre-flight check on configuration data...

Checking objects...
Checked 90 services.
Checked 12 hosts.
Checked 4 host groups.
Checked 0 service groups.
Checked 1 contacts.
Checked 1 contact groups.
Checked 25 commands.
Checked 5 time periods.
Checked 0 host escalations.
Checked 0 service escalations.
Checking for circular paths...
Checked 12 hosts
Checked 0 service dependencies
Checked 0 host dependencies
Checked 5 timeperiods
Checking global event handlers...
Checking obsessive compulsive processor commands...
Checking misc settings...

Total Warnings: 0
Total Errors: 0

Things look okay - No serious omeglz echat problems were detected during the pre-flight check

swolf wrote:There was an issue in Nagios Core 4.4.7 where the update check was causing a crash on some distributions.
{...}
1) Nagios Core 4.4.8 was released a couple of days ago, which shouldn't ever crash during the update check. You're welcome to try upgrading directly to that version.

I found I was running into the same bug. Disabling the update check fixed it on 4.4.7. Reverted my VM to before 4.4.7 and tried upgrading directly to 4.4.8 and had the same issue. Disabled update checking on 4.4.8 and it fixed it there to. I don't think this bug is fixed yet.

I also had this error recently after upgrading to 4.4.7 on Ubuntu 20.04.4. I can confirm that check_for_updates=0 in nagios.cfg fixes this for me.