Fixing "error while loading shared libraries" on Linux: Causes & Solutions

When a Linux program cannot find a required shared library, it displays an error such as

error while loading shared libraries: libevent-1.4.so.2: cannot open shared object file: No such file or directory

. The problem usually stems from either the library not being installed or the loader not searching the correct directories.

1. Run ldconfig for libraries in standard paths

If the library resides in /lib or /usr/lib, execute ldconfig to refresh the system's cache ( /etc/ld.so.cache) which stores the sorted list of available shared objects.

2. Add non‑standard directories to /etc/ld.so.conf

For libraries installed in locations such as /usr/local/lib or any other custom directory, append the path to /etc/ld.so.conf before running ldconfig:

# cat /etc/ld.so.conf include ld.so.conf.d/*.conf # echo "/usr/local/lib" >> /etc/ld.so.conf # ldconfig

3. Use LD_LIBRARY_PATH as a temporary workaround

When you lack permission to modify /etc/ld.so.conf or need a quick fix, export the environment variable LD_LIBRARY_PATH with the directory containing the library. Example for MySQL libraries:

export LD_LIBRARY_PATH=/usr/local/mysql/lib:$LD_LIBRARY_PATH

This method is suitable for temporary or user‑specific scenarios.

4. Create a symbolic link for version mismatches

If the program expects an older library version that is not present but a newer compatible version exists, create a symlink pointing the expected name to the available file. Example for libncurses:

ln -s /usr/lib/libncurses.so.5.3 /usr/lib/libncurses.so.4

The following image illustrates the linking command output:

These steps cover the most common causes and remedies for shared‑library loading errors on Linux systems.