Mailing-List: contact users-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@httpd.apache.org
Received-SPF: pass (asf.osuosl.org: local policy)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 20 Feb 2006 14:27:22 -0600
Message-ID: <D416592366C7B9449C626E43E65C8C6B782A5B@BENITO.Office.nFusion>
Thread-Topic: [users@httpd] Why the sudden need to raise MaxClients?
Thread-Index: AcY2TPPNGo/Wyho6TiK9UaqVFWMCUgADowhg
From: "Sage Weaver" <sage@nfusion.com>
To: <users@httpd.apache.org>
Subject: RE: [users@httpd] Why the sudden need to raise MaxClients?

Thanks for the reply -- at least knowing this is abnormal is a step in
the right direction.

By "standard debian packages," I mean I am using unmodified packages
from the stable distribution of debian; no backports, no recompiled
packages.  The package version is 2.0.54-5, which is the latest version
available from the official debian stable repository.

I would implement mod_status, except that once MaxClients is reached,
won't mod_status be useless, since it relies on being able to serve a
page via HTTP?  Or will mod_status work regardless?

-----Original Message-----
From: jslive@gmail.com [mailto:jslive@gmail.com] On Behalf Of Joshua
Slive
Sent: Monday, February 20, 2006 12:35 PM
To: users@httpd.apache.org
Subject: Re: [users@httpd] Why the sudden need to raise MaxClients?

On 2/20/06, Sage Weaver <sage@nfusion.com> wrote:
> I am having this exact same problem.  I'm also using standard debian=20
> packages for Apache 2.0.54, and the prefork MPM, except my MaxClients=20
> setting is already set to 512.
>
> The minute I hit 513 apache2 processes (listed in "ps -C apache2", the

> server stops responding entirely.  Those processes seem to never
close.
> The only way to fix it is to reload Apache via "/etc/init.d/apache2=20
> restart"

Well, "standard debian packages" mean nothing to me.  And given the fact
that it is being reported by two debian users, I suspect it is something
in there that is causing the problem.

What you are reporting is certainly not normal behavior.  You can use
mod_status's server-status handler to at least see what the processes
are doing.

Joshua.

---------------------------------------------------------------------
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@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org


---------------------------------------------------------------------
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@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org