perl-modperl mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From fREW Schmidt <fri...@gmail.com>
Subject Apache crashes relatively often
Date Wed, 17 Jun 2009 18:24:24 GMT
Hey guys,

We are having weird memory leak issues with Apache and some mod_perl.
Basically what happens is that, depending on load, we eventually run out of
ram and apache crashes.  We have the setting that will restart apache after
a given numer of requests, and that seems to work temporarily, but
eventually in the log it claims to restart, but no ram is freed.  The
following is written to the log when that happens:


[Wed Jun 17 13:07:49 2009] [notice] Child 5056: Process exiting because it
> reached MaxRequestsPerChild. Signaling the parent to restart a new child
> process.
> [Wed Jun 17 13:07:49 2009] [notice] Parent: Received restart signal --
> Restarting the server.
> [Wed Jun 17 13:07:49 2009] [warn] (OS 10038)An operation was attempted on
> something that is not a socket.  : setsockopt(SO_UPDATE_ACCEPT_CONTEXT)
> failed.
> [Wed Jun 17 13:07:50 2009] [notice] Child 5056: Released the start mutex
> [Wed Jun 17 13:07:50 2009] [notice] Apache/2.2.11 (Win32) mod_ssl/2.2.11
> OpenSSL/0.9.8i mod_perl/2.0.4-dev Perl/v5.10.0 configured -- resuming normal
> operations
> [Wed Jun 17 13:07:50 2009] [notice] Server built: Dec 10 2008 00:10:06
> [Wed Jun 17 13:07:50 2009] [notice] Parent: Created child process 3164
> [Wed Jun 17 13:07:51 2009] [notice] Child 3164: Child process is running
> [Wed Jun 17 13:07:51 2009] [notice] Child 3164: Acquired the start mutex.
> [Wed Jun 17 13:07:51 2009] [notice] Child 3164: Starting 64 worker threads.
> [Wed Jun 17 13:07:51 2009] [notice] Child 3164: Starting thread to listen
> on port 443.
> [Wed Jun 17 13:07:51 2009] [notice] Child 3164: Starting thread to listen
> on port 80.
> [Wed Jun 17 13:08:00 2009] [notice] Child 5056: All worker threads have
> exited.
> [Wed Jun 17 13:08:00 2009] [notice] Child 5056: Child process is exiting
>

And just to be clear, here are the relevant conf sections:

ThreadLimit 64
> ThreadsPerChild 64
> MaxRequestsPerChild 10000
> MaxMemFree 51200
>

That's in the "root" part of the config, or to be more explicit, it's not in
a virtual host or anything like that.

We are running apache on a Windows server, so if that could be part of the
issue let me know.

Any help at all would be very much appreciated.

-- 
fREW Schmidt
http://blog.afoolishmanifesto.com

Mime
View raw message