ID: 26771
Comment by: anakarlarc at hp dot com
Reported By: info at tphnet dot com
Status: Verified
Bug Type: Apache2 related
Operating System: * (ZTS only!)
PHP Version: 4CVS, 5CVS (2004-02-25)
New Comment:
I have the same erro but I don't have php
Apache 2.0.48 Openssl__0.9.7c-win32
Web Logic
I don't have a idea why it is restarting
arent: child process exited with status 128 -- Restarting.
Previous Comments:
------------------------------------------------------------------------
[2004-09-25 00:47:02] OvdSpek at LIACS dot NL
A simple testcase:
<?php
function f()
{
f();
}
f();
?>
This will result in: [notice] Parent: child process exited with status
128 -- Restarting.
I know it's not so valid code, but I do assume this isn't supposed to
restart the entire webserver.
I'd also expect an error message telling me the stack overflowed.
------------------------------------------------------------------------
[2004-09-24 23:47:40] OvdSpek at LIACS dot NL
I'm encountering the same error message with a certain script:
[Fri Sep 24 23:41:51 2004] [notice] Parent: child process exited with
status 128 -- Restarting.
Windows XP SP1
Apache/2.0.50 (Win32)
PHP/4.3.9
------------------------------------------------------------------------
[2004-08-13 05:23:05] loye dot young at iycc dot net
If you have the PEAR Date package installed, this might be a solution:
There is a command in a Pear function that tries to write information
to the server. Some Windows installations and Unix servers with strict
Safe Mode options enabled do not allow this. You can fix this yourself
however.
Open the file ./pear/Date/TimeZone.php in a text editor. Go to line
247. You should be in a function named 'inDaylightTime()'. Add this
line: return date("I"); at the very top of the function. It should now
look like this:
function inDaylightTime($date)
{
return date("I");
$env_tz = "";
if(getenv("TZ"))
$env_tz = getenv("TZ");
putenv("TZ=".$this->id);
$ltime = localtime($date->getTime(), true);
putenv("TZ=".$env_tz);
return $ltime['tm_isdst'];
}
This should stop the error. It did for me. Try it and let us know how
it worked for you.
------------------------------------------------------------------------
[2004-08-13 00:54:28] loye dot young at iycc dot net
I'm having the same error message in my apache log file, with similar
configuration. However, my php.ini settings allow unlimited persistent
connections, and my configuration for mysql does not include a limit on
the number of persistent connections.
My configuration:
apache 2.0.49
php 4.3.8
mysql 4.0.18
WinXP SP1 with latest WinUpdates
The application that I'm invoking is phpWebSite 0.9.3-3.
Loye Young
www.iycc.us
------------------------------------------------------------------------
[2004-07-23 15:46:53] super_freax at hotmail dot com
It says in the PHP-manual for child operations that :
This means that for every child that opened a persistent connection
will have its own open persistent connection to the server. For
example, if you had 20 different child processes that ran a script that
made a persistent connection to your SQL server, you'd have 20 different
connections to the SQL server, one from each child.
Note, however, that this can have some drawbacks if you are using a
database with connection limits that are exceeded by persistent child
connections. If your database has a limit of 16 simultaneous
connections, and in the course of a busy server session, 17 child
threads attempt to connect, one will not be able to. If there are bugs
in your scripts which do not allow the connections to shut down (such
as infinite loops), the database with only 16 connections may be
rapidly swamped
======
So it might be the database that has no more connections left ?
My config is :
WinXPProSP1 (NTFS Formatted)
Apache version 2.0.49
MySQL 4.0.18 with MyODBC 3.51 and winMYSQLadmin 1.4
PHP 4.3.6 with Pear 1.3.1 ,Smarty 2.5.0 ,Zend Opt. 2.5.0 , Dbg 2.16.3,
TCL 8.4.5 with TK 8.4 and Vtcl 1.6.0
------------------------------------------------------------------------
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/26771
--
Edit this bug report at http://bugs.php.net/?id=26771&edit=1
