Hello everyone,
After upgrading from secureweb-3.1-1 to 3.1-2, I get this
during startup:
Starting httpsd: [Sat Jan 22 21:08:52 2000] [warn] Loaded DSO
modules/mod_php.so uses plain Apache 1.3 API, this module might crash under
EAPI! (please recompile it with -DEAPI)
[Sat Jan 22 21:08:52 2000] [warn] Loaded DSO modules/libphp3.so uses plain
Apache 1.3 API, this module might crash under EAPI! (please recompile it
with -DEAPI)
[Sat Jan 22 21:08:55 2000] [warn] Loaded DSO modules/libperl.so uses plain
Apache 1.3 API, this module might crash under EAPI! (please recompile it
with -DEAPI)
[Sat Jan 22 21:08:55 2000] [warn] Loaded DSO modules/mod_jserv.so uses
plain Apache 1.3 API, this module might crash under EAPI! (please recompile
it with -DEAP
I)
[ OK ]
Well, it runs... I checked everything and it seems to work fine
but its really scary to see those messages.. Any idea what went wrong?
I even tried loading the modules from a different box that successfully
upgraded.
The box is a RedHat 6.1 system that had secure server 3.0,
upgraded to 3.1 and now the rhmask patch.
TIA,
Carl
http://www.carlc.com/
Troy Miller
2000-Jan-23 02:39 UTC
Re: Upgrading from SecureServer 3.1-1 to 3.1-2 problems...
Hi, I have the same thing happening. Worked without any report of error in 3.1-1 but now get the same error you mention. Everything is working fine with me as well....but who knows. At learst we''re in the same boat. :-) Troy tmiller@ccsd.net "Carl C." wrote:> Hello everyone, > > After upgrading from secureweb-3.1-1 to 3.1-2, I get this > during startup: > > Starting httpsd: [Sat Jan 22 21:08:52 2000] [warn] Loaded DSO > modules/mod_php.so uses plain Apache 1.3 API, this module might crash under > EAPI! (please recompile it with -DEAPI) > [Sat Jan 22 21:08:52 2000] [warn] Loaded DSO modules/libphp3.so uses plain > Apache 1.3 API, this module might crash under EAPI! (please recompile it > with -DEAPI) > [Sat Jan 22 21:08:55 2000] [warn] Loaded DSO modules/libperl.so uses plain > Apache 1.3 API, this module might crash under EAPI! (please recompile it > with -DEAPI) > [Sat Jan 22 21:08:55 2000] [warn] Loaded DSO modules/mod_jserv.so uses > plain Apache 1.3 API, this module might crash under EAPI! (please recompile > it with -DEAP > I) > [ OK ] > > Well, it runs... I checked everything and it seems to work fine > but its really scary to see those messages.. Any idea what went wrong? > I even tried loading the modules from a different box that successfully > upgraded. > > The box is a RedHat 6.1 system that had secure server 3.0, > upgraded to 3.1 and now the rhmask patch. > > TIA, > Carl > http://www.carlc.com/ > > -- > PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES! > http://www.redhat.com http://archive.redhat.com > To unsubscribe: mail redhat-secure-server-request@redhat.com with > "unsubscribe" as the Subject.
pbrown@redhat.com
2000-Jan-24 17:33 UTC
Re: Upgrading from SecureServer 3.1-1 to 3.1-2 problems...
On Sat, 22 Jan 2000, Troy Miller wrote:> Hi, > > I have the same thing happening. Worked without any report of error > in 3.1-1 but now get the same error you mention. Everything is > working fine with me as well....but who knows.It is a warning, not an error. You may ignore it. It simply means the modules were compiled for a non-SSL-enabled version of Apache. If the modules do not use any SSL functionality, there will be no problem. --- Preston Brown Systems Engineer pbrown@redhat.com Red Hat, Inc.
At 12:33 PM 1/24/00 -0500, you wrote:>On Sat, 22 Jan 2000, Troy Miller wrote: > >> Hi, >> >> I have the same thing happening. Worked without any report of error >> in 3.1-1 but now get the same error you mention. Everything is >> working fine with me as well....but who knows. > >It is a warning, not an error. You may ignore it. >It simply means the modules were compiled for a non-SSL-enabled version >of Apache. If the modules do not use any SSL functionality, there will >be no problem.Preston, Huhhhh, what if they are used under SSL... How do I fix this? Thanks! Carl http://www.carlc.com/ "Price, Performance, Quality. Choose any two you like."
pbrown@redhat.com
2000-Jan-24 19:27 UTC
Re: Upgrading from SecureServer 3.1-1 to 3.1-2 problems...
On Mon, 24 Jan 2000, Carl C. wrote:> >It is a warning, not an error. You may ignore it. > >It simply means the modules were compiled for a non-SSL-enabled version > >of Apache. If the modules do not use any SSL functionality, there will > >be no problem. > > Preston, > > Huhhhh, what if they are used under SSL... How do I fix this?No problem. It is only if the modules actually MAKE USE of the SSL functionality (i.e. call SSL functions) that you may have problems. --- Preston Brown Systems Engineer pbrown@redhat.com Red Hat, Inc.
At 02:27 PM 1/24/00 -0500, you wrote:>On Mon, 24 Jan 2000, Carl C. wrote: > >> >It is a warning, not an error. You may ignore it. >> >It simply means the modules were compiled for a non-SSL-enabled version >> >of Apache. If the modules do not use any SSL functionality, there will >> >be no problem. >> >> Preston, >> >> Huhhhh, what if they are used under SSL... How do I fix this? > >No problem. > >It is only if the modules actually MAKE USE of the SSL functionality (i.e. >call SSL functions) that you may have problems.Preston, I understand, No, they are not calling SSL function. Therefor, it can be safely ignored. Also, many thanks for your hard work here in the Redhat Secure server list. I''ve been a lurker for some time and appreaciate the professional way you and Redhat have been to the community. Carl http://www.carlc.com/ "Price, Performance, Quality. Choose any two you like."