error while loading shared libraries: libcrypto.so.1.1How can I build Node.js using static libssl and crypto libraries?Error while converting der private key to pemTLS connect failed: error:140943FC:SSL routines:SSL3_READ_BYTES:sslv3 alert bad record mac while sending mail via Qmailopenssl ./config shared error (libcrypto.a)Why this error: SSCEP.exe : error verifiying signature happens?OpenSSL error while loading CRLnumberWhat is causing SSL-“shutdown while in init” error on dovecot?Odd error while using opensslHow to resolve Openssl Package error while installing nginxWhy is there openSSL version difference?
Inverse-quotes-quine
Should I include salary information on my CV?
Does squid ink pasta bleed?
Would a two-seat light aircaft with a landing speed of 20 knots and a top speed of 180 knots be technically possible?
How to split an equation over two lines?
Through the Looking-Glass
How can I deal with a coworker killed on the job
Does the posterior necessarily follow the same conditional dependence structure as the prior?
Why is there no havdallah when going from Yom Tov into Shabbat?
In the Marvel universe, can a human have a baby with any non-human?
Is there any evidence that the small canisters (10 liters) of 95% oxygen actually help with altitude sickness?
Why is Madam Hooch not a professor?
What do you call a weak person's act of taking on bigger opponents?
Why aren't (poly-)cotton tents more popular?
Dimensions of list used in test
MH370 blackbox - is it still possible to retrieve data from it?
When is it ok to add filler to a story?
Story-based adventure with functions and relationships
How to determine what is the correct level of detail when modelling?
Can a Horncaller control a Druid who is using Wild Shape?
Is my Rep in Stack-Exchange Form?
Links to webpages in books
Require advice on power conservation for backpacking trip
Can ADFS connect to other SSO services?
error while loading shared libraries: libcrypto.so.1.1
How can I build Node.js using static libssl and crypto libraries?Error while converting der private key to pemTLS connect failed: error:140943FC:SSL routines:SSL3_READ_BYTES:sslv3 alert bad record mac while sending mail via Qmailopenssl ./config shared error (libcrypto.a)Why this error: SSCEP.exe : error verifiying signature happens?OpenSSL error while loading CRLnumberWhat is causing SSL-“shutdown while in init” error on dovecot?Odd error while using opensslHow to resolve Openssl Package error while installing nginxWhy is there openSSL version difference?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
When I run "openssl" I am getting an error as below :
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.8
Web server : nginx/1.10.2
Update #1 :
[root@host ~]# yum info openssl
Installed Packages
Name : openssl
Arch : x86_64
Version : 1.0.1e
Release : 48.el6_8.3
Size : 4.0 M
Repo : installed
From repo : system-updates
Summary : A general purpose cryptography library with TLS implementation
URL : ***
License : OpenSSL
Description : The OpenSSL toolkit provides support for secure communications
: between machines. OpenSSL includes a certificate management tool and
: shared libraries which provide various cryptographic algorithms and
: protocols.
Available Packages
Name : openssl
Arch : i686
Version : 1.0.1e
Release : 48.el6_8.3
Size : 1.5 M
Repo : system-updates
Summary : A general purpose cryptography library with TLS implementation
URL : ***
License : OpenSSL
Description : The OpenSSL toolkit provides support for secure communications
: between machines. OpenSSL includes a certificate management tool and
: shared libraries which provide various cryptographic algorithms and
: protocols.
openssl
add a comment |
When I run "openssl" I am getting an error as below :
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.8
Web server : nginx/1.10.2
Update #1 :
[root@host ~]# yum info openssl
Installed Packages
Name : openssl
Arch : x86_64
Version : 1.0.1e
Release : 48.el6_8.3
Size : 4.0 M
Repo : installed
From repo : system-updates
Summary : A general purpose cryptography library with TLS implementation
URL : ***
License : OpenSSL
Description : The OpenSSL toolkit provides support for secure communications
: between machines. OpenSSL includes a certificate management tool and
: shared libraries which provide various cryptographic algorithms and
: protocols.
Available Packages
Name : openssl
Arch : i686
Version : 1.0.1e
Release : 48.el6_8.3
Size : 1.5 M
Repo : system-updates
Summary : A general purpose cryptography library with TLS implementation
URL : ***
License : OpenSSL
Description : The OpenSSL toolkit provides support for secure communications
: between machines. OpenSSL includes a certificate management tool and
: shared libraries which provide various cryptographic algorithms and
: protocols.
openssl
2
Sorry, you've run into yet another bad Internet tutorial. You might have to reinstall the system. Before going further, I suggest you ask about the original problem that you were trying to solve by doing this. There is probably a better way to accomplish the original goal.
– Michael Hampton♦
Dec 2 '16 at 20:01
I wanted to install Server Monitor application provided by Monitis. It needed some shared library dependencies which was not installed in my server. So, all this happened when was up to install those. :(
– mayasl
Dec 2 '16 at 20:19
@MichaelHampton Please tell me something except reinstalling the system. Because a live site is running on that server!
– mayasl
Dec 2 '16 at 20:29
add a comment |
When I run "openssl" I am getting an error as below :
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.8
Web server : nginx/1.10.2
Update #1 :
[root@host ~]# yum info openssl
Installed Packages
Name : openssl
Arch : x86_64
Version : 1.0.1e
Release : 48.el6_8.3
Size : 4.0 M
Repo : installed
From repo : system-updates
Summary : A general purpose cryptography library with TLS implementation
URL : ***
License : OpenSSL
Description : The OpenSSL toolkit provides support for secure communications
: between machines. OpenSSL includes a certificate management tool and
: shared libraries which provide various cryptographic algorithms and
: protocols.
Available Packages
Name : openssl
Arch : i686
Version : 1.0.1e
Release : 48.el6_8.3
Size : 1.5 M
Repo : system-updates
Summary : A general purpose cryptography library with TLS implementation
URL : ***
License : OpenSSL
Description : The OpenSSL toolkit provides support for secure communications
: between machines. OpenSSL includes a certificate management tool and
: shared libraries which provide various cryptographic algorithms and
: protocols.
openssl
When I run "openssl" I am getting an error as below :
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.8
Web server : nginx/1.10.2
Update #1 :
[root@host ~]# yum info openssl
Installed Packages
Name : openssl
Arch : x86_64
Version : 1.0.1e
Release : 48.el6_8.3
Size : 4.0 M
Repo : installed
From repo : system-updates
Summary : A general purpose cryptography library with TLS implementation
URL : ***
License : OpenSSL
Description : The OpenSSL toolkit provides support for secure communications
: between machines. OpenSSL includes a certificate management tool and
: shared libraries which provide various cryptographic algorithms and
: protocols.
Available Packages
Name : openssl
Arch : i686
Version : 1.0.1e
Release : 48.el6_8.3
Size : 1.5 M
Repo : system-updates
Summary : A general purpose cryptography library with TLS implementation
URL : ***
License : OpenSSL
Description : The OpenSSL toolkit provides support for secure communications
: between machines. OpenSSL includes a certificate management tool and
: shared libraries which provide various cryptographic algorithms and
: protocols.
openssl
openssl
edited Dec 2 '16 at 22:01
mayasl
asked Dec 2 '16 at 19:47
mayaslmayasl
541 gold badge1 silver badge4 bronze badges
541 gold badge1 silver badge4 bronze badges
2
Sorry, you've run into yet another bad Internet tutorial. You might have to reinstall the system. Before going further, I suggest you ask about the original problem that you were trying to solve by doing this. There is probably a better way to accomplish the original goal.
– Michael Hampton♦
Dec 2 '16 at 20:01
I wanted to install Server Monitor application provided by Monitis. It needed some shared library dependencies which was not installed in my server. So, all this happened when was up to install those. :(
– mayasl
Dec 2 '16 at 20:19
@MichaelHampton Please tell me something except reinstalling the system. Because a live site is running on that server!
– mayasl
Dec 2 '16 at 20:29
add a comment |
2
Sorry, you've run into yet another bad Internet tutorial. You might have to reinstall the system. Before going further, I suggest you ask about the original problem that you were trying to solve by doing this. There is probably a better way to accomplish the original goal.
– Michael Hampton♦
Dec 2 '16 at 20:01
I wanted to install Server Monitor application provided by Monitis. It needed some shared library dependencies which was not installed in my server. So, all this happened when was up to install those. :(
– mayasl
Dec 2 '16 at 20:19
@MichaelHampton Please tell me something except reinstalling the system. Because a live site is running on that server!
– mayasl
Dec 2 '16 at 20:29
2
2
Sorry, you've run into yet another bad Internet tutorial. You might have to reinstall the system. Before going further, I suggest you ask about the original problem that you were trying to solve by doing this. There is probably a better way to accomplish the original goal.
– Michael Hampton♦
Dec 2 '16 at 20:01
Sorry, you've run into yet another bad Internet tutorial. You might have to reinstall the system. Before going further, I suggest you ask about the original problem that you were trying to solve by doing this. There is probably a better way to accomplish the original goal.
– Michael Hampton♦
Dec 2 '16 at 20:01
I wanted to install Server Monitor application provided by Monitis. It needed some shared library dependencies which was not installed in my server. So, all this happened when was up to install those. :(
– mayasl
Dec 2 '16 at 20:19
I wanted to install Server Monitor application provided by Monitis. It needed some shared library dependencies which was not installed in my server. So, all this happened when was up to install those. :(
– mayasl
Dec 2 '16 at 20:19
@MichaelHampton Please tell me something except reinstalling the system. Because a live site is running on that server!
– mayasl
Dec 2 '16 at 20:29
@MichaelHampton Please tell me something except reinstalling the system. Because a live site is running on that server!
– mayasl
Dec 2 '16 at 20:29
add a comment |
9 Answers
9
active
oldest
votes
I was having the same issue after install the last version of openssl 1.1.0c, I resolved the issue copying the library files 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.
ln -s libcrypto.so.1.1 libcrypto.so
ln -s libssl.so.1.1 libssl.so
After creating the symbolic link rebuilding the ldconfig cache was required as well:
sudo ldconfig
add a comment |
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):
echo "/usr/local/lib64" > /etc/ld.so.conf.d/openssl.conf
then execute:
ldconfig
I believe this will resolve your issue.
In at least modern Ubuntu distributions (I'm writing this on 16.04 LTS) and probably others,sudo echo "/usr/local/lib64" > /etc/ld.so.conf.d/openssl.conf
will result in a "permission denied" error because the second half of the command (the file write) isn't executed as root. If this happens, trysudo sh -c "echo '/usr/local/lib64' >> /etc/ld.so.conf.d/openssl.conf"
instead.
– Matthew Cole
Feb 21 '18 at 18:15
add a comment |
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!
add a comment |
You can reinstall it using
yum install -y openssl-devel
I tried it as well, but didn't help!
– mayasl
Dec 2 '16 at 20:19
@mayasl Maybe you need to reinstall other packages as well. I would expect a package calledopenssl-devel
to depend on a package calledopenssl
. Bare in mind that it has been a long time since I touchedyum
, so I cannot verify the syntax of the command for you.
– kasperd
Dec 2 '16 at 21:37
I have updated my question with the output of "yum info openssl". Please take a look, if it is useful. I removed and reinstalled openssl and openssl-devel before starting this thread. Didn't work! Commands I used :code
yum remove openssl yum remove openssl-devel yum clean all
– mayasl
Dec 2 '16 at 22:02
Reinstallingopenssl
, (and notopenssl-devel
) should be a good start.
– Michael Hampton♦
Dec 2 '16 at 22:03
I already tried that @MichaelHampton Is this some sort of linking issue???
– mayasl
Dec 2 '16 at 22:08
|
show 2 more comments
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:
lrwxrwxrwx 1 root root 16 May 21 15:28 libcrypto.so -> libcrypto.so.1.0
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.
add a comment |
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
:
/usr/bin/GET http://downloadURL/openssl-libs-1.0.2k-8.el7.x86_64.rpm > openssl-libs-1.0.2k-8.el7.x86_64.rpm
This will create openssl-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.
add a comment |
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.
add a comment |
This is best solution I have found around ...other solutions provided all over the internet, will not survive system reboot ;)
OS: Ubuntu 16.04
sudo vim /etc/ld.so.conf.d/libc.conf
Comment lib directory settings and add good path
# libc default configuration
#/usr/local/lib
/usr/lib
When you are done editing, run this command:
sudo ldconfig
Then you will have good setting when you run:
ldd /usr/bin/openssl
Before this fix:
/usr/bin/openssl: /usr/local/lib/libssl.so.1.0.0: no version information available (required by /usr/bin/openssl)
/usr/bin/openssl: /usr/local/lib/libssl.so.1.0.0: no version information available (required by /usr/bin/openssl)
/usr/bin/openssl: /usr/local/lib/libssl.so.1.0.0: no version information available (required by /usr/bin/openssl)
/usr/bin/openssl: /usr/local/lib/libcrypto.so.1.0.0: no version information available (required by /usr/bin/openssl)
/usr/bin/openssl: /usr/local/lib/libcrypto.so.1.0.0: no version information available (required by /usr/bin/openssl)
/usr/bin/openssl: /usr/local/lib/libcrypto.so.1.0.0: no version information available (required by /usr/bin/openssl)
/usr/bin/openssl: /usr/local/lib/libcrypto.so.1.0.0: no version information available (required by /usr/bin/openssl)
linux-vdso.so.1 => (0x00007ffe6d1e3000)
libssl.so.1.0.0 => /usr/local/lib/libssl.so.1.0.0 (0x00007f8999827000)
libcrypto.so.1.0.0 => /usr/local/lib/libcrypto.so.1.0.0 (0x00007f89993ed000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f8999023000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f8998e1f000)
/lib64/ld-linux-x86-64.so.2 (0x00007f8999a97000)
After fix I provided:
linux-vdso.so.1 => (0x00007ffec39bc000)
libssl.so.1.0.0 => /lib/x86_64-linux-gnu/libssl.so.1.0.0 (0x00007f7faad22000)
libcrypto.so.1.0.0 => /lib/x86_64-linux-gnu/libcrypto.so.1.0.0 (0x00007f7faa8dd000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f7faa513000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f7faa30f000)
/lib64/ld-linux-x86-64.so.2 (0x00007f7faaf8b000)
For people with CentOS path, I think good file is /etc/ld.so.conf ;), just to be clear.
– ZEROF
Jun 7 at 20:16
add a comment |
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
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "2"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f818445%2ferror-while-loading-shared-libraries-libcrypto-so-1-1%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
9 Answers
9
active
oldest
votes
9 Answers
9
active
oldest
votes
active
oldest
votes
active
oldest
votes
I was having the same issue after install the last version of openssl 1.1.0c, I resolved the issue copying the library files 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.
ln -s libcrypto.so.1.1 libcrypto.so
ln -s libssl.so.1.1 libssl.so
After creating the symbolic link rebuilding the ldconfig cache was required as well:
sudo ldconfig
add a comment |
I was having the same issue after install the last version of openssl 1.1.0c, I resolved the issue copying the library files 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.
ln -s libcrypto.so.1.1 libcrypto.so
ln -s libssl.so.1.1 libssl.so
After creating the symbolic link rebuilding the ldconfig cache was required as well:
sudo ldconfig
add a comment |
I was having the same issue after install the last version of openssl 1.1.0c, I resolved the issue copying the library files 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.
ln -s libcrypto.so.1.1 libcrypto.so
ln -s libssl.so.1.1 libssl.so
After creating the symbolic link rebuilding the ldconfig cache was required as well:
sudo ldconfig
I was having the same issue after install the last version of openssl 1.1.0c, I resolved the issue copying the library files 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.
ln -s libcrypto.so.1.1 libcrypto.so
ln -s libssl.so.1.1 libssl.so
After creating the symbolic link rebuilding the ldconfig cache was required as well:
sudo ldconfig
edited Feb 25 '17 at 16:06
Castaglia
2,6343 gold badges12 silver badges36 bronze badges
2,6343 gold badges12 silver badges36 bronze badges
answered Dec 3 '16 at 13:46
BenedictBenedict
1712 bronze badges
1712 bronze badges
add a comment |
add a comment |
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):
echo "/usr/local/lib64" > /etc/ld.so.conf.d/openssl.conf
then execute:
ldconfig
I believe this will resolve your issue.
In at least modern Ubuntu distributions (I'm writing this on 16.04 LTS) and probably others,sudo echo "/usr/local/lib64" > /etc/ld.so.conf.d/openssl.conf
will result in a "permission denied" error because the second half of the command (the file write) isn't executed as root. If this happens, trysudo sh -c "echo '/usr/local/lib64' >> /etc/ld.so.conf.d/openssl.conf"
instead.
– Matthew Cole
Feb 21 '18 at 18:15
add a comment |
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):
echo "/usr/local/lib64" > /etc/ld.so.conf.d/openssl.conf
then execute:
ldconfig
I believe this will resolve your issue.
In at least modern Ubuntu distributions (I'm writing this on 16.04 LTS) and probably others,sudo echo "/usr/local/lib64" > /etc/ld.so.conf.d/openssl.conf
will result in a "permission denied" error because the second half of the command (the file write) isn't executed as root. If this happens, trysudo sh -c "echo '/usr/local/lib64' >> /etc/ld.so.conf.d/openssl.conf"
instead.
– Matthew Cole
Feb 21 '18 at 18:15
add a comment |
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):
echo "/usr/local/lib64" > /etc/ld.so.conf.d/openssl.conf
then execute:
ldconfig
I believe this will resolve your issue.
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):
echo "/usr/local/lib64" > /etc/ld.so.conf.d/openssl.conf
then execute:
ldconfig
I believe this will resolve your issue.
edited Apr 17 '17 at 15:51
chicks
3,0907 gold badges20 silver badges33 bronze badges
3,0907 gold badges20 silver badges33 bronze badges
answered Apr 17 '17 at 13:40
doug.fsudoug.fsu
811 silver badge1 bronze badge
811 silver badge1 bronze badge
In at least modern Ubuntu distributions (I'm writing this on 16.04 LTS) and probably others,sudo echo "/usr/local/lib64" > /etc/ld.so.conf.d/openssl.conf
will result in a "permission denied" error because the second half of the command (the file write) isn't executed as root. If this happens, trysudo sh -c "echo '/usr/local/lib64' >> /etc/ld.so.conf.d/openssl.conf"
instead.
– Matthew Cole
Feb 21 '18 at 18:15
add a comment |
In at least modern Ubuntu distributions (I'm writing this on 16.04 LTS) and probably others,sudo echo "/usr/local/lib64" > /etc/ld.so.conf.d/openssl.conf
will result in a "permission denied" error because the second half of the command (the file write) isn't executed as root. If this happens, trysudo sh -c "echo '/usr/local/lib64' >> /etc/ld.so.conf.d/openssl.conf"
instead.
– Matthew Cole
Feb 21 '18 at 18:15
In at least modern Ubuntu distributions (I'm writing this on 16.04 LTS) and probably others,
sudo echo "/usr/local/lib64" > /etc/ld.so.conf.d/openssl.conf
will result in a "permission denied" error because the second half of the command (the file write) isn't executed as root. If this happens, try sudo sh -c "echo '/usr/local/lib64' >> /etc/ld.so.conf.d/openssl.conf"
instead.– Matthew Cole
Feb 21 '18 at 18:15
In at least modern Ubuntu distributions (I'm writing this on 16.04 LTS) and probably others,
sudo echo "/usr/local/lib64" > /etc/ld.so.conf.d/openssl.conf
will result in a "permission denied" error because the second half of the command (the file write) isn't executed as root. If this happens, try sudo sh -c "echo '/usr/local/lib64' >> /etc/ld.so.conf.d/openssl.conf"
instead.– Matthew Cole
Feb 21 '18 at 18:15
add a comment |
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!
add a comment |
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!
add a comment |
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!
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!
answered Sep 19 '18 at 2:05
Carl WalshCarl Walsh
1811 silver badge3 bronze badges
1811 silver badge3 bronze badges
add a comment |
add a comment |
You can reinstall it using
yum install -y openssl-devel
I tried it as well, but didn't help!
– mayasl
Dec 2 '16 at 20:19
@mayasl Maybe you need to reinstall other packages as well. I would expect a package calledopenssl-devel
to depend on a package calledopenssl
. Bare in mind that it has been a long time since I touchedyum
, so I cannot verify the syntax of the command for you.
– kasperd
Dec 2 '16 at 21:37
I have updated my question with the output of "yum info openssl". Please take a look, if it is useful. I removed and reinstalled openssl and openssl-devel before starting this thread. Didn't work! Commands I used :code
yum remove openssl yum remove openssl-devel yum clean all
– mayasl
Dec 2 '16 at 22:02
Reinstallingopenssl
, (and notopenssl-devel
) should be a good start.
– Michael Hampton♦
Dec 2 '16 at 22:03
I already tried that @MichaelHampton Is this some sort of linking issue???
– mayasl
Dec 2 '16 at 22:08
|
show 2 more comments
You can reinstall it using
yum install -y openssl-devel
I tried it as well, but didn't help!
– mayasl
Dec 2 '16 at 20:19
@mayasl Maybe you need to reinstall other packages as well. I would expect a package calledopenssl-devel
to depend on a package calledopenssl
. Bare in mind that it has been a long time since I touchedyum
, so I cannot verify the syntax of the command for you.
– kasperd
Dec 2 '16 at 21:37
I have updated my question with the output of "yum info openssl". Please take a look, if it is useful. I removed and reinstalled openssl and openssl-devel before starting this thread. Didn't work! Commands I used :code
yum remove openssl yum remove openssl-devel yum clean all
– mayasl
Dec 2 '16 at 22:02
Reinstallingopenssl
, (and notopenssl-devel
) should be a good start.
– Michael Hampton♦
Dec 2 '16 at 22:03
I already tried that @MichaelHampton Is this some sort of linking issue???
– mayasl
Dec 2 '16 at 22:08
|
show 2 more comments
You can reinstall it using
yum install -y openssl-devel
You can reinstall it using
yum install -y openssl-devel
answered Dec 2 '16 at 19:56
mzhaasemzhaase
3,4751 gold badge15 silver badges29 bronze badges
3,4751 gold badge15 silver badges29 bronze badges
I tried it as well, but didn't help!
– mayasl
Dec 2 '16 at 20:19
@mayasl Maybe you need to reinstall other packages as well. I would expect a package calledopenssl-devel
to depend on a package calledopenssl
. Bare in mind that it has been a long time since I touchedyum
, so I cannot verify the syntax of the command for you.
– kasperd
Dec 2 '16 at 21:37
I have updated my question with the output of "yum info openssl". Please take a look, if it is useful. I removed and reinstalled openssl and openssl-devel before starting this thread. Didn't work! Commands I used :code
yum remove openssl yum remove openssl-devel yum clean all
– mayasl
Dec 2 '16 at 22:02
Reinstallingopenssl
, (and notopenssl-devel
) should be a good start.
– Michael Hampton♦
Dec 2 '16 at 22:03
I already tried that @MichaelHampton Is this some sort of linking issue???
– mayasl
Dec 2 '16 at 22:08
|
show 2 more comments
I tried it as well, but didn't help!
– mayasl
Dec 2 '16 at 20:19
@mayasl Maybe you need to reinstall other packages as well. I would expect a package calledopenssl-devel
to depend on a package calledopenssl
. Bare in mind that it has been a long time since I touchedyum
, so I cannot verify the syntax of the command for you.
– kasperd
Dec 2 '16 at 21:37
I have updated my question with the output of "yum info openssl". Please take a look, if it is useful. I removed and reinstalled openssl and openssl-devel before starting this thread. Didn't work! Commands I used :code
yum remove openssl yum remove openssl-devel yum clean all
– mayasl
Dec 2 '16 at 22:02
Reinstallingopenssl
, (and notopenssl-devel
) should be a good start.
– Michael Hampton♦
Dec 2 '16 at 22:03
I already tried that @MichaelHampton Is this some sort of linking issue???
– mayasl
Dec 2 '16 at 22:08
I tried it as well, but didn't help!
– mayasl
Dec 2 '16 at 20:19
I tried it as well, but didn't help!
– mayasl
Dec 2 '16 at 20:19
@mayasl Maybe you need to reinstall other packages as well. I would expect a package called
openssl-devel
to depend on a package called openssl
. Bare in mind that it has been a long time since I touched yum
, so I cannot verify the syntax of the command for you.– kasperd
Dec 2 '16 at 21:37
@mayasl Maybe you need to reinstall other packages as well. I would expect a package called
openssl-devel
to depend on a package called openssl
. Bare in mind that it has been a long time since I touched yum
, so I cannot verify the syntax of the command for you.– kasperd
Dec 2 '16 at 21:37
I have updated my question with the output of "yum info openssl". Please take a look, if it is useful. I removed and reinstalled openssl and openssl-devel before starting this thread. Didn't work! Commands I used :
code
yum remove openssl yum remove openssl-devel yum clean all– mayasl
Dec 2 '16 at 22:02
I have updated my question with the output of "yum info openssl". Please take a look, if it is useful. I removed and reinstalled openssl and openssl-devel before starting this thread. Didn't work! Commands I used :
code
yum remove openssl yum remove openssl-devel yum clean all– mayasl
Dec 2 '16 at 22:02
Reinstalling
openssl
, (and not openssl-devel
) should be a good start.– Michael Hampton♦
Dec 2 '16 at 22:03
Reinstalling
openssl
, (and not openssl-devel
) should be a good start.– Michael Hampton♦
Dec 2 '16 at 22:03
I already tried that @MichaelHampton Is this some sort of linking issue???
– mayasl
Dec 2 '16 at 22:08
I already tried that @MichaelHampton Is this some sort of linking issue???
– mayasl
Dec 2 '16 at 22:08
|
show 2 more comments
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:
lrwxrwxrwx 1 root root 16 May 21 15:28 libcrypto.so -> libcrypto.so.1.0
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.
add a comment |
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:
lrwxrwxrwx 1 root root 16 May 21 15:28 libcrypto.so -> libcrypto.so.1.0
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.
add a comment |
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:
lrwxrwxrwx 1 root root 16 May 21 15:28 libcrypto.so -> libcrypto.so.1.0
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.
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:
lrwxrwxrwx 1 root root 16 May 21 15:28 libcrypto.so -> libcrypto.so.1.0
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.
answered May 22 '17 at 4:58
Ihsan IzwerIhsan Izwer
112 bronze badges
112 bronze badges
add a comment |
add a comment |
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
:
/usr/bin/GET http://downloadURL/openssl-libs-1.0.2k-8.el7.x86_64.rpm > openssl-libs-1.0.2k-8.el7.x86_64.rpm
This will create openssl-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.
add a comment |
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
:
/usr/bin/GET http://downloadURL/openssl-libs-1.0.2k-8.el7.x86_64.rpm > openssl-libs-1.0.2k-8.el7.x86_64.rpm
This will create openssl-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.
add a comment |
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
:
/usr/bin/GET http://downloadURL/openssl-libs-1.0.2k-8.el7.x86_64.rpm > openssl-libs-1.0.2k-8.el7.x86_64.rpm
This will create openssl-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.
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
:
/usr/bin/GET http://downloadURL/openssl-libs-1.0.2k-8.el7.x86_64.rpm > openssl-libs-1.0.2k-8.el7.x86_64.rpm
This will create openssl-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.
edited Jun 13 '18 at 13:00
chicks
3,0907 gold badges20 silver badges33 bronze badges
3,0907 gold badges20 silver badges33 bronze badges
answered Jun 13 '18 at 12:01
KarthikKarthik
592 bronze badges
592 bronze badges
add a comment |
add a comment |
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.
add a comment |
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.
add a comment |
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.
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.
answered Apr 24 '17 at 6:08
FaheemFaheem
1
1
add a comment |
add a comment |
This is best solution I have found around ...other solutions provided all over the internet, will not survive system reboot ;)
OS: Ubuntu 16.04
sudo vim /etc/ld.so.conf.d/libc.conf
Comment lib directory settings and add good path
# libc default configuration
#/usr/local/lib
/usr/lib
When you are done editing, run this command:
sudo ldconfig
Then you will have good setting when you run:
ldd /usr/bin/openssl
Before this fix:
/usr/bin/openssl: /usr/local/lib/libssl.so.1.0.0: no version information available (required by /usr/bin/openssl)
/usr/bin/openssl: /usr/local/lib/libssl.so.1.0.0: no version information available (required by /usr/bin/openssl)
/usr/bin/openssl: /usr/local/lib/libssl.so.1.0.0: no version information available (required by /usr/bin/openssl)
/usr/bin/openssl: /usr/local/lib/libcrypto.so.1.0.0: no version information available (required by /usr/bin/openssl)
/usr/bin/openssl: /usr/local/lib/libcrypto.so.1.0.0: no version information available (required by /usr/bin/openssl)
/usr/bin/openssl: /usr/local/lib/libcrypto.so.1.0.0: no version information available (required by /usr/bin/openssl)
/usr/bin/openssl: /usr/local/lib/libcrypto.so.1.0.0: no version information available (required by /usr/bin/openssl)
linux-vdso.so.1 => (0x00007ffe6d1e3000)
libssl.so.1.0.0 => /usr/local/lib/libssl.so.1.0.0 (0x00007f8999827000)
libcrypto.so.1.0.0 => /usr/local/lib/libcrypto.so.1.0.0 (0x00007f89993ed000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f8999023000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f8998e1f000)
/lib64/ld-linux-x86-64.so.2 (0x00007f8999a97000)
After fix I provided:
linux-vdso.so.1 => (0x00007ffec39bc000)
libssl.so.1.0.0 => /lib/x86_64-linux-gnu/libssl.so.1.0.0 (0x00007f7faad22000)
libcrypto.so.1.0.0 => /lib/x86_64-linux-gnu/libcrypto.so.1.0.0 (0x00007f7faa8dd000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f7faa513000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f7faa30f000)
/lib64/ld-linux-x86-64.so.2 (0x00007f7faaf8b000)
For people with CentOS path, I think good file is /etc/ld.so.conf ;), just to be clear.
– ZEROF
Jun 7 at 20:16
add a comment |
This is best solution I have found around ...other solutions provided all over the internet, will not survive system reboot ;)
OS: Ubuntu 16.04
sudo vim /etc/ld.so.conf.d/libc.conf
Comment lib directory settings and add good path
# libc default configuration
#/usr/local/lib
/usr/lib
When you are done editing, run this command:
sudo ldconfig
Then you will have good setting when you run:
ldd /usr/bin/openssl
Before this fix:
/usr/bin/openssl: /usr/local/lib/libssl.so.1.0.0: no version information available (required by /usr/bin/openssl)
/usr/bin/openssl: /usr/local/lib/libssl.so.1.0.0: no version information available (required by /usr/bin/openssl)
/usr/bin/openssl: /usr/local/lib/libssl.so.1.0.0: no version information available (required by /usr/bin/openssl)
/usr/bin/openssl: /usr/local/lib/libcrypto.so.1.0.0: no version information available (required by /usr/bin/openssl)
/usr/bin/openssl: /usr/local/lib/libcrypto.so.1.0.0: no version information available (required by /usr/bin/openssl)
/usr/bin/openssl: /usr/local/lib/libcrypto.so.1.0.0: no version information available (required by /usr/bin/openssl)
/usr/bin/openssl: /usr/local/lib/libcrypto.so.1.0.0: no version information available (required by /usr/bin/openssl)
linux-vdso.so.1 => (0x00007ffe6d1e3000)
libssl.so.1.0.0 => /usr/local/lib/libssl.so.1.0.0 (0x00007f8999827000)
libcrypto.so.1.0.0 => /usr/local/lib/libcrypto.so.1.0.0 (0x00007f89993ed000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f8999023000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f8998e1f000)
/lib64/ld-linux-x86-64.so.2 (0x00007f8999a97000)
After fix I provided:
linux-vdso.so.1 => (0x00007ffec39bc000)
libssl.so.1.0.0 => /lib/x86_64-linux-gnu/libssl.so.1.0.0 (0x00007f7faad22000)
libcrypto.so.1.0.0 => /lib/x86_64-linux-gnu/libcrypto.so.1.0.0 (0x00007f7faa8dd000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f7faa513000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f7faa30f000)
/lib64/ld-linux-x86-64.so.2 (0x00007f7faaf8b000)
For people with CentOS path, I think good file is /etc/ld.so.conf ;), just to be clear.
– ZEROF
Jun 7 at 20:16
add a comment |
This is best solution I have found around ...other solutions provided all over the internet, will not survive system reboot ;)
OS: Ubuntu 16.04
sudo vim /etc/ld.so.conf.d/libc.conf
Comment lib directory settings and add good path
# libc default configuration
#/usr/local/lib
/usr/lib
When you are done editing, run this command:
sudo ldconfig
Then you will have good setting when you run:
ldd /usr/bin/openssl
Before this fix:
/usr/bin/openssl: /usr/local/lib/libssl.so.1.0.0: no version information available (required by /usr/bin/openssl)
/usr/bin/openssl: /usr/local/lib/libssl.so.1.0.0: no version information available (required by /usr/bin/openssl)
/usr/bin/openssl: /usr/local/lib/libssl.so.1.0.0: no version information available (required by /usr/bin/openssl)
/usr/bin/openssl: /usr/local/lib/libcrypto.so.1.0.0: no version information available (required by /usr/bin/openssl)
/usr/bin/openssl: /usr/local/lib/libcrypto.so.1.0.0: no version information available (required by /usr/bin/openssl)
/usr/bin/openssl: /usr/local/lib/libcrypto.so.1.0.0: no version information available (required by /usr/bin/openssl)
/usr/bin/openssl: /usr/local/lib/libcrypto.so.1.0.0: no version information available (required by /usr/bin/openssl)
linux-vdso.so.1 => (0x00007ffe6d1e3000)
libssl.so.1.0.0 => /usr/local/lib/libssl.so.1.0.0 (0x00007f8999827000)
libcrypto.so.1.0.0 => /usr/local/lib/libcrypto.so.1.0.0 (0x00007f89993ed000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f8999023000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f8998e1f000)
/lib64/ld-linux-x86-64.so.2 (0x00007f8999a97000)
After fix I provided:
linux-vdso.so.1 => (0x00007ffec39bc000)
libssl.so.1.0.0 => /lib/x86_64-linux-gnu/libssl.so.1.0.0 (0x00007f7faad22000)
libcrypto.so.1.0.0 => /lib/x86_64-linux-gnu/libcrypto.so.1.0.0 (0x00007f7faa8dd000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f7faa513000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f7faa30f000)
/lib64/ld-linux-x86-64.so.2 (0x00007f7faaf8b000)
This is best solution I have found around ...other solutions provided all over the internet, will not survive system reboot ;)
OS: Ubuntu 16.04
sudo vim /etc/ld.so.conf.d/libc.conf
Comment lib directory settings and add good path
# libc default configuration
#/usr/local/lib
/usr/lib
When you are done editing, run this command:
sudo ldconfig
Then you will have good setting when you run:
ldd /usr/bin/openssl
Before this fix:
/usr/bin/openssl: /usr/local/lib/libssl.so.1.0.0: no version information available (required by /usr/bin/openssl)
/usr/bin/openssl: /usr/local/lib/libssl.so.1.0.0: no version information available (required by /usr/bin/openssl)
/usr/bin/openssl: /usr/local/lib/libssl.so.1.0.0: no version information available (required by /usr/bin/openssl)
/usr/bin/openssl: /usr/local/lib/libcrypto.so.1.0.0: no version information available (required by /usr/bin/openssl)
/usr/bin/openssl: /usr/local/lib/libcrypto.so.1.0.0: no version information available (required by /usr/bin/openssl)
/usr/bin/openssl: /usr/local/lib/libcrypto.so.1.0.0: no version information available (required by /usr/bin/openssl)
/usr/bin/openssl: /usr/local/lib/libcrypto.so.1.0.0: no version information available (required by /usr/bin/openssl)
linux-vdso.so.1 => (0x00007ffe6d1e3000)
libssl.so.1.0.0 => /usr/local/lib/libssl.so.1.0.0 (0x00007f8999827000)
libcrypto.so.1.0.0 => /usr/local/lib/libcrypto.so.1.0.0 (0x00007f89993ed000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f8999023000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f8998e1f000)
/lib64/ld-linux-x86-64.so.2 (0x00007f8999a97000)
After fix I provided:
linux-vdso.so.1 => (0x00007ffec39bc000)
libssl.so.1.0.0 => /lib/x86_64-linux-gnu/libssl.so.1.0.0 (0x00007f7faad22000)
libcrypto.so.1.0.0 => /lib/x86_64-linux-gnu/libcrypto.so.1.0.0 (0x00007f7faa8dd000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f7faa513000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f7faa30f000)
/lib64/ld-linux-x86-64.so.2 (0x00007f7faaf8b000)
edited Jun 7 at 20:21
answered Jun 7 at 20:12
ZEROFZEROF
11 bronze badge
11 bronze badge
For people with CentOS path, I think good file is /etc/ld.so.conf ;), just to be clear.
– ZEROF
Jun 7 at 20:16
add a comment |
For people with CentOS path, I think good file is /etc/ld.so.conf ;), just to be clear.
– ZEROF
Jun 7 at 20:16
For people with CentOS path, I think good file is /etc/ld.so.conf ;), just to be clear.
– ZEROF
Jun 7 at 20:16
For people with CentOS path, I think good file is /etc/ld.so.conf ;), just to be clear.
– ZEROF
Jun 7 at 20:16
add a comment |
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
add a comment |
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
add a comment |
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
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
answered Aug 11 '17 at 14:27
RafaelRafael
1011 bronze badge
1011 bronze badge
add a comment |
add a comment |
Thanks for contributing an answer to Server Fault!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f818445%2ferror-while-loading-shared-libraries-libcrypto-so-1-1%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
2
Sorry, you've run into yet another bad Internet tutorial. You might have to reinstall the system. Before going further, I suggest you ask about the original problem that you were trying to solve by doing this. There is probably a better way to accomplish the original goal.
– Michael Hampton♦
Dec 2 '16 at 20:01
I wanted to install Server Monitor application provided by Monitis. It needed some shared library dependencies which was not installed in my server. So, all this happened when was up to install those. :(
– mayasl
Dec 2 '16 at 20:19
@MichaelHampton Please tell me something except reinstalling the system. Because a live site is running on that server!
– mayasl
Dec 2 '16 at 20:29