Return-Path: Delivered-To: apmail-perl-modperl-archive@www.apache.org Received: (qmail 64657 invoked from network); 17 Jun 2009 18:25:06 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 17 Jun 2009 18:25:06 -0000 Received: (qmail 9344 invoked by uid 500); 17 Jun 2009 18:25:16 -0000 Delivered-To: apmail-perl-modperl-archive@perl.apache.org Received: (qmail 9317 invoked by uid 500); 17 Jun 2009 18:25:16 -0000 Mailing-List: contact modperl-help@perl.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list modperl@perl.apache.org Received: (qmail 9309 invoked by uid 99); 17 Jun 2009 18:25:16 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Jun 2009 18:25:16 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of frioux@gmail.com designates 209.85.218.222 as permitted sender) Received: from [209.85.218.222] (HELO mail-bw0-f222.google.com) (209.85.218.222) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Jun 2009 18:25:05 +0000 Received: by bwz22 with SMTP id 22so554418bwz.10 for ; Wed, 17 Jun 2009 11:24:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:from:date:message-id :subject:to:content-type; bh=s8ecjX1h5bbnv4chVnJRuOPsh6gkpp3dFr0+ssZdTUw=; b=jXk7obTzvjcqLCbNjnZ7UaPpc4g8Bn2oWo5tX53uXz9u6++jmHUY19J7ULyK4K2ZZ/ iGPvbLfXn7V5sEwl7hLOFtaw79ABMJ1WwaoiZSoy3/F7gdrXR24N7fi7kE5h2b6IVgK3 a6LK9fF4Lilua23VAy/SCrWoU548Pf4s/W0KE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type; b=urozfC8E//tvi/UnosRtQFGYOgg6tPmHd8xG51ZcnDmKUN3lkTFoBs2wf+UkTfU1Fh B0nPF5zkb1647TwplvCFHZDY2+TWcxGAVm4Rjlg/hIswjxK4oOvPGdS551nYxhQXVWD9 L5WZ4B8e3ed6UjaXT4IszXgBmfTQ3VZHD3un0= MIME-Version: 1.0 Received: by 10.204.65.65 with SMTP id h1mr412223bki.26.1245263084149; Wed, 17 Jun 2009 11:24:44 -0700 (PDT) From: fREW Schmidt Date: Wed, 17 Jun 2009 13:24:24 -0500 Message-ID: Subject: Apache crashes relatively often To: modperl Content-Type: multipart/alternative; boundary=001636c5ad4dc85b16046c8f67f4 X-Virus-Checked: Checked by ClamAV on apache.org --001636c5ad4dc85b16046c8f67f4 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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 --001636c5ad4dc85b16046c8f67f4 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hey guys,

We are having weird memory leak issues with Apache and som= e mod_perl.=A0 Basically what happens is that, depending on load, we eventu= ally run out of ram and apache crashes.=A0 We have the setting that will re= start apache after a given numer of requests, and that seems to work tempor= arily, but eventually in the log it claims to restart, but no ram is freed.= =A0 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 M= axRequestsPerChild. Signaling the parent to restart a new child process. [Wed Jun 17 13:07:49 2009] [notice] Parent: Received restart signal -- Rest= arting the server.
[Wed Jun 17 13:07:49 2009] [warn] (OS 10038)An operat= ion was attempted on something that is not a socket.=A0 : setsockopt(SO_UPD= ATE_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 O= penSSL/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
[W= ed 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 thread= s.
[Wed Jun 17 13:07:51 2009] [notice] Child 3164: Starting thread to li= sten on port 443.
[Wed Jun 17 13:07:51 2009] [notice] Child 3164: Starting thread to listen o= n port 80.
[Wed Jun 17 13:08:00 2009] [notice] Child 5056: All worker th= reads 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:=

ThreadLim= it 64
ThreadsPerChild 64
MaxRequestsPerChild 10000
MaxMemFree 51200

That's in the "root" part of the config, or to b= e 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 appreciate= d.

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