#22975 [Opn->Bgs]: PHP crashed at/after the 26 system-call

From: Date: Wed, 23 Apr 2003 09:25:47 +0000
Subject: #22975 [Opn->Bgs]: PHP crashed at/after the 26 system-call
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-38183@lists.php.net to get a copy of this message
 ID:               22975
 Updated by:       sniper@php.net
 Reported By:      kju at arcor dot de
-Status:           Open
+Status:           Bogus
 Bug Type:         Program Execution
 Operating System: Windows NT 4 SP 6a
 PHP Version:      4.3.2-RC
 New Comment:

If it works on cmd line but not from Apache -> apache bug.



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

[2003-04-01 04:43:03] kju at arcor dot de

additional information (problem not solved yet):

Using the dev-Version produces entries in the nt-eventlog 
PHP Version 4.3.2-RC 
Build Date  Mar 31 2003 09:11:59  

Error Detail in the nt-system-log:
--
User: N/A
EventID: 2000
Source: Srv
Type: Error
Category: None
Description: The server's call to a system service failed
unexpectedly.
--
Starting ONE skript (even phpmyadmin 2.4.0) will put many of these
errors in the system-log.

There are no errors after we have downgraded to 4.3.1, so the
error-messages seem to be a problem/feature in the 4.3.2-dev

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

[2003-04-01 00:29:40] kju at arcor dot de

We are using Apache/1.3.26 (Win32) on a WindowsNT4-Server with SP
6a...

PHP is running as CGI...
Switching the system to use PHP as module isn't easy in our
environment, so we couldn't test it...

Hmmm, we have tested something else yet, we have started the script at
the command-line... the script ends without error! all output is as
expected.

But there seems to bee no problem with the apache-configuration,
because when we turn back to PHP 4.1 all is running well!

How we should explain 'crashed'?
I will try to do that...
Starting a PHP-Script on the WebServer build a new PHP-process on the
machine... After finishing the script the process will end... thats the
normal way, isn't it?

But when n>26 the script (and the process) will never end... We have
set the "set_limit_time" to 30 seconds, after 5 minutes the process is
still "alive", but it doesn't use CPUTime any longer.
No output to the webbrowser is generated.
The output "exec("echo $i >> c:\test.log");" is done up to i=26. No
hint concerning the abort is given from PHP.

What do you think of the source of the error: OS, Apache or PHP?

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

[2003-03-31 18:25:15] sniper@php.net

(updated PHP version info)

And could you explain what you mean with 'crashed'?
Are you using CGI? Under IIS or Apache?



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

[2003-03-31 04:34:15] kju at arcor dot de

we have installed the following version (win32):
PHP Version 4.3.2-RC 
Build Date  Mar 31 2003 09:11:59  

No improvements...

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

[2003-03-31 03:34:34] sniper@php.net

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

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

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/22975

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



Thread (7 messages)

« previous php.bugs (#38183) next »