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

From: Date: Mon, 09 Jun 2003 13:26:04 +0000
Subject: #23942 [Opn]: php 4.3.x causes apache2+mod_ssl to sigsev on client authentication
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-41515@lists.php.net to get a copy of this message
ID: 23942 User updated by: alextxm at tin dot it Reported By: alextxm at tin dot it Status: Open Bug Type: Apache2 related Operating System: Linux PHP Version: 4.3.2 New Comment: I did some more tests but i'm still unable to obtain a backtrace. I tried : gdb /usr/sbin/apache2 gdb> run -X -D SSL -D PHP output is: Starting program: /usr/sbin/apache2 -X -D PHP -D SSL (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...[New Thread 1024 (LWP 24998)] (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... ---Type <return> to continue, or q <return> to quit--- is there something i forgot? can you please help me obtaining the bt? I think it would be really helpful having something to work on for this bug. I'm available for any kind of operation aimed to obtain the bt or anything else you would need for inevstigating this bug alessandro Previous Comments: ------------------------------------------------------------------------ [2003-06-02 14:33:28] alextxm at tin dot it i'm having problems trying to obtain the bt: i get a lot of "(no debugging symbols found)...(no debugging symbols found)..." messages and when it works (it usually gives me an "Unable to contact site sitename" error in the browser), i get no bt all (even if I ask for a bt) but a message like: LWP thread 26404 ended with error 1 any idea? btw please note that i'm now going to move the whole thing on a new server (where i can try to obtain bt and all what you could need) since the current one is a production one and so I can't shut down it for tests for a long time... ------------------------------------------------------------------------ [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

« previous php.bugs (#41515) next »