not able toaccesshttp://localhost/nagios/cgi-bin/

[Marc Powell]

> -----Original Message-----
> From: nagios-users-bounces at lists.sourceforge.net [mailto:nagios-users-
> bounces at lists.sourceforge.net] On Behalf Of Gagandeep Singh
> Sent: Saturday, July 14, 2007 4:03 PM
> To: Nagios-users at lists.sourceforge.net
> Subject: Re: [Nagios-users] not able
toaccesshttp://localhost/nagios/cgi-
> bin/
> 
> i see all the cgi's in the /usr/local/nagios/sbin.  They are all in
green
> color.  So you are saying there should be another directory that hold
the
> cgi's?

No, I'm not saying that at all. They should all be in
/usr/local/nagios/sbin.

So, in /usr/local/nagios/sbin, you see a file named trends.cgi?
statusmap.cgi, statuswrl.cgi, histogram.cgi? Your web server is saying
that you do not. You said earlier --

"In the error_log it says "[error] [client 127.0.0.1] script not found
or unable to stat: /usr/local/nagios/sbin/trends.cgi, referer:
http://localhost/nagios/side.html."  Same kind of log message for the
other links (status map, 3-d-status map, alert histogram)."

The above says that /usr/local/nagios/sbin/trends.cgi does not exist. If
it does, are the permissions on the file such that your web server can
read and execute it? 'make install' should have set them properly. If
the file exists and the permissions appear to be correct, re-check that
you don't have SELinux enabled or at least misconfigured.

If the file does not exist, read the FAQ.

--
Marc

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
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