We are using a setup with a "light-weight" apache in front of the
mod_perl server.
Lately we have seen some problems with the mod_perl server. From time to
time it stops responding to the requests from the front end. The problem
seems to be related to the mod_perl server only since wget-ing on the
I would like to add that no messages are seen in the error logs. We are
using Apache/1.3.29 and mod_perl/1.29 on Redhat linux.
mvh
Anders Nielsen
Anders Nielsen wrote:
We are using a setup with a "light-weight" apache in front of the
mod_perl server.
Lately we have seen some problems with the mod_perl server. From time to
time it stops responding to the requests from the front end. The problem
seems to be related to the mod_perl server only
On Wed, 2005-03-16 at 21:11 -0500, Stas Bekman wrote:
> Please see:
> 21.7. Hanging Processes: Detection and Diagnostics
> http://modperlbook.org/html/ch21_07.html
>
Thank you for the reply.
The problem I described happened again and I was able to get some more
information.
The server isn't act
Anders Nielsen wrote:
On Wed, 2005-03-16 at 21:11 -0500, Stas Bekman wrote:
Please see:
21.7. Hanging Processes: Detection and Diagnostics
http://modperlbook.org/html/ch21_07.html
Thank you for the reply.
The problem I described happened again and I was able to get some more
information.
The serve
On Fri, 2005-03-18 at 11:15 -0500, Stas Bekman wrote:
> Anders, do you by chance use a proxy that may have eaten the response?
>
> What do you see in logs/access_log, it tells how many bytes were sent to
> the client.
>
> What happens if you replace print($x) with Apache->request->print($x)
>
Anders, the first priority is to figure out how to reproduce the problem
at will. If you don't manage that, you most likely are going to waste
hours staring at the screen. I'd concentrate on that task first.
Try using ab (apachebench), httpd_load or another utility to stress test.
More advanced
On Fri, 2005-03-18 at 17:37 -0500, Stas Bekman wrote:
> Anders, the first priority is to figure out how to reproduce the problem
> at will. If you don't manage that, you most likely are going to waste
> hours staring at the screen. I'd concentrate on that task first.
>
> Try using ab (apachebenc
Anders Nielsen wrote:
[...]
I have been doing some testing with ab and I found some interesting
cases.
On our production system I get the following when testing an important
mod_perl enabled script from my local desktop:
$ ab -n 100 -c 5 "http://www.xx.dk/cgi/xx.cgi?q=test&allowall=1";
[...
On Mon, 2005-03-21 at 16:51 -0500, Stas Bekman wrote:
> > Failed requests:21
> >(Connect: 0, Length: 21, Exceptions: 0)
>
> Googling helps :) Rich Graves says:
> http://my.brandeis.edu/bboard/q-and-a-fetch-msg?msg_id=0001GK
> (Ignore "failed requests" -- ab considers it a failure when
10 matches
Mail list logo
