Bug#385004: Info received (apache-ssl: I get this too)
Philip Craig a écrit : it seemed to be the apache.pem key cert. Not the config files. Andreas Barth wrote: Hi, * Philip Craig ([EMAIL PROTECTED]) [060830 10:43]: I have more info. I did a stack trace with apache-ssl.dbg built from source, and it was crashing in libssl. i test 'apache-ssl.dbg -FX' with gdb and the backtrace reports a segfault when loading php5 module. if i comment this module in modules.conf, it works this is the backtrace: #0 0xb7b98947 in raise () from /lib/tls/libc.so.6 #1 0xb7b9a0c9 in abort () from /lib/tls/libc.so.6 #2 0xb7bcdfda in __fsetlocking () from /lib/tls/libc.so.6 #3 0xb7bd589f in mallopt () from /lib/tls/libc.so.6 #4 0xb7bd5942 in free () from /lib/tls/libc.so.6 #5 0xb7f17de8 in __os_free () from /usr/lib/libdb-4.4.so #6 0xb7e5ed3b in __bam_db_close () from /usr/lib/libdb-4.4.so #7 0xb7ec0a7c in __db_refresh () from /usr/lib/libdb-4.4.so #8 0xb7ec10b9 in __db_close () from /usr/lib/libdb-4.4.so #9 0xb7ece177 in __db_close_pp () from /usr/lib/libdb-4.4.so #10 0xb713677f in _nss_db_getspnam_r () from /usr/lib/libnss_db.so.2 #11 0xb7136818 in _nss_db_getspnam_r () from /usr/lib/libnss_db.so.2 #12 0xb7135276 in _nss_db_endprotoent () from /usr/lib/libnss_db.so.2 #13 0xb713548e in _nss_db_getprotobyname_r () from /usr/lib/libnss_db.so.2 #14 0xb7c52beb in getprotobyname_r () from /lib/tls/libc.so.6 #15 0xb7c52aaa in getprotobyname () from /lib/tls/libc.so.6 #16 0xb77ad913 in zm_startup_sockets () from /usr/lib/apache/1.3/libphp5.so #17 0xb7892d5c in zend_startup_module_ex () from /usr/lib/apache/1.3/libphp5.so #18 0xb78991ad in zend_hash_apply () from /usr/lib/apache/1.3/libphp5.so #19 0xb78933ed in zend_startup_modules () from /usr/lib/apache/1.3/libphp5.so #20 0xb784ee63 in php_module_startup () from /usr/lib/apache/1.3/libphp5.so #21 0xb7912240 in apache_php_module_main () from /usr/lib/apache/1.3/libphp5.so #22 0xb79124ed in apache_php_module_main () from /usr/lib/apache/1.3/libphp5.so #23 0x080552d3 in ap_init_modules (p=0x8090024, s=0x809005c) at http_config.c:1710 #24 0x08062053 in main (argc=2, argv=0xbfdcd9d4) at http_main.c:5798 sylvain smime.p7s Description: S/MIME Cryptographic Signature
Bug#385004: Info received (apache-ssl: I get this too)
reassign 385004 openssl,apache-ssl * Philip Craig ([EMAIL PROTECTED]) [060918 14:57]: > it seemed to be the apache.pem key cert. Not the config files. Hm, that is a bit bad with sharing. But then, it sounds like it is a bug in the ssl-part. I reassigned the bug as well to openssl. Cheers, Andi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#385004: Info received (apache-ssl: I get this too)
Hi, * Philip Craig ([EMAIL PROTECTED]) [060830 10:43]: > I have more info. I did a stack trace with apache-ssl.dbg built from > source, and it was crashing in libssl. > > But this didn't help. > > What *did* help was totally purging the apache-ssl package, deleting the > /etc/apache-ssl directory, and reinstalling. It now works fine. > > Another theory is that possibly just forcing a regeneration of the certs > would also have worked. in this case, are the not working configuration files available? (Or best, can you try which file fails by comparing the not working and the working set ups, and replacing file by file)? Cheers, Andi -- http://home.arcor.de/andreas-barth/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#385004: Info received (apache-ssl: I get this too)
it seemed to be the apache.pem key cert. Not the config files. Andreas Barth wrote: Hi, * Philip Craig ([EMAIL PROTECTED]) [060830 10:43]: I have more info. I did a stack trace with apache-ssl.dbg built from source, and it was crashing in libssl. But this didn't help. What *did* help was totally purging the apache-ssl package, deleting the /etc/apache-ssl directory, and reinstalling. It now works fine. Another theory is that possibly just forcing a regeneration of the certs would also have worked. in this case, are the not working configuration files available? (Or best, can you try which file fails by comparing the not working and the working set ups, and replacing file by file)? Cheers, Andi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#385004: Info received (apache-ssl: I get this too)
I have more info. I did a stack trace with apache-ssl.dbg built from source, and it was crashing in libssl. But this didn't help. What *did* help was totally purging the apache-ssl package, deleting the /etc/apache-ssl directory, and reinstalling. It now works fine. Another theory is that possibly just forcing a regeneration of the certs would also have worked. Philip Craig wrote: I have now built and installed apache-ssl and apache-common from source using the previous version in testing, 1.34-2. This still fails with the same error, so I guess it must actually be a bug in a dependency? As apache is fine, I guess it may be some ssl dependency. Any ideas what this could be? I am drawing a blank as I haven't actually got new versions of openssl, ssl-cert or libssl0.9.8 for months, so I do not know what dependency has produced this issue. Debian Bug Tracking System wrote: Thank you for the additional information you have supplied regarding this problem report. It has been forwarded to the package maintainer(s) and to other interested parties to accompany the original report. Your message has been sent to the package maintainer(s): Debian Apache Maintainers If you wish to continue to submit further information on this problem, please send it to [EMAIL PROTECTED], as before. Please do not reply to the address at the top of this message, unless you wish to report a problem with the Bug-tracking system. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#385004: Info received (apache-ssl: I get this too)
I have now built and installed apache-ssl and apache-common from source using the previous version in testing, 1.34-2. This still fails with the same error, so I guess it must actually be a bug in a dependency? As apache is fine, I guess it may be some ssl dependency. Any ideas what this could be? I am drawing a blank as I haven't actually got new versions of openssl, ssl-cert or libssl0.9.8 for months, so I do not know what dependency has produced this issue. Debian Bug Tracking System wrote: Thank you for the additional information you have supplied regarding this problem report. It has been forwarded to the package maintainer(s) and to other interested parties to accompany the original report. Your message has been sent to the package maintainer(s): Debian Apache Maintainers If you wish to continue to submit further information on this problem, please send it to [EMAIL PROTECTED], as before. Please do not reply to the address at the top of this message, unless you wish to report a problem with the Bug-tracking system. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
