Re: [users@httpd] Help debugging 500 Error

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I found what was going on. I thought I let other know in case anybody is interested and close this thread.

We have a third-party Apache filter to enforce authentication and it turned out that the filter is the problem as it rejects the request b/c of some chars in URL. Nothing wrong w/ Apache!

Thanks for everybody's help.

-Jalil

On 9/15/06, Jalil Feghhi <jalil.feghhi@xxxxxxxxx> wrote:
Owen,

What we are doing is we reverse proxy our requests for a /main/ in the URL to one of our servers. Everything works so far except for this URL (/main/FileStore.ashx/Attachment/13001=Blue%20hills.jpg ) which is just a .jpg file. I don't know what is special about it! Same URLs without a %20 work fine!!

Here is what I have in httpd.conf in (do I need anything else?)

ErrorLog logs/error.log

LogLevel debug

LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
LogFormat "%h %l %u %t \"%r\" %>s %b" common
LogFormat "%{Referer}i -> %U" referer
LogFormat "%{User-agent}i" agent

LoadModule  proxy_module       modules/mod_proxy.so
LoadModule  proxy_http_module  modules/mod_proxy_http.so
LoadModule  headers_module     modules/mod_headers.so
LoadModule  deflate_module     modules/mod_deflate.so

ProxyRequests Off
ProxyPreserveHost On

ProxyPass /main/ http://sw55qaprimoa01/main/
ProxyPassReverse /main/ http://sw55qaprimoa01/main/

The rest is the default from the apache ( 2.0.59 - we have to use this version) installation.

I cleared the log files and ran the test again and just tryied to get the file that has the issue. Here is the only entry in access.log:

10.172.93.120 - - [15/Sep/2006:14:44:04 +0000] "GET /main/FileStore.ashx/Attachment/13001=Blue%20hills.jpg HTTP/1.1" 500 628

And last entries from error.log:

[Fri Sep 15 14:43:08 2006] [debug] child.c(697): Child 5684: Worker thread 244 starting.
[Fri Sep 15 14:43:08 2006] [debug] child.c(697): Child 5684: Worker thread 245 starting.
[Fri Sep 15 14:43:08 2006] [debug] child.c(697): Child 5684: Worker thread 246 starting.
[Fri Sep 15 14:43:08 2006] [debug] child.c(697): Child 5684: Worker thread 247 starting.
[Fri Sep 15 14:43:08 2006] [debug] child.c(697): Child 5684: Worker thread 248 starting.
[Fri Sep 15 14:43:08 2006] [debug] child.c(697): Child 5684: Worker thread 249 starting.

As you see, there is nothing w/ the same timestamp and that is the end of error.log. I don't know if logs are buffered but even if I do stop apache, I don't see anything related to this request in error.log.



-Jalil


On 9/14/06, Boyle Owen < Owen.Boyle@xxxxxxx> wrote:
> -----Original Message-----
> From: Jalil Feghhi [mailto:jalil.feghhi@xxxxxxxxx]
> Sent: Thursday, September 14, 2006 11:28 PM
> To: users@xxxxxxxxxxxxxxxx
> Subject: [users@httpd] Help debugging 500 Error
>
> 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.

500 usually means that the request caused apache to execute some
server-sided code (eg CGI or PHP) but that the program failed. So this
will be an error in the program apache called - not in apache itself or
in any proxy.

> There is no info in error.log file that
> helps me find out what went wrong.

Are you absolutely sure? Every error in apache (4xx or 5xx response
code) should lead to a line in the error log.. please check again
(cross-reference the timestamps) Are you sure you don't get "Premature
end of script headers"?

> I was wondering how else I can get more info why the request
> failed.

It depends on the server-sided logic - if it's CGI, you can get the
script output by activating ScriptLog (see docs for details).

> I am sure the request doesn't get reverse proxied to
> the destination web server and something happens inside Apache.

This is correct..

But I'm wondering why a dynamic resource would end up getting proxied -
usually, you proxy requests immediately (based on the pattern of the
URL). Can you supply more details of exactly how your site works?

Rgds,
Owen Boyle
Disclaimer: Any disclaimer attached to this message may be ignored.

>
> Any help is appreciated.
>
> -Jalil
>
> --
> Jalil
>


This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please notify the sender urgently and then immediately delete the message and any copies of it from your system. Please also immediately destroy any hardcopies of the message. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. The sender's company reserves the right to monitor all e-mail communications through their networks. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them to be the views of the sender's company.

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL: http://httpd.apache.org/userslist.html > for more info.
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
   "   from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx




--
Jalil



--
Jalil
[Index of Archives]     [Open SSH Users]     [Linux ACPI]     [Linux Kernel]     [Linux Laptop]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Squid]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]

  Powered by Linux