Nagios Support Forum

Our previous build was configured exactly the same on this system ./configure --with-nagios-user=nagios --with-nagios-group=nagios Our configuration is really very simple, out-of-the-box install from the source code. So, I suspect something has changed -- and this may need to be logged as a bug or s...

I did a chgrp "apache" to the nagios.cmd file and it's working -- this makes some sense, as that is the effective group of the apache server. But, with our older Nagios installation (3.x) under CentOS 5.x, this is not necessary. So, what changed in the code (I wonder) if anything that this...

Logging in with a regular account, with LDAP/SSSD disabled, had no effect. When I went to reschedule a check, it gave the same error.

That is, I disabled LDAP/SSSD and added a local user (me) along with a local "nagios" user and "nagios" group.

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.

This is what the lot was compiled with:

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.

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. Thanks! # ll -d /usr/local/nagi...

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 perform...

Oops, I think you are right. We have a few systems that are pre-installed here and I didn't happen to take note of that prior to posting. I don't see any way to accomplish what I need with the current framework. I would have to write a separate check for each /mount/point -- and that's not going to ...

I've been hacking around with some scripting in an effort to solve an irritating problem with the stock check_nfs_mounts.sh script (or that procedure). The problem being when you pass an array of mount points to check, if one of them fails, the entire alert is in error and you don't really know whic...