Ralf, FYI: I've seen lots of problems with the Slackware 4.0 DBM
library. It worked for a while sometime between Slackware 3.6 and
Slackware 4.0 in slackware-current, but Slackware 4.0's library seems to
be broken again. I had the same problem as Charles... MM works nicely
(and much faster, of course ;> ). I notice there's already a FAQ on
this (which has a couple of typos, BTW), but maybe the FAQ should
include a list of distros that have been known to have problems. That
way, a search through the FAQ for, say "Slackware," would turn up the
segfault problem for DBM session caching. Thoughts? Would this be too
hard to maintain/keep track of?
-Cliff
<<< "Ralf S. Engelschall" <[EMAIL PROTECTED]> 8/10 6:31a >>>
On Mon, Aug 09, 1999, Charles Tassell wrote:
> My Apache 1.3.6 with mod_ssl 2.3.9 has suddenly started to core dump
on
> any secure connection (non-secure connections work fine) I did an
strace
> on one of the processes, and have attached the output. Does anyone
have
> any ideas as to what could be wrong? I'm running SlackWare Linux 4.0
with
> a custom 2.2.10 kernel, and I compiled Apache/mod_ssl myself (method 2
of
> the mod_ssl install instructions, with OpenSSL 0.9.3a and mm 1.0.9)
You say, you've built with MM, but it looks like you're _running_ with a
DBM-based session cache. And it seems like your DBM database got
corrupted and
this way the DBM library gets crazy. You should upgrade to 2.3.11, use
at
least --enable-rule=SSL_SDBM and even better use the shared memory
session
cache.
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
