httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 32239] - Server reached MaxClients setting on FreeBSD
Date Wed, 17 Nov 2004 20:51:20 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=32239>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=32239





------- Additional Comments From trawick@apache.org  2004-11-17 21:51 -------
Trying different acceptmutex flavors is a good plan.  With processes blocked
waiting for the accept mutex, either something is hosed with the mutex or the
one child process holding that mutex got stuck in the narrow window where it is
held.  (It needs to call select or poll followed by accept.)

Did you encounter any child process crashes?  (check web server error log)  That
can sometimes result in mutex ownership being lost.

Note that "server reached maxclients" is a one-time only message; no later
message if problem resolved itself.  A child process blocked waiting for the
accept mutex definitely means you aren't currently at maxclients, since that
only counts processes which are handling an active connection.

Are there any FreeBSD kernel limits/tuning related to flock?  You would be
growing in number of busy child processes up until you reach maxclients, then
when load subsides you'll suddenly have more processes blocked in that accept
mutex than you ever had before.  This could result in kernel being unable to
allocate enough of some sort of resource to handle the many simultaneous lock
requests.  Maybe "AcceptMutex something-besides-flock" will work around that.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


Mime
View raw message