ID:               28556
 User updated by:  floeff at arcor dot de
 Reported By:      floeff at arcor dot de
-Status:           Feedback
+Status:           Open
 Bug Type:         CGI related
 Operating System: Linux 2.4
 PHP Version:      4.3.6
 New Comment:

Sorry, seems I forgot to update this bug report.
The problem disappears as soon as I do *NOT* compile with --with-libmm

So it seem to be a libmm bug?


Previous Comments:
------------------------------------------------------------------------

[2004-12-13 01:06:13] [EMAIL PROTECTED]

Please try using this CVS snapshot:

  http://snaps.php.net/php4-STABLE-latest.tar.gz
 
For Windows:
 
  http://snaps.php.net/win32/php4-win32-STABLE-latest.zip



------------------------------------------------------------------------

[2004-07-08 17:58:36] floeff at arcor dot de

I have tried on a lot of machines.

------------------------------------------------------------------------

[2004-07-08 13:02:00] [EMAIL PROTECTED]

Have you tried on another machine?

------------------------------------------------------------------------

[2004-06-24 18:18:03] trevor at verite dot com

I have also experienced this problem, we have a nightly crontab that
uses the CGI version of PHP to run a weekly import, every week we need
to kill the script because even with a exit; command at the end it just
keeps running and taking up more and more memory/processor time. I'm not
sure if this is related but..

We're on a debian potato/apache 1.3/PHP 4.3.7 (Jun 7th Build).

Any ideas?

------------------------------------------------------------------------

[2004-05-28 14:37:06] floeff at arcor dot de

Description:
------------
Sorry for posting this again and again, but I still experience this
problem and there seems to be no way for me to solve it. I've got
confirmation from others that this problem is not only mine, so please
take the time to read this.

I've tried Apache 1.3 and 2.0, both on Linux 2.4. I've tried using
suEXEC and not using suEXEC, and I even tried modules that stop script
execution at a specific load average (tested with 1.00!) or number of
processes (tested with 10!). But nothing seems to help in the following
case:

I run PHP as CGI because I don't want to have world-readable scripts
and mod_perchild is not ready yet. When I do a hard reload - i.e.
reloading the same script for about 10 seconds continously which should
open quite a lot of scripts - I can crash the server. PHP-CGI-processes
become zombies, I get a load average of about 90 (!) and it can take up
to 30 minutes until the system responds again. This happens even with
the simplest PHP scripts like a phpinfo call, but Perl scripts make
absolutely no problem.

The PHP developers say it's an Apache problem, the Apache developers
say it's a PHP problem. So *PLEASE* take the time to review this one
again - I'm helpless right now! :-( I know there must be a solution,
because some providers run PHP as CGI without problems, but I don't
know what it could be. :-(



------------------------------------------------------------------------


-- 
Edit this bug report at http://bugs.php.net/?id=28556&edit=1

Reply via email to