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

go to bug id or search bugs for

Bug #24039 Apache 2.0.46/PHP 4.3.2 continually crashes with segmention fault
Submitted: 2003-06-05 09:53 UTC Modified: 2003-06-11 21:14 UTC
Votes:2
Avg. Score:5.0 ± 0.0
Reproduced:2 of 2 (100.0%)
Same Version:1 (50.0%)
Same OS:0 (0.0%)
From: poulman at wirsbo dot com Assigned:
Status: No Feedback Package: Apache2 related
PHP Version: 4.3.2 OS: SuSE Linux 8.2
Private report: No CVE-ID: None
View Developer Edit
 [2003-06-05 09:53 UTC] poulman at wirsbo dot com 
Recently tried upgrading from Apache 2.0.45/PHP 4.3.1 to Apache 2.0.46/PHP 4.3.2.. everything worked fine with the previous configuration. Upgraded using exact same config parameters in both applications. This is just an initial FYI in case others are experiencing similar issues with this combination. I will work on narrowing down an exact script(s) that may be triggering the failure (segmentation fault).

Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2003-06-05 11:05 UTC] magnus@php.net 
Which MPM are you using ? 
 
Also, a backtrace and/or reproduce script is needed.
 [2003-06-11 19:11 UTC] sniper@php.net 
No feedback was provided. The bug is being suspended because
we assume that you are no longer experiencing the problem.
If this is not the case and you are able to provide the
information that was requested earlier, please do so and
change the status of the bug back to "Open". Thank you.
 [2003-06-11 20:38 UTC] poulman at wirsbo dot com 
At the present time I have reverted back to Apache 2.0.46/PHP 4.3.1 and everything works. I do not have sufficient time or resources at the moment to troubleshoot the Apache 2.0.46/PHP 4.3.2 configuration. Sorry.
 [2003-06-11 21:14 UTC] magnus@php.net 
still not the requested info. Leave as "No Feedback" until 
you can give it.
 [2004-04-13 12:19 UTC] sean_walton at e-nps dot com 
xref: Bug #27980
 [2004-07-23 01:28 UTC] klopp dot geo at yahoo dot com 
I too have seen similar results after upgrading from an earlier version of PHP and apache. Basically what we found was happening was that when we would store large objects in the session it would put the apache process in charge of that script in a constant state of 'sending reply' (we found this out by checking the apache-status screen). After being put into that state the process was riddled useless and apache was forced to create new processes to handle new requests. After several hours of this our apache couldn't create any new processes and our server thus couldn't accept any new connections. After removing all instances of this object from our sessions we found that we were not getting anymore locked apache processes and appeared to have fixed the problem.

BTW we are running php 4.3.2 and apache 2.0.46. Feel free to contact me if you need more information.
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved. 		Last updated: Thu Dec 26 12:01:30 2024 UTC