| Bug #46218 | apache2 reaches max clients limit with error in php_stdiop_set_option | ||||
|---|---|---|---|---|---|
| Submitted: | 2 Oct 2008 1:47pm UTC | Modified: | 27 Oct 10:04am UTC | ||
| From: | funky2step at gmail dot com | Assigned to: | |||
| Status: | Bogus | Category: | Streams related | ||
| Version: | 5.2.6 | OS: | RHEL ES Rel 4 (Nahant Update 6) | ||
| Votes: | 16 | Avg. Score: | 4.9 ± 0.5 | Reproduced: | 13 of 13 (100.0%) |
| Same Version: | 11 (84.6%) | Same OS: | 6 (46.2%) | ||
[2 Oct 2008 1:47pm UTC] funky2step at gmail dot com
[7 Oct 2008 9:11am UTC] funky2step at googlemail dot com
Does anyone have any ideas about this? It's causing a lot of problems as it happens quite frequently.
[6 Nov 2008 10:38am UTC] funky2step at googlemail dot com
Thanks for the reply. Do you actually know if there is a problem with the main release of php 5.2. I'm slightly cautious about installing a snapshot because it is a busy production site. Are there any issues with installing a snapshot?
[7 Nov 2008 9:09am UTC] funky2step at googlemail dot com
I installed the latest snapshot of PHP5 (PHP 5.2.7RC3-dev) and the problem remains. In fact it has happened twice in the space of 24 hours. This problem doesn't just occur with this particular server and its associated site but on all other php5.2.6 and apache2 installations. Has no-one else seen this serious problem with busy sites using this software?
[13 Mar 2:23pm UTC] mibrahim at mibrahim dot net
Same exact problem. Tested it by lowering MaxClients, apache hangs within 1 minute. The only temporary solution is to increase MaxClients way up, and restart the server with a cron job every period of time.
[25 Mar 4:11pm UTC] funky2step at gmail dot com
We fixed this in the end by ditching apache2 and running php5 with apache 1.3.41 The problem has not occurred in the month or so since implementing it and considering it used to happen at least once per day, I think this is a decent solution.
[6 Apr 9:12pm UTC] jani@php.net
What MPM did you use with Apache2?
[7 Apr 11:06am UTC] 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.
[9 Apr 9:24am UTC] funky2step at googlemail dot com
We used the prefork mpm.
[14 Apr 1:00am UTC] 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".
[8 Oct 8:04pm UTC] 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 ?
[20 Oct 12:06am UTC] joliver at gmx dot at
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.
[20 Oct 7:27pm UTC] srinatar@php.net
to me, it sounds more like configuration issue rather than a possible bug within php. if your application is taking time to long to process , then either you will need to reduce the maximum execution time of your php script (within php.ini) or increase apache's max client value to address to your system load.. did you try to reduce the maximum_execution_time in your php.ini setting to make sure that your php scripts are terminated after some time ? if you think it is some php bug that is causing it, get pstack output of your php process on a regular basis and see what all these processes are doing
[27 Oct 9:36am UTC] joliver at gmx dot at
Thank you for your response. We found out the problem yesterday, it was eaccelerator, not php/apache. The problem described before occured when eaccelerator didn't have any memory left (shm_size) which happend regularily depending on the number of visits. Sorry for accusing php/apache, the reason for the problem wasn't easy to find.
[27 Oct 10:04am UTC] johannes@php.net
Do not file bugs when you have Zend extensions (zend_extension=) loaded. Examples are Zend Optimizer, Zend Debugger, Turck MM Cache, APC, Xdebug and ionCube loader. These extensions often modify engine behavior which is not related to PHP itself.
