On Fri, Jan 15, 1999, Taylor Blackwell wrote:
> I'm having trouble getting mod_ssl working in a fresh stock copy of
> Apache 1.3.4 on a Slackware 3.6 box with Linux 2.0.36. I followed the
> instructions verbatim, and now, when running the server, odd things are
> afoot...
>
> For one, I can access the server at port 80, unsecured, just fine.
> However, when I go to the secure port on 443, I get the key, asked if I
> want to accept something from such a seethy corporation, and once I say
> yes, error_log says...
>
> httpd: [Thu Jan 14 19:49:10 1999] [notice] child pid 108 exit signal
> Segmentation fault (11)
> httpd: [Thu Jan 14 19:49:10 1999] [notice] child pid 107 exit signal
> Segmentation fault (11)
>
> Did I miss something here? I read a bunch of archives, and tried double
> checking my modules, etc. Since this is stock apache, it wasn't hard. I
> have fresh distributions of all sources, and am pretty good at following
> instructions, usually. *cough*
>
> ideas, suggestions, fruit?
When you built with DSO (--enable-shared=ssl) this is because of subtle bugs
in hook registering. When you built without DSO this is something else. Can
you provide us with a backtrace, so we can see where exactly it segfaults?
Look inside the mod_ssl FAQ under debugging for details on how to create such
a backtrace.
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/
Official Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
