Bug 8934

Summary:	problem with libperl.so after upgrading to secureweb-3.1-2
Product:	[Retired] Red Hat Secure Web Server	Reporter:	Steevithak <steevithak>
Component:	mod_perl	Assignee:	Preston Brown <pbrown>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	low	Docs Contact:
Priority:	low
Version:	3.1
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2000-01-28 21:54:18 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Steevithak 2000-01-28 03:19:02 UTC

After performing an upgrade to secureweb-3.1-2, a warning is issued each
time the secure server starts as folows:

 [warn] Loaded DSO modules/libperl.so uses plain Apache 1.3 API, this
module might crash under EAPI! (please recompile it with -DEAPI)

This warning did not appear when starting the secureserver as shipped with
RH6.1. I couldn't not find a matching upgrade of mod_perl on the errata
site. Please advise - should I discontinue use of mod_perl until Red Hat
releases a new mod_perl RPM? Thanks!

Comment 1 Sullivan, Drew 2000-01-28 17:50:59 UTC

This also affects the following modules:

libphp3.so
libperl.so
mod_jserv.so
libdav.so
mod_roaming.so

In otherwords, it totally breaks any use of ssl in scripted
site (which is the whole point of having ssl.)

Comment 2 Preston Brown 2000-01-28 21:54:59 UTC

you may safely ignore it.  It is a warning for those modules which may use SSL
functionality, but aren't compiled against a SSL-enabled web server.  The web
server is SSL-enabled, and the modules don't use any SSL functionality, so there
is no problem and the warning (it is not an error) can be safely ignored.

If you do experience any actual crashes, open a new bug.