https://issues.apache.org/bugzilla/show_bug.cgi?id=45826
Summary: Apache Dies When HItting the Per User Process Limit
Product: Apache httpd-2
Version: 2.2.8
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: prefork
AssignedTo: [email protected]
ReportedBy: [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]
I've recently been experiencing apache crashes when a system-wide per-user
process limit is reached. I have confirmed that if a per-user limit is set and
the parent apache process spawns as many children as this limit, one of the
child processes will die and the parent will then exit.
Here is a pertinent section of my log files:
[Wed Sep 17 09:35:47 2008] [alert] (11)Resource temporarily unavailable:
setuid:
unable to change to uid: 33
[Wed Sep 17 09:35:47 2008] [alert] (11)Resource temporarily unavailable:
setuid:
unable to change to uid: 33
[Wed Sep 17 09:35:47 2008] [alert] (11)Resource temporarily unavailable:
setuid:
unable to change to uid: 33
[Wed Sep 17 09:35:47 2008] [alert] Child 7038 returned a Fatal error... Apache
i
s exiting!
I have duplicated this behavior by setting the per-user process limit to 64 in
two different versions of Open SuSE Linux (10.3 and 11.0) x86_64 and Debian on
Power PC and with apache versions 2.2.3, 2.2.4 and 2.2.8. Under Debian, this
behavior will not manifest itself unless a "ulimit -u 64" is inserted into the
apache2ctl script.
Once started with a process limit, I can then access a simple "Hello World" cgi
script repeatedly using ab2 (e.g. "ab2 -n 512 -c 512
http://server.com/~user/index.cgi";) and the errors above will show up in the
logs.
At that point, all of the orphaned apache processes are inherited by init and
it is necessary to kill them manually before I can restart apache.
It is necessary to have per-user process limits in our environment.
I have not attempted to duplicate this behavior on a non-Linux OS.
--
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]
