This article is discussing about the specific error as is in the title. It is still has a connection with the article in this link. The impact is also affecting on how the vim command react. Below is the output of executing ‘vim’ command that ends with the error message :
[root@localhost sbin]# vim sshd vim: error while loading shared libraries: libfreebl3.so: cannot open shared object file: No such file or directory [root@localhost sbin]#
As the error message in the above command execution output shows, it cannot find libfreebl.30 file. Actually, it has the same impact with the ssh service as shown in the article in this link.
The solution obviously is similar. The question is why bother copy the libfreebl3.s0 file to ‘/usr/lib64’ directory since it is a CentOS Linux operating system ?. Actually, reinstalling the libfreebl using ‘yum’ will just solve the problem. But that is possible when ‘yum’ command is not affected. In the reality, performing the yum command is also fails terribly.
So, to solve this problem without further explanation, just do the following steps :
1. Copy the file with the name of libfreebl3.so. In this case, the operating system is CentOS. It exists in the /usr/lib64 folder. Execute several commands as follows :
[root@hostname lib64]# pwd /usr/lib64 [root@hostname lib64]# ls -al | grep libfree3.so [root@hostname lib64]# ls -al | grep libfreebl3.so -rwxr-xr-x. 1 root root 11448 May 16 2018 libfreebl3.so [root@hostname lib64]# scp libfreebl3.so firstname.lastname@example.org:/root email@example.com's password: libfreebl3.so 100% 11KB 1.9MB/s 00:00 [root@hostname lib64]#
2. Don’t forget to modify the file permission. Execute the following command :
[root@localhost lib64]# chmod +x libfreebl3.so [root@localhost lib64]#
3. Finally, test the ‘vim’ command again to make sure that the solution actually works like a charm.