ID: 46218 Comment by: joliver at gmx dot at Reported By: funky2step at gmail dot com Status: No Feedback Bug Type: Streams related Operating System: RHEL ES Rel 4 (Nahant Update 6) PHP Version: 5.2.6 New Comment:
Exactly the same problem here: Debian Lenny, apache 2.2.9 (prefork), php 5.2.6, eaccelerator 0.9.5.3 Server crashes every few days with "server reached MaxClients setting, consider raising the MaxClients setting" When restarting several warnings "child process XXX still did not exit, sending a SIGTERM" show up (however much less than MaxClients). We first suspected a Slowloris attack, however we can rule out this after counting new connections in the firewall-logs. Previous Comments: ------------------------------------------------------------------------ [2009-10-08 20:04:27] apache at vacances-location dot net I experiencing exactly the same problem, Apache2 crash with message "reaches the maxclients limit", with no load, and it don't kill the old processes. I have the same versions, but on Debian Lenny. Somebody have a fix ? ------------------------------------------------------------------------ [2009-04-14 01:00:01] php-bugs at lists dot php dot net No feedback was provided for this bug for over a week, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open". ------------------------------------------------------------------------ [2009-04-09 09:24:52] funky2step at googlemail dot com We used the prefork mpm. ------------------------------------------------------------------------ [2009-04-07 11:06:02] david at dsanders dot co dot uk I too am seeing this bug on Apache 2.2.9 with PHP 5.2.6 using MPM Prefork. In a web crawler application that I have written it continually hangs up max clients. ------------------------------------------------------------------------ [2009-04-06 21:12:29] [email protected] What MPM did you use with Apache2? ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/46218 -- Edit this bug report at http://bugs.php.net/?id=46218&edit=1
