-- forwarded message --
From: [EMAIL PROTECTED] ("Khimenko Victor")
Subject: Re: httpd core dumping
Date: 30 Sep 1998 00:25:18 +0200
Message-ID: <[EMAIL PROTECTED]>
29-Sep-98 08:01 you wrote:
> On Tue, Sep 29, 1998, Khimenko Victor wrote:
>> > AddModule mod_ssl.c
>> > AddModule mod_perl.c
>>
>> > in http.conf (this is the default order). But when I switch these
>> > two lines, everything works fine!
>>
>> See my postings in mod_ssl about mod_perl :-)) This is error in mod_perl, not
>> in mod_ssl :-))
>>[...]
> Ok, that's also what I think, because in mod_ssl 2.0 (the stable branch) the
> mod_ssl.c code didn't change in the last versions. But the question now is:
> How can we help Doug MacEachern to fix this problem for mod_perl 1.15_02? I
> think those of you who discovered the problem should post as much details as
> possible to the mod_perl mailing list (or directly to [EMAIL PROTECTED] if
> you're not subscribed to the mod_perl ML), so Doug has a chance to fix it.
Ok. What I'm know just now: when you have mod_ssl or mod_jserv (both modules
will try to spawn child process (ssl_gcache for mod_ssl, java interpreten for
mod_jserv) in INITIALIZATION phase) now you MUST use the following order:
-- cut --
AddModule mod_perl.c
AddModule mod_jserv.c
AddModule mod_ssl.c
-- cut --
I.e. you must add AddModule for such modules AFTER mod_perl.c. If you'll try
to do this other way (i.e. mod_perl.c added after mod_ssl.c or mod_jserv.c in
httpd.conf) apache will work just fine except core dump somewhere in child
creation process (in ap_run_cleanup AFAIK but I'm not 100% sure about this
while I'm sure that this is AFTER fork but before exec)... Apache 1.3.1 with
mod_perl 1.15 works Ok...
P.S. And of course apache will be unable to create https connections and will
be unable to run servlets due lack of working ssl_gcache and/or JServ :-))
P.P.S. In my case this was apache+mod_ssl and mod_jserv/mod_perl compiled
as DSO (via apxs) under bot RedHat 5.1 and KSI-Linux 2.0beta but looks like
this problem is not related to DSO... May be this problem is related to Linux
and/or glibc ?
-- end of forwarded message --
This is a very strange problem. It seems to be platform dependent because I
couldn't reproducde it neither on my FreeBSD nor my Solaris boxes. So, I've
to move it into the BugDB as suspended to not forget it. Let's hope Doug or
others find out more in the future or newer mod_perl releases solve it...
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]
