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.
I have installed nagios core 4.3.2-8.el7 from epel and done the SELinux config suggested by the startup script. Subsequently the nagios daemon started and looks ok:
Still the nagios home page shows "Unable to get process status" and "End of script output before headers" is written to the apache error log. Setting SELinux to permissive does not help and the permissions seem ok, as installed by RPM.
Any suggestions where to start looking?
Does the rest of the UI work correctly? It is possible that the RPM packagers missed something when creating the SELinux context that is required for the pid check on the landing page.
Calling the Scripts from the sidebar links results in HTTP 500, i.e. nothing in the GUI works. Calling the scripts directly from command line works fine, though.
Thanks for pointing me to the httpd config, the problem was setting SuexecUserGroup for another application on server level.
Now it will work, but only when setting SELinux to permissive. Did I miss something on installation?
Obviously, guess I will then have to either grep through the audit logs until everything works, or look for a policy package to install. Thanks for helping out anyway, much appreciated.