+++ This bug was initially created as a clone of Bug #240253 +++
My latest run of 'yum update' included an update for openldap-devel. Since I
don't plan to do any development related to ldap I removed the package 'using
rpm -e openldap-devel'. I then discovered I could no longer use the 'sudo'
command. The sudo command would give me the message:
sudo: error while loading shared libraries: libldap-2.3.so.0: cannot open shared
object file: No such file or directory
When I re-install the openldap-devel package I am able to use the sudo command
The above happens consistently. When I remove openldap-devel I no longer have
the /usr/lib/libldap.so file and can't run sudo. When I install openldap-devel I
can use the sudo command.
--- Additional comment from firstname.lastname@example.org on 2007-05-16 04:13:18 EDT ---
Thank you for the bug report. There is just missing 'ldconfig' in %postun of
You can safely remove openldap-devel, but afterwards you must manually call
ldconfig as root:
rpm -e openldap-devel
I'll fix it in next release of openldap rpms.
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
Apart from the problem described above, OpenLDAP uses libldap.so as name of ldap library and it confuses ldconfig - it can create links during package update as follows:
libldap-2.3.so.0 -> libldap.so
/usr/lib64/libldap.so -> libldap-2.3.so.0.2.31
The same applies to libldap and libldap_r.
This is perfectly working, only "rpm -V openldap" complains about wrong links:
The correct way how to fix it is to rename libldap.so to libldap-2.3.so, but doing that might break customers setup, they are used to have libldap.so.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.