ID: 34637 User updated by: rtdean at tcamail dot net Reported By: rtdean at tcamail dot net -Status: Feedback +Status: Open Bug Type: Apache related Operating System: FreeBSD 4.11-STABLE PHP Version: 5.0.5 New Comment:
Quick initial tests on my local system show that the problem may be resolved with the current snapshot. I'll do more testing on the production system tomorrow, and see if the changes hold there as well... Previous Comments: ------------------------------------------------------------------------ [2005-09-26 01:41:24] [EMAIL PROTECTED] Please try using this CVS snapshot: http://snaps.php.net/php5-STABLE-latest.tar.gz For Windows: http://snaps.php.net/win32/php5.0-win32-latest.zip ------------------------------------------------------------------------ [2005-09-26 01:32:19] rtdean at tcamail dot net Description: ------------ I'm running apache-1.3.33 with mod_ssl-2.8.24 on FreeBSD 4.11. I've installed this via ports, using no special options. For fun, I built everything by hand as well, and ran into the same issues. I'm in the process of upgrading from running 4.4.0 to 5.0.5. With 4.4.0, everything is working just fine; I can run PHP content in an SSL-enabled vhost. When I upgraded to PHP 5.0.5, when I start apache, it seems to launch okay, but instead crashes and burns. There is no useful information in the log file(s). So, I started some testing. If I start the server without SSL support, everything comes up just fine. Conversely, if I start the server with SSL but without PHP, again, everything is working just fine. Both mod_ssl and PHP5 are linked against the same version of OpenSSL in the same place on disk. Now, interestingly enough, if I reorder the module execution order so the Load/Add directives for SSL come below the directives for PHP, the system will start - and PHP content on non-SSL sites will work just fine. However, any dynamic content on a SSL site, wether it be PHP, CGI, or server-extended (ie, server-info) causes the apache child which is servicing the request to segmentation fault. I'm not sure where the offender is, but I've repeatedly recompiled Apache with mod_ssl and PHP, so it wasn't a one-time compile bug. Looking through the bug history, it looks like #29227 might have been the same issue I'm seeing, but there was no resolution provided. ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=34637&edit=1
