#23942 [Fbk->Opn]: php 4.3.x causes apache2+mod_ssl to sigsev on client authentication

ID: 23942 User updated by: alextxm at tin dot it Reported By: alextxm at tin dot it -Status: Feedback +Status: Open Bug Type: Apache2 related Operating System: Linux PHP Version: 4.3.2 New Comment: i'm doing some more tests... an interesting thing: on Redhat 9.0 it works fine (openssl 0.9.7a, php 4.2.2, apache 2.0.40 - both stock versions) . I'm trying to figure out where the problem is. I'll let you know, probaly there is something in my setup which causes php or apache to behave strangely. alessandro Previous Comments: ------------------------------------------------------------------------ [2003-06-11 11:28:03] sniper@php.net Try reduce the configure options to the bare minimum first. Then if you don't get any segfaults, try every excluded option one by one to see which one is causing this. And for the backtrace you just need to keep pressing 'enter' until it gets there..the first couple of screens gdb is loading the symbols from every linked library, you can ignore it.. ------------------------------------------------------------------------ [2003-06-02 13:21:38] sniper@php.net No, don't change the MPM. And yes, you will get a backtrace always, it's not really PHP related thing. # gdb httpd (gdb) run -X -DSSL ..then access the page causing the crash.. (gdb) bt ------------------------------------------------------------------------ [2003-06-02 13:00:59] alextxm at tin dot it I did some more tests: - enabling your suggested configure cleanups didn't help (=the problem is still there)...thanks anyway (i was using them since previous 4.2.x release) - tested the same setup with apache 1.3.27+mod_ssl : it works fine with php both enabled and disabled... so it seems to be only confined to apache2+ssl+php - MPM used for apache2 is "prefork" ... should I change it? - php 4.3.1 and 4.3.2 both show the issue i'm going to try to obtain a backtrace using httpd -X with php in debug mode. btw, will this work (=will it produce a backtrace) even if the site is not using any php script at all ? ------------------------------------------------------------------------ [2003-06-02 05:51:35] sniper@php.net Your configure line contains couple of options that are really unnecessary, for example these: -with-db (use --enable-dba) --enable-versioning (Only needed if you have php3 installed too and that doesn't support Apache2, so..) --enable-track-vars (doesn't exist), --enable-inline-optimization (might cause problems) --without-readline (not enabled by default anyway) --disable-posix-threads (why?) --enable-force-cgi-redirect (Only used for CGI build) --enable-discard-path (Only used for CGI builds) And what MPM is used for Apache2? Remove those options mentioned above + --enable-debug and try again. ("rm -f config.cache" first!) If it still crashes, provide the backtrace. ------------------------------------------------------------------------ [2003-06-02 03:51:19] alextxm at tin dot it yes i'm sure they use the same openssl library since i've complied both openssl, apache2 and php from source. configure for mod_php (php as apache DSO module) : ./configure --without-readline --with-pam --with-openssl -with-gdbm=/usr --with-mysql=/usr --with-gd=/usr --with-pspell --with-tiff-dir=/usr --with-jpeg-dir=/usr --with-pdflib=/usr --with-ttf --with-t1lib --with-zlib --with-zlib-dir=/usr/lib --with-exec-dir=/usr/bin --with-apxs2=/usr/sbin/apxs2 --with-imap --with-imap-ssl --with-mcrypt --with-mhash --disable-posix-threads --with-java=/opt/sun-jdk-1.4.1.02 --prefix=/usr --with-bz2 --enable-ftp --enable-force-cgi-redirect --enable-discard-path --enable-mime-magic --enable-wddx --enable-dbase --with-zlib=yes --with-iconv --enable-bcmath --enable-sysvsem --enable-exif --enable-sysvshm --enable-sockets --enable-calendar --enable-trans-sid --enable-safe-mode --enable-versioning --enable-track-vars --enable-inline-optimization --with-config-file-path=/etc/php4 --with-sablot=/usr --enable-xslt --with-xslt-sablot --with-xmlrpc --with-gettext -with-db=/usr ------------------------------------------------------------------------ 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/23942 -- Edit this bug report at http://bugs.php.net/?id=23942&edit=1