You are viewing a plain text version of this content. The canonical link for it is here.
Posted to bugs@httpd.apache.org by bu...@apache.org on 2012/04/05 16:15:17 UTC
DO NOT REPLY [Bug 53038] New: Crash in mod_ssl
https://issues.apache.org/bugzilla/show_bug.cgi?id=53038
Bug #: 53038
Summary: Crash in mod_ssl
Product: Apache httpd-2
Version: 2.3.11-beta
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: mod_ssl
AssignedTo: bugs@httpd.apache.org
ReportedBy: silviu.andrica@gmail.com
Classification: Unclassified
Created attachment 28546
--> https://issues.apache.org/bugzilla/attachment.cgi?id=28546
The httpd configuration file
Hi,
the bug refers to Apache httpd 2.3.4, not 2.3.11.
When running httpd 2.3.4, I get in the error log the following backtrace:
*** glibc detected *** /usr/local/apache2.3/bin/httpd: free(): invalid pointer:
0x00007fcf8c000078 ***
======= Backtrace: =========
/lib/x86_64-linux-gnu/libc.so.6(+0x78a96)[0x7fcfb68c5a96]
/lib/x86_64-linux-gnu/libc.so.6(cfree+0x6c)[0x7fcfb68c9d7c]
/lib/x86_64-linux-gnu/libcrypto.so.1.0.0(CRYPTO_free+0x1d)[0x7fcfad6c4c7d]
/lib/x86_64-linux-gnu/libcrypto.so.1.0.0(EC_GROUP_free+0x2e)[0x7fcfad70147e]
/lib/x86_64-linux-gnu/libcrypto.so.1.0.0(EC_KEY_set_group+0x22)[0x7fcfad70ba62]
/usr/local/apache2.3/modules/mod_ssl.so(+0x15367)[0x7fcfadc7c367]
/lib/x86_64-linux-gnu/libssl.so.1.0.0(+0x11a1b)[0x7fcfada27a1b]
/lib/x86_64-linux-gnu/libssl.so.1.0.0(+0x14710)[0x7fcfada2a710]
/lib/x86_64-linux-gnu/libssl.so.1.0.0(+0x20363)[0x7fcfada36363]
/usr/local/apache2.3/modules/mod_ssl.so(+0x11928)[0x7fcfadc78928]
/usr/local/apache2.3/modules/mod_ssl.so(+0x11edf)[0x7fcfadc78edf]
/usr/local/apache2.3/bin/httpd(ap_rgetline_core+0x85)[0x42e055]
/usr/local/apache2.3/bin/httpd(ap_read_request+0x24e)[0x42fe6e]
/usr/local/apache2.3/bin/httpd[0x4481f2]
/usr/local/apache2.3/bin/httpd(ap_run_process_connection+0x48)[0x443338]
/usr/local/apache2.3/bin/httpd[0x44fd75]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x7efc)[0x7fcfb6e2fefc]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7fcfb692e89d]
The build configuration is the following:
"./configure" \
"--prefix=/usr/local/apache2.3" \
"--with-included-apr" \
"--enable-mods-shared=all ssl cache proxy authn_alias file_cache charset_lite
dav_lock cache_disk" \
"--enable-load-all-modules" \
"--with-mpm=worker" \
The server settings are
Server Version: Apache/2.3.4 (Unix) mod_ssl/2.3.4 OpenSSL/1.0.0e DAV/2
PHP/5.3.10
Server Built: Feb 13 2012 16:06:11
Server loaded APR Version: 1.4.0-dev
Compiled with APR Version: 1.4.0-dev
Server loaded APU Version: 1.4.0-dev
Compiled with APU Version: 1.4.0-dev
Module Magic Number: 20091119:1
Hostname/port: conferr:80
Timeouts: connection: 300 keep-alive: 5
MPM Name: worker
MPM Information: Max Daemons: 1 Threaded: yes Forked: yes
Server Architecture: 64-bit
Server Root: /usr/local/apache2.3/
Config File: /usr/local/apache2.3/conf/httpd.conf
Server Built With: -D APR_HAS_SENDFILE -D APR_HAS_MMAP -D APR_HAVE_IPV6
(IPv4-mapped addresses enabled) -D APR_USE_SYSVSEM_SERIALIZE -D
APR_HAS_OTHER_CHILD -D AP_HAVE_RELIABLE_PIPED_LOGS -D
HTTPD_ROOT="/usr/local/apache2.3" -D
SUEXEC_BIN="/usr/local/apache2.3/bin/suexec" -D
DEFAULT_ERRORLOG="logs/error_log" -D AP_TYPES_CONFIG_FILE="conf/mime.types" -D
SERVER_CONFIG_FILE="conf/httpd.conf"
I attached the configuration file (slightly edited for privacy reasons).
I tried to reproduce the problem in 2.4.1, but did not manage.
Best regards,
Silviu
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org
[Bug 53038] Crash in mod_ssl
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=53038
Stefan Fritsch <sf...@sfritsch.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #1 from Stefan Fritsch <sf...@sfritsch.de> ---
I am pretty sure that this bug has been fixed in 2.4.2 by r1308862
--
You are receiving this mail because:
You are the assignee for the bug.