The following reply was made to PR general/5278; it has been noted by GNATS.
From: Marc Slemko <[EMAIL PROTECTED]>
To: Apache bugs database <[EMAIL PROTECTED]>
Cc: Subject: RE: general/5278: Apache don't react after MaxClients where on the
server (fwd)
Date: Thu, 11 Nov 1999 11:18:29 -0700 (MST)
---------- Forwarded message ----------
Date: Thu, 11 Nov 1999 16:55:57 +0100
From: Djon Kleine <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: RE: general/5278: Apache don't react after MaxClients where on the
server
Hi,
I resolved the bug myself.
Try this : commandout your ErrorLog (the main not of a virtual host) and
make the
MaxClients real low.
#ErrorLog logs/error_log
MaxClients 200
If the server gets to his max clients te server will write to the
error_log!!
But we don't have an errorlog. If this hapens the server will stop serving.
-----Oorspronkelijk bericht-----
Van: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Verzonden: dinsdag 9 november 1999 22:20
Aan: apache-bugdb@apache.org; [EMAIL PROTECTED];
[EMAIL PROTECTED]
Onderwerp: Re: general/5278: Apache don't react after MaxClients where
on the server
[In order for any reply to be added to the PR database, ]
[you need to include <[EMAIL PROTECTED]> in the Cc line ]
[and leave the subject line UNCHANGED. This is not done]
[automatically because of the potential for mail loops. ]
[If you do not include this Cc, your reply may be ig- ]
[nored unless you are responding to an explicit request ]
[from a developer. ]
[Reply only with text; DO NOT SEND ATTACHMENTS! ]
Synopsis: Apache don't react after MaxClients where on the server
State-Changed-From-To: open-feedback
State-Changed-By: marc
State-Changed-When: Tue Nov 9 13:19:45 PST 1999
State-Changed-Why:
You need to provide some more details and try to look into
what is going on a bit more.
Are you using NFS?
Enable mod_status, then look at the server-status page over
time. Is it filling up? Are there slots that claim to be
active but haven't had a request serviced in a long time?
How many httpds are running soon after you start the server?
Does that grow evenly, or in big leaps? If evenly, find
one of the httpds that has been sitting around and not doing
anything for a while and run strace or gdb on it to see what
it is doing.
