perl-modperl mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeff Trawick <>
Subject Re: How to determine what makes Apache crash?
Date Thu, 07 Mar 2013 15:02:27 GMT
On Thu, Mar 7, 2013 at 9:52 AM, Michiel Beijen <>wrote:

> Hi,
> I'm using mod_perl 2.0.7 on Windows with Apache 2.2.23. I got Apache
> from Apachelounge, and compiled mod_perl and perl 5.16.2 myself using
> Visual Studio 2008. I'm using a 32-bit Windows Vista.
> Pretty frequently my app (which works just fine on Linux) makes Apache
> crash. If I perform 500 requests with Apache Bench, I see this:
> Benchmarking localhost (be patient)
> Completed 100 requests
> Completed 200 requests
> Completed 300 requests
> apr_socket_recv: An existing connection was forcibly closed by the
> remote host.   (730054)
> Total of 338 requests completed
> In the apache error log I see apache is restarting, but this results
> in some HTTP 500 errors that make the apache-bench results fail. When
> using a web browser, I also get these http 500 errors.
> If I run the application using native CGI (i.e. I turn off mod_perl) I
> do not see crashes but of course it is *very* slow.
> How can I find out what makes apache/mod_perl crash?

I don't see any Windows crash diagnosis information on this page:   Is Dr. Watson still the way to

mod_backtrace ( may be a
shortcut to getting a backtrace.  There's a binary for use with Apache 2.2
on Windows in the download package.

Any mechanism for getting a backtrace will require that symbol files (.pdb
files) matching your Apache httpd build be present.  I don't know how the
Apache Lounge distributions accommodate that.  Some other builds provide a
separate .zip with the .pdb files, to be unpacked from the Apache httpd
install directory prior to collecting problem documentation.

> --
> Mike

Born in Roswell... married an alien...

View raw message