ID: 21987 Updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] -Status: Open +Status: Feedback Bug Type: Apache related Operating System: Openbsd 3.2 PHP Version: 4.3.0 New Comment:
Thank you for this bug report. To properly diagnose the problem, we need a backtrace to see what is happening behind the scenes. To find out how to generate a backtrace, please read http://bugs.php.net/bugs-generating-backtrace.php Once you have generated a backtrace, please submit it to this bug report and change the status back to "Open". Thank you for helping us make PHP better. Previous Comments: ------------------------------------------------------------------------ [2003-02-03 08:43:17] [EMAIL PROTECTED] yes it's the same openssl and you are right i didn't end up doing a restart i did a killall httpd and then a startssl ------------------------------------------------------------------------ [2003-02-03 06:52:29] [EMAIL PROTECTED] And DO NOT do 'apachctl restart' after you have installed new PHP module!! ------------------------------------------------------------------------ [2003-02-03 06:51:49] [EMAIL PROTECTED] Are you sure you're linking PHP with exactly SAME openssl libs as you have linked Apache with? ------------------------------------------------------------------------ [2003-02-01 09:43:36] [EMAIL PROTECTED] this behavior only occurs when compiling: --with-openssl unless you propose the bug is w/ openbsd's openssl, however be advised my mod_ssl is compiled with it and it suffers no issues. -quel ------------------------------------------------------------------------ [2003-01-31 16:29:43] [EMAIL PROTECTED] Sorry, but your problem does not imply a bug in PHP itself. For a list of more appropriate places to ask for help using PHP, please visit http://www.php.net/support.php as this bug system is not the appropriate forum for asking support questions. Thank you for your interest in PHP. Given the provided information there is nothing to indicate that it is PHP who is responsible for the broken configuration. If you want you could try compiling PHP with --enable-debug, which may make the backtrace more meaningful if it is indeed PHP who is responsible for the problem. ------------------------------------------------------------------------ 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/21987 -- Edit this bug report at http://bugs.php.net/?id=21987&edit=1
