Rei,

I believe the Slackware 3.6 dist has a buggy DBM library. I tried
compiling the same thing on another box and I get the same thing. Try
using this setting:

SSLSessionCache None

This seems to help. Or you can try recompiling Apache_SSL using the
internal DBM library by setting this option during the 'configure' of
mod_ssl:

--enable-rule=SSL_SDBM

Z

On Fri, 21 May 1999, Rei Yoshioka wrote:

> >To make a long story short, had a crash on one of my webservers and had
> >to rebuild the machine.  It was using apache_1.3.4+mod_ssl-2.2(?, sorry
> >don't remeber)+openssl-0.9.2b+php-3.0.7 on Linux 2.0.33.  This was the
> >machine that my key and crt request were created on and mod_ssl with the
> >server.crt had run for months on without problem.  I had backups of all
> >the date but still had to recreate the machine.
> >
> >The new machine is the following and also uses the original server.crt
> >and server.key files
> >
> >apache_1.3.6+mod_ssl-2.2.6+openssl-0.9.2b+php-3.0.7 on Linux 2.0.35.
> >
> >
> >When I startup the server I can do a few https transactions, but every
> >time I click a link three of these appear in the log file.
> >
> >Child pid exit signal Segmentation fault (11)
> >
> >At this point I shutdown the server, when I restart it http works but
> >https returns a "server returned bad data error."
> >
> >The compiles had no error, I've also tried to compile several older
> >version combinations.  Include one with SSLeay, but I always get the
> >same results.
> >
> >Thank you for your time.
> >
> >Shane Wilson
> >Centre College
> 
> I get the same symptoms with a Slackware 3.6 setup (sorry for the "me 
> too" post, but I'm not using any other modules like php so there's 
> one tiny tidbit of new info):
> 
> ---
> 
> Apache 1.3.6 + mod_ssl-2.2.7 (tried older versions too) + 
> openssl-0.9.2b + Linux 2.0.35
> 
>  From error_log right after apachectl startssl:
> 
> [Fri May 21 21:17:17 1999] [notice] Apache/1.3.6 (Unix) mod_ssl/2.2.7 
> OpenSSL/0.9.2b configured -- resuming normal operations
> [Fri May 21 21:17:21 1999] [notice] child pid 2236 exit signal 
> Segmentation fault (11)
> [Fri May 21 21:17:25 1999] [notice] child pid 2237 exit signal 
> Segmentation fault (11)
> [Fri May 21 21:17:33 1999] [notice] child pid 2239 exit signal 
> Segmentation fault (11)
> 
> ---
> 
> Apache 1.3.6 + mod_ssl-2.2.8-1.3.6 + openssl-0.9.2b (and with or w/o 
> rsaref, and with or without mm) + Linux 2.0.35.
> 
>  From error_log right after apachectl startssl:
> 
> [Fri May 21 21:20:26 1999] [notice] Apache/1.3.6 (Unix) mod_ssl/2.2.8 
> OpenSSL/0.9.2b configured -- resuming normal operations
> [Fri May 21 21:20:33 1999] [notice] child pid 2354 exit signal 
> Segmentation fault (11)
> 
> ---
> 
> I have tried with the default "snake oil" server cert/key created 
> during the build, and also with a real Thawte cert.
> 
>  From the browser point of view (either Mac or WindowsNT versions of 
> IE or Netscape), I can get to any http page no problem.  But if I use 
> https, then the index page will show with broken graphics (cant load 
> the graphics), and I cannot get to anything in sub-directories 
> without getting various "Security Error. Data Decryption error" or 
> "bad data error" messages.
> 
> I checked to see if Dave Paris' recent posting regarding ndbm.h 
> applied to Slackware but it does not seem to apply here for Slackware 
> release.
> 
> Any ideas of things to try, or steps to debug this further to isolate 
> the problem?
> 
> -Rei
> 
> ______________________________________________________________________
> Apache Interface to OpenSSL (mod_ssl)                   www.modssl.org
> User Support Mailing List                      [EMAIL PROTECTED]
> Automated List Manager                            [EMAIL PROTECTED]
> 

--
Zivago 'Jaeman' Lee
[EMAIL PROTECTED]
--



______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl)                   www.modssl.org
User Support Mailing List                      [EMAIL PROTECTED]
Automated List Manager                            [EMAIL PROTECTED]

Reply via email to