osdir.com


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug 61613] Facing issue to start Apache after upgrading to 2.4.28 -libssl.so.1.1: cannot open shared object file: No such file or directory


https://bz.apache.org/bugzilla/show_bug.cgi?id=61613

--- Comment #11 from Ruediger Pluem <rpluem@xxxxxxxxxx> ---
(In reply to Aakash from comment #9)
> Hi,
> 
> We have rolled back the apache to version 2.4.27 and tried to do ldd.
> Following is the result:
> 
> [apache@*** apache]$ ldd /opt/SP/apache/httpd_current/modules/mod_ssl.so
>         linux-vdso.so.1 =>  (0x00007ffef4f05000)
>         librt.so.1 => /lib64/librt.so.1 (0x00007fedaf0cf000)
>         libcrypt.so.1 => /lib64/libcrypt.so.1 (0x00007fedaee98000)
>         libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fedaec7b000)
>         libdl.so.2 => /lib64/libdl.so.2 (0x00007fedaea77000)
>         libc.so.6 => /lib64/libc.so.6 (0x00007fedae6b4000)
>         libfreebl3.so => /lib64/libfreebl3.so (0x00007fedae4b0000)
>         /lib64/ld-linux-x86-64.so.2 (0x00007fedaf78f000)
> Kindly advice.
> 
> Thanks and best regards,
> Aakash

This confirms what was suspected in comment 7: You have compiled httpd 2.4.27
against a self compiled Openssl, but this Openssl was of the same version as
the system one. So when you started httpd it used the system one and not the
Openssl you compiled on your own. Now that you use a newer version of Openssl
for your self compiled Openssl and compile httpd against this, this does no
longer work as httpd cannot fall back to the system provided Openssl. To solve
this ensure that your self compiled version of Openssl is usable for httpd by
either setting LD_LIBRARY_PATH or by making it available to the dynamic linker
in general (adding path to linker configuration, installing it in a path the
linker already is aware of).

-- 
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: bugs-help@xxxxxxxxxxxxxxxx