When I run 'openssl' I am getting an error as below :
It is starting to make sense now from outside the chroot, means exit the chroot if you are inside it or do not run the chroot command but setup the the mounts under /mnt ready to run arch-chroot.
openssl: error while loading shared libraries: libcrypto.so.1.1: cannot open shared object file: No such file or directory'
This happened after I attempted to update OpenSSL according to this article
Is there anyway to fix this?
OS : CentOS 6.8Web server : nginx/1.10.2
Update #1 :
mayasl
mayaslmayasl
9 Answers
I was having the same issue after install the last version of openssl 1.1.0c, I resolved the issue copying the library files
After copy the libraries you need to create the symbolic link.
libcrypto.so.1.1
, libcrypto.a
and libssl.so
from /usr/local/lib64
to the share library at /usr/lib64
.After copy the libraries you need to create the symbolic link.
After creating the symbolic link rebuilding the ldconfig cache was required as well:
Castaglia2,65433 gold badges1212 silver badges3636 bronze badges
BenedictBenedict
With your original version of OpenSSL it knew how to find the shared libs because
/usr/lib64
is included in the linker's search path. When you downloaded and compiled a 'local' copy of OpenSSL, the shared libs were placed in /usr/local/lib64
by default. So you probably just need to add this directory to the search path of the linker, like this (as root):then execute:
I believe this will resolve your issue.
chicks3,09077 gold badges2020 silver badges3333 bronze badges
doug.fsudoug.fsu
I got this error using Termux on ChromeOS, which caused the
npm
and node
command line programs to crash.Running
pkg upgrade
fixed the problem!Carl WalshCarl Walsh
You can reinstall it using
yum install -y openssl-devel
3,47511 gold badge1515 silver badges2929 bronze badges
What @benedict said worked for me. However you may find that some of the symlinks are pointing to older versions. Running
ls -l libcrypto*
from the /usr/libs will show you the links. As in the below example:Then you would want to remove the existing link first by typing
sudo rm libcrypto.so
and then copying libcrypto.so.1.1 as @benedict mentioned. Finally you can create the new link.sudo ln -s libcrypto.so.1.1 libcrypto.so
Hope this helps.
Ihsan IzwerIhsan Izwer
The
libcrypto.so
belongs to openssl-libs
package. If you manually force removed (with --nodeps
) this package or corrupted it by upgrading it, you will lose access to yum, wget, curl, ssh, etc. If the system has Internet access, download the openssl-libs
using the command /usr/bin/GET
. The syntax would look like the below if you're trying to restore version openssl-libs-1.0.2k-8.el7.x86_64
:This will create
chicksopenssl-libs-1.0.2k-8.el7.x86_64.rpm
package for you, you can use this to either re-install or extract the missing .so
file.3,09077 gold badges2020 silver badges3333 bronze badges
KarthikKarthik
I am gone through the exactly same issue... I have solved it by running the following commands.
ln -s /usr/local/lib/libcrypto.so.1.1 /usr/lib/libcrypto.so.1.1
This will create a softlink and you are good to go.
FaheemFaheem
This is best solution I have found around ...other solutions provided all over the internet, will not survive system reboot ;)
OS: Ubuntu 16.04
Comment lib directory settings and add good path
When you are done editing, run this command:
Then you will have good setting when you run:
ldd /usr/bin/openssl
Before this fix:
After fix I provided:
ZEROFZEROF
After building and installing open ssl openssl-1.1.0f, I fixed same error for lib libssl.so.1.1 creating a soft link :
ln -s /usr/local/lib/libssl.so.1.1 /usr/lib/libssl.so.1.1
RafaelRafael
Not the answer you're looking for? Browse other questions tagged openssl or ask your own question.
I am trying to run Spotify on Ubuntu 12.04. It used to work some time ago, when I tried to start it today, I got the following error:
how to fix it?
I tried
which however gives an error saying that it does not exist (any more)
Braiam53.6k2121 gold badges143143 silver badges228228 bronze badges
user3825755user382575521211 gold badge22 silver badges1010 bronze badges
1 Answer
THIS SOLUTION BREAKS UNITY ON RECENT VERSIONS OF UBUNTU WHICH MAKES UBUNTU UNABLE TO BOOT. YOU PROBABLY DON'T WANT TO TRY IT UNLESS YOU KNOW WHAT YOU'RE DOING.
PLEASE PROCEED WITH CAUTION.
In Ubuntu 12.04 LTS do following:
Then you create a symlink to the file as following (64bit):
PLEASE PROCEED WITH CAUTION!!
sudo ln -sf /lib/x86_64-linux-gnu/libudev.so.0 /lib/x86_64-linux-gnu/libudev.so.1
sudo ln -sf /lib/x86_64-linux-gnu/libudev.so.0 /lib/x86_64-linux-gnu/libudev.so.1
If you are using a 32bit:
PLEASE PROCEED WITH CAUTION!!
sudo ln -sf /lib/i386-linux-gnu/libudev.so.0 /lib/i386-linux-gnu/libudev.so.1
sudo ln -sf /lib/i386-linux-gnu/libudev.so.0 /lib/i386-linux-gnu/libudev.so.1
Now Spotify should recognize the correct library.If this doesn't work, please post back and I'll try to help you further :)
Mina Michael4,3491818 gold badges6262 silver badges125125 bronze badges
Lars MartinsenLars Martinsen