Bug 817928 - Apache with high MaxClient values hang with 308 kernel release
Apache with high MaxClient values hang with 308 kernel release
Status: CLOSED DUPLICATE of bug 804778
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: httpd (Show other bugs)
5.8
All Linux
urgent Severity urgent
: rc
: 5.8
Assigned To: Joe Orton
BaseOS QE Security Team
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-05-01 16:16 EDT by Jamie Duncan
Modified: 2012-05-01 17:01 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-05-01 17:01:26 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
CentOS 0005634 None None None Never

  None (edit)
Description Jamie Duncan 2012-05-01 16:16:43 EDT
Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
patch -p0 << EOF
--- /etc/httpd/conf/httpd.conf 2012-04-12 12:34:41.000000000 -0700
+++ /etc/httpd/conf/httpd.conf.new 2012-04-12 12:35:21.000000000 -0700
@@ -98,11 +98,11 @@
 # MaxClients: maximum number of server processes allowed to start
 # MaxRequestsPerChild: maximum number of requests a server process serves
 <IfModule prefork.c>
-StartServers 8
+StartServers 1001
 MinSpareServers 5
 MaxSpareServers 20
-ServerLimit 256
-MaxClients 256
+ServerLimit 1001
+MaxClients 1001
 MaxRequestsPerChild 4000
 </IfModule>
EOF
service httpd start
ab -n 2000 -c 1 http://127.0.0.1/icons/blank.gif [^]

  
Actual results:
Apache hangs, essentially going catatonic.

Expected results:
Apache would serve content normally


Additional info:
http://bugs.centos.org/view.php?id=5634
Comment 1 Jamie Duncan 2012-05-01 17:01:26 EDT

*** This bug has been marked as a duplicate of bug 804778 ***

Note You need to log in before you can comment on or make changes to this bug.