I'm looking to troubleshoot this error when I run "tail /etc/httpd/logs/error_log"
[Tue Oct 09 07:22:59 2007] [error] [client 127.0.0.1] Directory index forbidden by rule: /var/www/html/
(I get this when I run Nagios' "./check_http -H 127.0.0.1".)
All I did was install CentOS and then modify httpd.conf to include "ServerName 192.168.1.10:80" and also run " htpasswd -c /etc/nagios/htpasswd.users nagiosadmin".
Is this a permissions issue on my /var/www/html/ folder?
I tried to get the Apache page to serve properly, and it's not doing that. And when I try from another computer, I don't see anything in the logs, which made me think it was an IPTABLES issue (which it doesn't appear to be).
Chain RH-Firewall-1-INPUT (2 references) target prot opt source destination ACCEPT all -- anywhere anywhere ACCEPT icmp -- anywhere anywhere icmp any ACCEPT ipv6-crypt-- anywhere anywhere ACCEPT ipv6-auth-- anywhere anywhere ACCEPT udp -- anywhere 224.0.0.251 udp dpt:5353 ACCEPT udp -- anywhere anywhere udp dpt:ipp ACCEPT all -- anywhere anywhere state RELATED,ESTAB LISHED ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:s sh ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:h ttp ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:f tp ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:s mtp REJECT all -- anywhere anywhere reject-with icmp-ho st-prohibited
Directory index is a feature of apache, which: - if there is a file named in DirectoryIndex directive (usually index.html) in the requested directory, then show it (i think this is made by mod_dir) - if not, then create a list of files, if you have mod_autoindex loaded and Options +Indexes in directory configuration (I recommend http://httpd.apache.org/docs/2.2/mod/mod_dir.html and http://httpd.apache.org/docs/2.2/mod/mod_autoindex.html)
I believe, this comes because your /var/www/html contains no index mentioned in DirectoryIndex rule. What is the content of /var/www/html?
best regards ------------------------------------------------------------------------------- Tomáš Ruprich ruprich@uikt.mendelu.cz DCD IICT MUAF Brno tel.: +420 545 132 885, +420 602 127 744 -------------------------------------------------------------------------------
Tue, Oct 09, 2007 ve 08:34:21AM -0700, Rogelio Bastardo napsal:
I'm looking to troubleshoot this error when I run "tail /etc/httpd/logs/error_log"
[Tue Oct 09 07:22:59 2007] [error] [client 127.0.0.1] Directory index forbidden by rule: /var/www/html/
(I get this when I run Nagios' "./check_http -H 127.0.0.1".)
All I did was install CentOS and then modify httpd.conf to include "ServerName 192.168.1.10:80" and also run " htpasswd -c /etc/nagios/htpasswd.users nagiosadmin".
Is this a permissions issue on my /var/www/html/ folder?
I tried to get the Apache page to serve properly, and it's not doing that. And when I try from another computer, I don't see anything in the logs, which made me think it was an IPTABLES issue (which it doesn't appear to be).
Chain RH-Firewall-1-INPUT (2 references) target prot opt source destination ACCEPT all -- anywhere anywhere ACCEPT icmp -- anywhere anywhere icmp any ACCEPT ipv6-crypt-- anywhere anywhere ACCEPT ipv6-auth-- anywhere anywhere ACCEPT udp -- anywhere 224.0.0.251 udp dpt:5353 ACCEPT udp -- anywhere anywhere udp dpt:ipp ACCEPT all -- anywhere anywhere state RELATED,ESTAB LISHED ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:s sh ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:h ttp ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:f tp ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:s mtp REJECT all -- anywhere anywhere reject-with icmp-ho st-prohibited
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On 10/9/07, Rogelio Bastardo scubacuda@gmail.com wrote:
I'm looking to troubleshoot this error when I run "tail /etc/httpd/logs/error_log"
[Tue Oct 09 07:22:59 2007] [error] [client 127.0.0.1] Directory index forbidden by rule: /var/www/html/
(I get this when I run Nagios' "./check_http -H 127.0.0.1".)
All I did was install CentOS and then modify httpd.conf to include "ServerName 192.168.1.10:80" and also run " htpasswd -c /etc/nagios/htpasswd.users nagiosadmin".
Is this a permissions issue on my /var/www/html/ folder?
No, this is caused by the Indexes setting in your Options statement in your httpd.conf file, or other included file for this directory (welcome.conf). Consult your config and the apache documentation for details. If you're serving up the standard welcome to centos page, this is actually an error page because you have no other page to default to. create a blank index.html page or put something there and you won't get this.
Actuallly, believe it or not, but everything was ok. Those with the browser I was using had a known issue accessing VMs, I was told.
I did the exactly same thing on another VM setup, and everything worked beautifully.
Thanks for the help, everyone.
salam,
Please check what is your document root???? it is /var/www/html???? in httpd.conf where does your nagios folder has been placed???? is it /var/www/html???
gust give the server name 192.168.1.10 and no need to put :80, as it is already listening on 80.
Regards,
Umair Shakil ETD
On 10/9/07, Rogelio Bastardo scubacuda@gmail.com wrote:
I'm looking to troubleshoot this error when I run "tail /etc/httpd/logs/error_log"
[Tue Oct 09 07:22:59 2007] [error] [client 127.0.0.1] Directory index forbidden by rule: /var/www/html/
(I get this when I run Nagios' "./check_http -H 127.0.0.1".)
All I did was install CentOS and then modify httpd.conf to include "ServerName 192.168.1.10:80" and also run " htpasswd -c /etc/nagios/htpasswd.users nagiosadmin".
Is this a permissions issue on my /var/www/html/ folder?
I tried to get the Apache page to serve properly, and it's not doing that. And when I try from another computer, I don't see anything in the logs, which made me think it was an IPTABLES issue (which it doesn't appear to be).
Chain RH-Firewall-1-INPUT (2 references) target prot opt source destination ACCEPT all -- anywhere anywhere ACCEPT icmp -- anywhere anywhere icmp any ACCEPT ipv6-crypt-- anywhere anywhere ACCEPT ipv6-auth-- anywhere anywhere ACCEPT udp -- anywhere 224.0.0.251 udp dpt:5353 ACCEPT udp -- anywhere anywhere udp dpt:ipp ACCEPT all -- anywhere anywhere state RELATED,ESTAB LISHED ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:s sh ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:h ttp ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:f tp ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:s mtp REJECT all -- anywhere anywhere reject-with icmp-ho st-prohibited
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Umair, please stop top-posting. It screws the readability of the messages in the archive.
On 10/9/07, umair shakil umairshakeel@gmail.com wrote:
salam,
Please check what is your document root???? it is /var/www/html????
Something appears to be malfunctioning with your '?' on your keyboard.
in httpd.conf where does your nagios folder has been placed???? is
it /var/www/html???
This doesn't have anything to do with his issue. From his email, nagios is working fine, it's just returning that his webserver is throwing an error. It's the webserver error he's tracking down.
gust give the server name 192.168.1.10 and no need to put :80, as it is already listening on 80.
While you don't *need* to specify the port, the example config does this and it's beneficial to do this if you have more than one website, with apache listening on multiple ports. Otherwise you have the potential for one ServerName definition to override another. With apache, it's best to be as explicit as possible.
salam!!!
please explain...... i have only post one message.... clear ur point
Regards,
Umair
On 10/10/07, Jim Perrin jperrin@gmail.com wrote:
Umair, please stop top-posting. It screws the readability of the messages in the archive.
On 10/9/07, umair shakil umairshakeel@gmail.com wrote:
salam,
Please check what is your document root???? it is /var/www/html????
Something appears to be malfunctioning with your '?' on your keyboard.
in httpd.conf where does your nagios folder has been placed???? is
it /var/www/html???
This doesn't have anything to do with his issue. From his email, nagios is working fine, it's just returning that his webserver is throwing an error. It's the webserver error he's tracking down.
gust give the server name 192.168.1.10 and no need to put :80, as it is already listening on 80.
While you don't *need* to specify the port, the example config does this and it's beneficial to do this if you have more than one website, with apache listening on multiple ports. Otherwise you have the potential for one ServerName definition to override another. With apache, it's best to be as explicit as possible.
-- During times of universal deceit, telling the truth becomes a revolutionary act. George Orwell _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
umair shakil wrote:
salam!!!
please explain...... i have only post one message.... clear ur point
Hi Top posting means replying at the top of a message rather than below or inside the original message. As a preference for this mailing list and a lot of others they ask that you don't do this. The general reason being that it makes the e-mails easier to read.
Regards,
Umair
On 10/10/07, *Jim Perrin* < jperrin@gmail.com mailto:jperrin@gmail.com> wrote:
Umair, please stop top-posting. It screws the readability of the messages in the archive. On 10/9/07, umair shakil <umairshakeel@gmail.com <mailto:umairshakeel@gmail.com>> wrote: > salam, > > Please check what is your document root???? it is /var/www/html???? Something appears to be malfunctioning with your '?' on your keyboard. >in httpd.conf where does your nagios folder has been placed???? is it /var/www/html??? This doesn't have anything to do with his issue. From his email, nagios is working fine, it's just returning that his webserver is throwing an error. It's the webserver error he's tracking down. > gust give the server name 192.168.1.10 <http://192.168.1.10> and no need to put :80, as it is > already > listening on 80. While you don't *need* to specify the port, the example config does this and it's beneficial to do this if you have more than one website, with apache listening on multiple ports. Otherwise you have the potential for one ServerName definition to override another. With apache, it's best to be as explicit as possible. -- During times of universal deceit, telling the truth becomes a revolutionary act. George Orwell _______________________________________________ CentOS mailing list CentOS@centos.org <mailto:CentOS@centos.org> http://lists.centos.org/mailman/listinfo/centos <http://lists.centos.org/mailman/listinfo/centos>
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Salam!!!
Well, man i know i suppose i replied to the orignal message.... its ok
Reagards,
Umair
On 10/11/07, Clint Dilks clintd@scms.waikato.ac.nz wrote:
umair shakil wrote:
salam!!!
please explain...... i have only post one message.... clear ur point
Hi Top posting means replying at the top of a message rather than below or inside the original message. As a preference for this mailing list and a lot of others they ask that you don't do this. The general reason being that it makes the e-mails easier to read.
Regards,
Umair
On 10/10/07, *Jim Perrin* < jperrin@gmail.com mailto:jperrin@gmail.com> wrote:
Umair, please stop top-posting. It screws the readability of the messages in the archive. On 10/9/07, umair shakil <umairshakeel@gmail.com <mailto:umairshakeel@gmail.com>> wrote: > salam, > > Please check what is your document root???? it is/var/www/html????
Something appears to be malfunctioning with your '?' on yourkeyboard.
>in httpd.conf where does your nagios folder has been placed???? is it /var/www/html??? This doesn't have anything to do with his issue. From his email, nagios is working fine, it's just returning that his webserver is throwing an error. It's the webserver error he's tracking down. > gust give the server name 192.168.1.10 <http://192.168.1.10> and no need to put :80, as it is > already > listening on 80. While you don't *need* to specify the port, the example config does this and it's beneficial to do this if you have more than one website, with apache listening on multiple ports. Otherwise you have the potential for one ServerName definition to override another. With apache, it's best to be as explicit as possible. -- During times of universal deceit, telling the truth becomes a revolutionary act. George Orwell _______________________________________________ CentOS mailing list CentOS@centos.org <mailto:CentOS@centos.org> http://lists.centos.org/mailman/listinfo/centos <http://lists.centos.org/mailman/listinfo/centos>
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
on 10/10/2007 9:57 PM umair shakil spake the following:
Salam!!!
Well, man i know i suppose i replied to the orignal message.... its ok
Reagards,
Umair
On 10/11/07, *Clint Dilks* < clintd@scms.waikato.ac.nz mailto:clintd@scms.waikato.ac.nz> wrote:
umair shakil wrote: > salam!!! > > please explain...... i have only post one message.... clear ur point > Hi Top posting means replying at the top of a message rather than below or inside the original message. As a preference for this mailing list and a lot of others they ask that you don't do this. The general reason being that it makes the e-mails easier to read.
Some people just don't listen ;-P
-
Clint Dilks -
Jim Perrin -
Rogelio -
Rogelio Bastardo
-
Scott Silva -
Tomas Ruprich -
umair shakil