https://issues.apache.org/bugzilla/show_bug.cgi?id=48744
Summary: apache have more than ServerLimit processes
Product: Apache httpd-2
Version: 2.2.14
Platform: HP
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: worker
AssignedTo: [email protected]
ReportedBy: [email protected]
we have busy web site and for last few weeks we have problem with apache
processes eat all memory. we attempt to control problem by lowering ServerLimit
(documentation states that is max number of apache processes).
ServerLimit is at 75 (confirmed by /server-info as active value), but ps auxw
show around 90-95 processes.
here is part of worker config:
<IfModule mpm_worker_module>
ServerLimit 75
ThreadLimit 30
StartServers 11
MinSpareThreads 45
MaxSpareThreads 95
ThreadsPerChild 25
MaxClients 1500
MaxRequestsPerChild 500
</IfModule>
server is 12core, 8Gb ram. cpu usage is about 20-25% under normal load. at
busier part of day sometimes processes start to eat more memory, and server
locks (no swap configured as this make stuff even more painful). if i grab some
server statistics (ps, netstat, df...) between start of problem and lock-up, i
see there are more apache processes than configured.
is this a bug in ServerLimit or that directive really cannot keep server
processes limited to number? (next i going to use kernel mechanism to keep
apache down in limits, but i'm not sure how apache would like fork() to fail)
because i would rather have apache shot dead (and restarted by cron job) than
dead server (which i need to restart).
additional info: server is using php & proxy modules.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
