Problems running checks from web interface

[Marc Powell]

> -----Original Message-----
> From: nagios-users-admin at lists.sourceforge.net [mailto:nagios-users-
> admin at lists.sourceforge.net] On Behalf Of Pavel Santos
> Sent: Thursday, October 20, 2005 9:34 PM
> To: nagios-users at lists.sourceforge.net
> Subject: [Nagios-users] Problems running checks from web interface
> 
> Hello list,


> I'm running Nagios 2.0b4 on FC4.  Everything seems to be working ok
except
> when I try to run an external command from the web interface, it
fails.
> 
> I think I have everything configure properly since I don't see any
> problems in the logs and set all the required permissions in nagios
> /var/rw directory.   I still receive the error below:


> Error: Could not stat() command file
> '/usr/local/nagios/var/rw/nagios.cmd'!

> Any ideas as to what I missed.

Some possible reasons --

1) Does nagios.cmd exist?

2) Most likely you have SELinux enabled (use /usr/sbin/sestatus -v to
verify) and it's not allowing apache to write to the file. If you have
SELinux enabled run 'audit2allow -l -i /var/log/messages -v' and look
for references to nagios.cmd. If it's there you'll have to modify your
policy to allow permissive or add http context to
/usr/local/nagios/var/rw/*.

3) nagios.cmd is not writable by your web server due to standard
permissions. If you had to add your web server to the nagios or
nagioscmd group (whichever you used), did you remember to restart it?
Are the permissions on /usr/local/nagios /usr/local/nagios/var and
/usr/local/nagios/var/rw such that the web server can access those
directories?

--
Marc


-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null