Bug #13824 error while loading shared libraries: libmysqlclient.so.14:
Submitted: 6 Oct 2005 23:26 Modified: 7 Nov 2005 0:55
Reporter: Rabindran Kanakalingam Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:4.1.12 OS:Linux (Linux (Fedora))
Assigned to: MySQL Verification Team CPU Architecture:Any

[6 Oct 2005 23:26] Rabindran Kanakalingam
Description:
When i try to run any commands from the bin directory, mysql commands i get the below errror messages

[root@opsdev bin]# ./mysqladmin
./mysqladmin: error while loading shared libraries: libmysqlclient.so.14: cannot open shared object file: No such file or directory

[root@opsdev bin]# ldd /usr/local/mysql/lib/mysql/libmysqlclient.so.14
        libcrypt.so.1 => /lib/libcrypt.so.1 (0xf6f64000)
        libnsl.so.1 => /lib/libnsl.so.1 (0xf6f4e000)
        libm.so.6 => /lib/tls/libm.so.6 (0xf6f2a000)
        libz.so.1 => /usr/lib/libz.so.1 (0xf6f1a000)
        libc.so.6 => /lib/tls/libc.so.6 (0xf6df3000)
        /lib/ld-linux.so.2 (0x002dc000)

How to repeat:
When i try to run any commands from the bin directory, mysql commands i get the below errror messages

[root@opsdev bin]# ./mysqladmin
./mysqladmin: error while loading shared libraries: libmysqlclient.so.14: cannot open shared object file: No such file or directory

[root@opsdev bin]# ldd /usr/local/mysql/lib/mysql/libmysqlclient.so.14
        libcrypt.so.1 => /lib/libcrypt.so.1 (0xf6f64000)
        libnsl.so.1 => /lib/libnsl.so.1 (0xf6f4e000)
        libm.so.6 => /lib/tls/libm.so.6 (0xf6f2a000)
        libz.so.1 => /usr/lib/libz.so.1 (0xf6f1a000)
        libc.so.6 => /lib/tls/libc.so.6 (0xf6df3000)
        /lib/ld-linux.so.2 (0x002dc000)
[7 Oct 2005 0:55] MySQL Verification Team
Please verify if you don't have in your environment mixed libraries
and binaries with different version installed during the Fedora
initial installation.

Thanks in advance.
[8 Nov 2005 0:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".