Bookmarks

Yahoo Gmail Google Facebook Delicious Twitter Reddit Stumpleupon Myspace Digg

Search queries

192.168.1.41:8000, Www.xxxcon., %s wwwxxxcon, %s wwwxxxcon, www.xxxcon, xxxxdup, bitlord outgoing port settings, ckowwwxxx, 192.168.1.41:8000/nor-482.html, php.ini "Unable to initialize module"

Links

XODOX
Impressum

#1: Debuggin internal server errors

Posted on 2006-09-14 23:27:21 by Jalil Feghhi

------=_Part_24674_24905109.1158269241672
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

We are using Apache 2.0.x with mod_proxy and for a specific URL we get a 500
error. I check the error and access log files and only see that there was an
internal server error in the access.log file. There is no info in
error.logfile that helps me find out what went wrong.

I was wondering how else I can get more info why the request failed. I am
sure the request doesn't get reverse proxied to the destination web server
and something happens inside Apache.

Any help is appreciated.

-Jalil

------=_Part_24674_24905109.1158269241672
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

We are using Apache 2.0.x with mod_proxy and for a specific URL we get a 500 error. I check the error and access log files and only see that there was an internal server error in the access.log file. There is no info in error.log
file that helps me find out what went wrong.<br><br>I was wondering how else I can get more info why the request failed. I am sure the request doesn't get reverse proxied to the destination web server and something happens inside Apache.
<br><br>Any help is appreciated.<br><br>-Jalil

------=_Part_24674_24905109.1158269241672--

Report this message

#2: Re: Debuggin internal server errors

Posted on 2006-09-21 10:07:39 by James Blond

Start apache with
apache -e debug
maybe the old apache -t also helps

apache -t -e debug

Hope that helps, if you haven't allready fixed that.

Mario

On 9/14/06, Jalil Feghhi <jalil.feghhi@gmail.com> wrote:
> We are using Apache 2.0.x with mod_proxy and for a specific URL we get a 500
> error. I check the error and access log files and only see that there was an
> internal server error in the access.log file. There is no info in error.log
> file that helps me find out what went wrong.
>
> I was wondering how else I can get more info why the request failed. I am
> sure the request doesn't get reverse proxied to the destination web server
> and something happens inside Apache.
>
> Any help is appreciated.
>
> -Jalil

Report this message