apache 1.3.17, tomcat 3.3 with mod_jk compiled under AIX 4.3.3 was
running fine for years, even though we switched servers and are now
running AIX 5.2.

After rebooting for the first time since installing AIX 5.2 ML07,
apache does not start and has the following entry in error_log:

"Cannot load /usr/local/lib/apache/mod_jk.so into server: Bad address"

I could not find any resource that tells me what "Bad address" means.

Help!

kurt.bremser@allianz.at wrote:
> apache 1.3.17, tomcat 3.3 with mod_jk compiled under AIX 4.3.3 was
> running fine for years, even though we switched servers and are now
> running AIX 5.2.
>
> After rebooting for the first time since installing AIX 5.2 ML07,
> apache does not start and has the following entry in error_log:
>
> "Cannot load /usr/local/lib/apache/mod_jk.so into server: Bad address"
>
> I could not find any resource that tells me what "Bad address" means.

Although i'm not an expert on the *exact* details of the
ML update process i'd guess the following: Up to the re-
boot some old libs (probably from the original 4.3.3 OS
level) were in use by apache/tomcat. On disk they were
already replaced with those supplied by the update. By
rebooting you forced apache/tomcat to use the new libs
from disk. Now it will not run since those new libs seem
not to be compatible with the 4.3.3 libs.
A solution would be to use a newer apache/tomcat version
from the linux toolbox. If you are bound to a specific
version of apache/tomcat by your application you might
have to build that particular apache/tomcat version your-
self, using the new libs from 5.2ML7.

Regards,

Frank

Obviously some sort of PEBKAC came into play. It looks as if somebody
(could even have been me in a fit of madness) reactivated libssl.so,
and that collided with the mod_jk we use.
After commenting out the lines for LoadModule and AddModule (libssl),
everything worked again.