Error While Loading Shared Cannot Open Shared Object No Such File or Directory

⏳ TL;DR (Too Long; Didn’t Read)

The “error while loading shared libraries” message means a Linux application is trying to run, but it can’t find a specific .so (Shared Object) file it needs to function. To fix this, you simply need to find out which library is missing using the ldd command, install the missing package via your package manager (like apt or yum), and refresh the system’s library cache using ldconfig.

If you manage Linux servers or develop software, you have likely encountered the dreaded terminal message: “error while loading shared libraries: [library_name].so: cannot open shared object file: No such file or directory.”

While it looks intimidating, this is one of the easiest Linux errors to diagnose and resolve. It is simply a missing dependency issue. Below is the ultimate system administrator guide to fixing this error permanently.

⚡ Quick Answer: Fix the Missing Shared Library

Run these commands sequentially in your terminal to resolve the dependency:

Identify the missing library: Run ldd /path/to/your/program. Look for the line that says “not found”.
Locate the package: Run apt-file search libname.so (Ubuntu/Debian) or yum whatprovides libname.so (CentOS/RHEL).
Install the package: Run sudo apt install [package_name].
Refresh the cache: Run sudo ldconfig so the system registers the newly installed library.

Why Does This Error Happen?

In Linux, programs are often dynamically linked. Instead of bundling every single piece of code into one massive executable file, programs rely on external Shared Objects (.so files) installed on the operating system. This saves disk space and RAM. The error occurs when:

The required library is simply not installed on the system.
The library is installed, but in a non-standard directory (not in /usr/lib or /lib).
The application was compiled for a 32-bit architecture, but you are running a 64-bit OS without the 32-bit compatibility libraries.

CBSE 10th Second Exam Result 2026: Expected Date & How to Check

Common Missing Libraries & Installation Commands

Missing File Error	Ubuntu / Debian Command	RHEL / CentOS Command
libstdc++.so.6	`sudo apt install libstdc++6`	`sudo yum install libstdc++`
libc.so.6	`sudo apt install libc6`	`sudo yum install glibc`
libnsl.so.1	`sudo apt install libnsl`	`sudo yum install libnsl`
libz.so.1 (32-bit on 64-bit OS)	`sudo apt install zlib1g:i386`	`sudo yum install zlib.i686`

Advanced Fixes: What if the Library is Already Installed?

Sometimes, you download a library manually or install custom software in /opt/ or /usr/local/lib. The system doesn’t automatically look there. You have two ways to tell Linux where to find the file.

Method 1: Update LD_LIBRARY_PATH (Temporary/User Fix)

You can export an environment variable that tells the program exactly where to look during runtime. This is great for software that doesn’t need system-wide access.

export LD_LIBRARY_PATH=/path/to/custom/lib:$LD_LIBRARY_PATH
./your_program

Method 2: Add to ldconfig (Permanent/System-wide Fix)

To make the custom library path permanent across system reboots, you need to add it to the ld.so.conf directory.

Create a new configuration file: sudo nano /etc/ld.so.conf.d/custom-libs.conf
Paste the absolute path to your library directory (e.g., /opt/myapp/libs) into the file and save.
Run sudo ldconfig to rebuild the linker cache.

Expert Note: This guide follows best practices for Linux System Administration across Debian and Red Hat based distributions. Always avoid downloading .so files from unverified third-party websites. Rely strictly on your OS’s official package managers (apt, yum, dnf, pacman) to ensure system stability and security.