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.
We have a brand new nagios-4.0.4 installation that I've been testing. The first time around, I ran into this error. I'm convinced it's not a permissions problem on that directory, nor is it a group membership issue (nagios is in the apache group). I re-did the installation (kickstart VM) and performed a very vanilla install, with only "localhost" and the problem persists.
The system I have is CentOS 6.5 (up-to-date) 64-bit.
Prior to this, I compared the permissions to our working 3.x system, and they are exactly the same. This leads me to believe the error is obscured -- and I'm at a loss as to what the issue is.
Error: Could not open command file '/usr/local/nagios/var/rw/nagios.cmd' for update!
The permissions on the external command file and/or directory may be incorrect. Read the FAQs on how to setup proper permissions.
An error occurred while attempting to commit your command for processing.
Return from whence you came
Nagios-Plugins maintainer exclusively, unless you have other C language bugs with open-source nagios projects, then I am happy to help! Please pm or use other communication to alert me to issues as I no longer track the forum.
We are also using LDAP for UID/GID, and I wonder if this plays a part in the issue (SSSD). Here is the output (below). I did experiment by adding these to /etc/passwd and /etc/group, as our nsswitch.conf has "files" as a first lookup, but that had no affect.
Yes that is definitely a possibility. Are you able to su to the nagios user and open\read the nagios.cmd file? Otherwise I would agree all of those permissions look just fine.
Nagios-Plugins maintainer exclusively, unless you have other C language bugs with open-source nagios projects, then I am happy to help! Please pm or use other communication to alert me to issues as I no longer track the forum.
I am able to su to nagios and access the nagios.cmd file without any problems.
Again, this is on a brand new installation (from source). SELinux is not a factor, there are no ACLs on that directory structure. I am able to repeat this error each time, without changing anything.
Nagios itself isn't using LDAP, and other parts of Nagios appear to be working fine. I will look into reconfiguring the VM to use standard logins and see if that makes a difference.