On Thu, Nov 19, 1998, Anthony Rumble wrote:
> OK.. first.. using the Bog standard apache/1.3.3 with modperl/1.15 that
> comes with RedHat 5.2.. (also using a cookie based authentication module)
> works fine.. no problems..
>
> Thu Nov 19 00:44:06 1998] [notice] Apache/1.3.3 (Unix) (Red Hat/Linux)
> mod_perl/1.15 configured -- resuming normal operations
>
> No problems..
>
> I took the RH 5.2 SRPMS and hacked in the mod_ssl configure and build..
>
> and with the same setup except now compiled with mod_ssl... I get :-
>
> [Thu Nov 19 00:29:13 1998] [notice] Apache/1.3.3 (Unix) (Red Hat/Linux)
> mod_ssl/2.1.0 SSLeay/0.9.0b mod_perl/1.15 configured -- resuming normal
> operations
>
> [Thu Nov 19 00:31:33 1998] [notice] httpd: child pid 22158 exit signal
> Segmentation fault (11)
> [Thu Nov 19 00:31:34 1998] [notice] httpd: child pid 22152 exit signal
> Segmentation fault (11)
> [Thu Nov 19 00:31:41 1998] [notice] httpd: child pid 22182 exit signal
> Segmentation fault (11)
> [Thu Nov 19 00:31:44 1998] [notice] httpd: child pid 22188 exit signal
> Segmentation fault (11)
>
> These happen when I execute my mod_perl programs..
> There is some particular behaviour attached.. I have set my Max servers to
> 2 (for development this makes sense)..
>
> And I dont see the Seg Faults till I execute at least two scripts (using
> both the httpds).. then I get two seg fault messages in a row..
>
> BTW.. Not loading the libssl.so and turning off all the SSL stuff makes no
> difference..
Makes no difference? You mean when libssl.so is not loaded httpd still
segfaults? Then the problem cannot be directly inside mod_ssl. Then it's
perhaps related to the Extended API or even to a problem between mod_perl and
the EAPI? Make sure mod_perl is compiled with -DEAPI, too! Else you get
segfaults, of course.
> Know where I can start looking?
You have to re-compile all parts with LDFLAGS="-g -ggdb3" and after getting
the core dumps you have to inspect them with gdb and using "bt" (backtrace) to
find out at which location in the source it segfaults.
OTOH your setup is very complicated (partly SRPMS, additional modules, mod_ssl
added manually, etc.pp), so I would generally recommend you to don't try all
thing this way. Instead I would start with fresh apache_1.3.3.tar.gz,
mod_perl-1.16.tar.gz and mod_ssl-2.1.0-1.3.3.tar.gz tarballs and follow the
mod_ssl INSTALL file _very closely_. When it then doesn't run it's easier to
find the problem. When it runs it's easy to switch over to your RPM-based
stuff with more features.
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]
