Immediate Check Failure

[DarenBrim23]

On the Host Status Detail page, when I click the "Force an immediate check" link, I get a popup that states:

"Please Wait"
"Your request was not processed in a timely manner. It may still execute, as the server may be temporarily busy"

I am not sure what is causing this, as the server load/memory usage and such are very low.

[npolovenko]

Hello, @DarenBrim23.
Does that happen when you force check any service or just one particular? Please run the following commands:

Code: Select all

service nagios stop
service http stop
killall -9 nagios
service nagios start
service http start

If the above doesn't help please force the check one more time and send us your system profile.
To send us your system profile. Login to the Nagios XI GUI using a web browser.
Click the "Admin" > "System Profile" Menu
Click the "Download Profile" button
Save the profile.zip file and attach it to your next post, or you may upload the profile to a cloud storage of your choice and share the link with me in a PM.

[DarenBrim23]

Hi,

That did not help, as I am still having the same issues. Also, after following the steps provided... the Windows machines that I was monitoring are no longer being monitored. Is that a result of running the killall command?

Is there another way to getting you system profile information for trying to diagnose the problem? This install is in a secure offline environment, in which getting logs out of is near impossible there is anything specific that you are looking for, I can hand type it in for you.

Just to give a little more information, this is a manual offline install of Nagios XI 5.4.8 on RHEL 6.9 (64-bit).

Thanks

[dwhitfield]

What's the output of sestatus? Also, can you send your /etc/sudoers? If someone has modified the default XI entries for the sudoers, that is likely the source of your issue.

Is there any other sort of hardening that might be in place?

Are you a customer? Would your org be more comfortable sending us a profile through a ticket rather than on the forum? If you're not a customer, what about sending it to one of our sales techs?

[DarenBrim23]

SELinux is disabled on our servers.

I did the manual install of Nagios, and have not modified the sudoers file at all. I read in another thread what the sudoers file should be set to, and how to troubleshoot it logging in as the nagios user and executing the reconfigure script. Everything matched up perfectly and ran fine.

We are not a customer, just simply evaluating product.

We do have quite a bit of hardening in place. I need to comb through our hardening procedure/script to see everything that it is doing. Would you happen to have any idea what configs from a hardening perspective might have been affected to cause the issues that I am seeing with Nagios?

It is possible that we could send it to one of your sales tech. I would just need to have the information scrubbed and approved to be sent out. Assuming that it isn't a tedious process to get the profile from an offline environment, which it might be.

Thanks

[dwhitfield]

It is possible that we could send it to one of your sales tech. I would just need to have the information scrubbed and approved to be sent out. Assuming that it isn't a tedious process to get the profile from an offline environment, which it might be.

Do you have ssh access to the server? If so, then it shouldn't be too difficult.

If you haven't already, since you are evaluating, I would suggest putting your name in for a quickstart: https://www.nagios.com/services/quickstart/

cgroups and a noexec flag at the partition level would be the two next most obvious things to check, aside from the actual file permissions.

Also, the umask of the nagios user is an important aspect. Generally, 0002 and 0022 should work for the nagios user.

There are many fewer moving pieces in Nagios Core, which should make it easier to harden. You might want to look into a Core support contract: https://www.nagios.com/services/nagios- ... ort-plans/