php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login

go to bug id or search bugs for

Bug #35446 Apache2 2.0.55 child restarts if ErrorDocument is used
Submitted: 2005-11-28 13:50 UTC Modified: 2005-11-28 18:35 UTC
From: jrivett at uvic dot ca Assigned:
Status: Not a bug Package: Apache2 related
PHP Version: 4.4.1 OS: Windows 2000 SP4
Private report: No CVE-ID: None
View Add Comment Developer Edit
 [2005-11-28 13:50 UTC] jrivett at uvic dot ca 
Description:
------------
Upgraded PHP from 4.4.0 to 4.4.1 on Nov 3/05 and immediately started seeing these in the Apache error log:
"[notice] Parent: child process exited with status 3221225477 -- Restarting."  Every time this happens the server becomes unresponsive for a while.  The trigger is when a client tries to browse to a page that doesn't exist: 
"[error] [client xxx.xxx.xxx.xxx] File does not exist: D:/htdocs/public/hownote".  We use a custom error 404 page, configured using Apache's ErrorDocument directive.  The page contains PHP code.  Commenting out the ErrorDocument directive resolves the problem.

Bug #35056 looks like the same problem, but it was reported in PHP 4.4.1RC1, fixed in CVS and supposedly fixed in 4.4.1.
Bug #33987 looks like the same problem as well but it was reported on PHP 5.1.
Bug #21074 is similar.


Reproduce code:
---------------
<?php
require ($_SERVER["DOCUMENT_ROOT"]."/includes/functions.php");
$print_home_link = true;
print_header ();
?>

<!-- user message here -->

<?php
	print_footer();
?>

URL: http://helpdesk.uvic.ca

Expected result:
----------------
The custom error 404 page should appear on the client.  Apache should not restart.

Actual result:
--------------
On the client end, the session usually appears to hang.  In any case, the error 404 page does not appear.  On the server end, about every other instance causes the child to restart.

Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2005-11-28 14:52 UTC] sniper@php.net 
Please try using this CVS snapshot:

  http://snaps.php.net/php5-latest.tar.gz
 
For Windows:
 
  http://snaps.php.net/win32/php5-win32-latest.zip
 [2005-11-28 17:59 UTC] jrivett at uvic dot ca 
Thanks for the response.  Unfortunately, I'm running 4.4.x and am not in a position to upgrade to 5.x right now.  If the only fix is to upgrade to 5.x, does that mean that 4.4.x is no longer being supported?  How likely is it that 4.4.1 will get the fix for this problem that's apparently in the 5.x CVS you pointed to?
 [2005-11-28 18:00 UTC] iliaa@php.net 
The issue is resolved in 5.1.1 and 4.4.2-cvs, snapshot of which is available from http://snaps.php.net
 [2005-11-28 18:30 UTC] jrivett at uvic dot ca 
Okay, I'll take a look at 4.4.2-cvs.  However, I'm unwilling to put a CVS version onto a production system, so I guess I'll just have to wait for the fix in the release version of 4.4.2.

One other thing: I did search for this issue in the bug database and although I did find similar ones, I found nothing related to the particular version of PHP I'm using: 4.4.1.  I see that you've flagged this issue as "Bogus" which I understand, but what happens when someone else running 4.4.1 has this problem?  If their searches only find the bugs I found (different version) then this was wasted effort.  If they find *this* bug, they may be distracted by the "Bogus" status.  Is there some way to leave things so that the next person in my position doesn't just do the same things over again?
 [2005-11-28 18:35 UTC] iliaa@php.net 
I marked it bogus since this is a duplicate of the original bug report. If you don't want to get the cvs version, there is 4.4.2RC1 available from http://qa.php.net/
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved. 		Last updated: Fri May 17 03:01:32 2024 UTC