New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Nagios 4.4.7 on AIX: #882
Comments
Hi @ewwolz, thanks for reaching out. Unfortunately, we don't have any AIX machines available in-house at the moment, so I'm not able to reproduce/debug this (and I haven't seen this issue in any other contexts). If I were you, I'd try reaching out to an AIX-specific support forum or users' group to see if anyone else has run into this. |
It's been a while, but every time we've installed Nagios Core on AIX, we've compiled it from source. If that's an option for you, I'd go that route rather than rpms. However, you definitely need to increase the ulimit for root or else you will see problems that are not unlike these. |
I increased nofiles to unlimited but that didn't help. As long as nofiles is an actual number (doesn't matter which one) I get the messages reported at the top of this thread.
|
Sorry - my last suggestion would be to compile from source. The last time my fingers used Nagios on AIX was 10 years and one week ago, to the day. :-) |
I'm trying to run the Nagios 4.4.7 downloaded from the AIX Open Source Toolbox (https://www.ibm.com/support/pages/aix-toolbox-open-source-software-downloads-alpha#N):
but I am seeing a bunch of "wproc: Registry request: name=Core Worker" statements in nagios.log followed almost immediately by an equal number of "wproc: Socket to worker Core Worker broken, removing" statements. There are also a bunch of "Unable to run scheduled host check at this time" and "failed because job was null" messages in the nagios.debug.
If starting Nagios not as a daemon but in the current command window, I also see an equal number of "Worker failed to create io broker socket set: No such file or directory" statements. The googles tell me that this problem can occur when operating system limits restrict the max number of processes that can be executed... but I'm pretty sure that's not the case here:
This is on a POWER8 LPAR with 4 virtual processors and 8 GB of RAM. AIX oslevel is 7200-05-03-2135. Any ideas?
The text was updated successfully, but these errors were encountered: