How do I fix error while loading shared libraries Libssl.so.1.1

root@localhost:~# spl-token create-token
spl-token: error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such file or directory

3 Replies

This happens most often when you update something and libssl.so gets updated. The name gets changed from libssl.so.1.1 to libssl.so.m.n (where m,n are not both 1).

Go to /usr/lib and make a symlink called libssl.so.1.1 to the libssl.so that you have:

cd /usr/lib
sudo ln -s libssl.so libssl.so.1.1

spl-token shouldn't be looking for libssl.so.1.1 in the first place. It should be looking for libssl.so…which is (usually) already a symlink to the right thing. The system and/or package update facility takes care of making sure that libssl.so points to the correct libssl.so.m.n.

You should report this as a defect.

-- sw

Go to /usr/lib and make a symlink called libssl.so.1.1 to the libssl.so that you have:

how do i know the libssl.so.m.n that i have? how do i go to /usr/lib?

how do i know the libssl.so.m.n that i have? how do i go to /usr/lib?

cd /usr/lib
ls -l libssl*

You should see a file called libssl.so.m.n (where {m,n} are each numbers in the range of 0..9).

-- sw

Reply

Please enter an answer
Tips:

You can mention users to notify them: @username

You can use Markdown to format your question. For more examples see the Markdown Cheatsheet.

> I’m a blockquote.

I’m a blockquote.

[I'm a link] (https://www.google.com)

I'm a link

**I am bold** I am bold

*I am italicized* I am italicized

Community Code of Conduct