Nagios Support Forum

We created a new volume to hold our NagiosXI backups called /backups. We made the Nagios user the Owner and used our teams group as the group:

nagios:teamx

When I went into Scheduled Backups and had it run a test on the /backups directory I got this:
Which made no since. So we changed the permissions to nagios:nagcmd and now it tested fine. Which is still odd. The only other user in the nagcmd group is the apache user.

With that in mind we tried this:

apache:teamx -- This passed the test

So it appears it is the apache user that is writing the backup and not the Nagios user, like the error specifies.

Just wanted to verify this with you guys, and if this is truly the case, then this is a request to change the wording in the error to avoid confusion for other users in the future.

I've seen this happen before, I believe the error handling could be worked on a bit, because what it was really complaining about was the apache using not having access, as the nagios group contains the apache user, that was what the issue was. In your case, giving it apache user rights, and then supplying your group worked fine, because the main component, apache, was present. Where the error expects only the defaults to be supplied.

I agree, I just think the error message should state the 'Apache user or the nagcmd group' versus the "Nagios user or Nagios group" as that last one is not accurate as the Nagios user cannot perform that.

We did it this way because we wanted to be able, along with our Linux administrators, to be able to get in there if a situation occurs and have permissions.

They can root of course, but we cannot.

Thanks for getting back with me. This thread can be closed.