bmrsetupclient: error while loading shared libraries: libnsl.so.1: cannot open shared object file: No such file or directory

Article: 100046875
Last Published: 2019-12-20
Ratings: 1 4
Product(s): NetBackup & Alta Data Protection

Problem

NetBackup 8.2 Client Installation fails on CentOS 8.0 with bmrsetupclient, since it cannot open shared object file due to there being no such file or directory.

 

Error Message

Error during NetBackup Client Installation, after migrating logs:
 
Migrating log files in /usr/openv/logs
Migration of log files complete.
 
/usr/openv/netbackup/bin/bmrsetupclient: error while loading shared libraries: libnsl.so.1: cannot open shared object file: No such file or directory

 

Cause

After following steps in Related Article (100045645). The required library reportedly still did not exist.

ls -l /usr/lib64/libnsl.so.1
ls: cannot access '/usr/lib64/libnsl.so.1': No such file or directory

ls -l /usr/lib64/libnsl.so.2
lrwxrwxrwx. 1 root root 15 May 11  2019 /usr/lib64/libnsl.so.2 -> libnsl.so.2.0.0

ls -l /usr/lib64/libnsl.so.2.0.0
-rwxr-xr-x. 1 root root 120592 May 11  2019 /usr/lib64/libnsl.so.2.0.0

Note: For this example, the client also had /lib64 symbolically linked to the /usr/lib64 directory.

ls -l / | grep lib64
lrwxrwxrwx.   1 root          root             9 May 11  2019 lib64 -> usr/lib64

 

Solution

Workaround

Create a symbolic link for version 1, which is pointing to the version 2 symbolic link, which already exists and is pointing to the latest library version file.

# cd /usr/lib64
# ln -sf libnsl.so.2 libnsl.so.1

Afterwards, the install completed successful and services started properly.

 

Was this content helpful?