<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE>Re: [Nagios-users] HTTP WARNING: HTTP/1.1 403 Forbidden</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>Does the directory /var/www/html contain and index.html? Are you requesting the right URL that you think you are in you check_http command definition?<BR>
<BR>
<BR>
--<BR>
Marc<BR>
<BR>
Sent from a very tiny wireless device with a very tiny unlit keyboard.<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: Patrick Lambooy <p.lambooy@narmida.com><BR>
To: 'Leonard Miller' <Leonard_Miller@udlp.com>; nagios-users@lists.sourceforge.net <nagios-users@lists.sourceforge.net><BR>
Sent: Sun May 18 16:36:01 2003<BR>
Subject: RE: [Nagios-users] HTTP WARNING: HTTP/1.1 403 Forbidden<BR>
<BR>
<BR>
<BR>
Error does not give anything but ssl_error gives this :<BR>
<BR>
[error] [client 192.168.4.112] Directory index forbidden by rule:<BR>
/var/www/html/<BR>
<BR>
and 112 is the ip of the nagios server.<BR>
<BR>
In the services :<BR>
<BR>
define service{<BR>
use generic-service ; Name<BR>
of service template to use<BR>
<BR>
host_name fileserver<BR>
service_description HTTP<BR>
is_volatile 0<BR>
check_period 24x7<BR>
max_check_attempts 6<BR>
normal_check_interval 6<BR>
retry_check_interval 1<BR>
contact_groups somename-admins<BR>
notification_interval 120<BR>
notification_period 24x7<BR>
notification_options w,u,c,r<BR>
check_command check_http<BR>
}<BR>
<BR>
<BR>
All help welcome tnx dudes<BR>
<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: nagios-users-admin@lists.sourceforge.net<BR>
[<A HREF="mailto:nagios-users-admin@lists.sourceforge.net">mailto:nagios-users-admin@lists.sourceforge.net</A>] On Behalf Of Leonard<BR>
Miller<BR>
Sent: Tuesday, May 13, 2003 6:15 PM<BR>
To: nagios-users@lists.sourceforge.net; p.lambooy@narmida.com<BR>
Subject: RE: [Nagios-users] HTTP WARNING: HTTP/1.1 403 Forbidden<BR>
<BR>
Look at /var/log/httpd/error_log and see what it says. That may<BR>
give you a better idea if it can't read a particular file.<BR>
<BR>
>>> "Carroll, Jim P [Contractor]" <jcarro10@sprintspectrum.com> 05/13/03<BR>
11:56AM >>><BR>
Check file permissions... if Apache can't read the files, that could do<BR>
it.<BR>
<BR>
jc<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: Patrick Lambooy [<A HREF="mailto:p.lambooy@narmida.com">mailto:p.lambooy@narmida.com</A>]<BR>
Sent: Tuesday, May 13, 2003 7:25 AM<BR>
To: nagios-users@lists.sourceforge.net<BR>
Subject: [Nagios-users] HTTP WARNING: HTTP/1.1 403 Forbidden<BR>
<BR>
<BR>
HTTP WARNING: HTTP/1.1 403 Forbidden<BR>
<BR>
Anyone know how to fix this ?<BR>
<BR>
Cant find a solution<BR>
<BR>
Tnx<BR>
<BR>
<BR>
<BR>
-------------------------------------------------------<BR>
Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara<BR>
The only event dedicated to issues related to Linux enterprise solutions<BR>
www.enterpriselinuxforum.com<BR>
<BR>
_______________________________________________<BR>
Nagios-users mailing list<BR>
Nagios-users@lists.sourceforge.net<BR>
<A HREF="https://lists.sourceforge.net/lists/listinfo/nagios-users">https://lists.sourceforge.net/lists/listinfo/nagios-users</A><BR>
::: Please include Nagios version, plugin version (-v) and OS when<BR>
reporting any issue.<BR>
::: Messages without supporting info will risk being sent to /dev/null<BR>
<BR>
<BR>
<BR>
<BR>
-------------------------------------------------------<BR>
This SF.net email is sponsored by: If flattening out C++ or Java<BR>
code to make your application fit in a relational database is painful,<BR>
don't do it! Check out ObjectStore. Now part of Progress Software.<BR>
<A HREF="http://www.objectstore.net/sourceforge">http://www.objectstore.net/sourceforge</A><BR>
_______________________________________________<BR>
Nagios-users mailing list<BR>
Nagios-users@lists.sourceforge.net<BR>
<A HREF="https://lists.sourceforge.net/lists/listinfo/nagios-users">https://lists.sourceforge.net/lists/listinfo/nagios-users</A><BR>
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue.<BR>
::: Messages without supporting info will risk being sent to /dev/null<BR>
</FONT>
</P>
</BODY>
</HTML>