5

Im having an issue on my aws instance, After running spl-token with any arg, I get the following error

spl-token: error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such file or directory

I thought that maybe it has somethin to do with my shared libraries,

so after running ldconfig -p | grep libssl

This is what I get

        libssl3.so (libc6,x86-64) => /lib/x86_64-linux-gnu/libssl3.so
        libssl.so.3 (libc6,x86-64) => /lib/x86_64-linux-gnu/libssl.so.3
        libssl.so (libc6,x86-64) => /lib/x86_64-linux-gnu/libssl.so

What I notice is that there is no libssl.so.1.1 listed, does that account for the error?

So next I searched for how to add libssl.so.1.1 to the shared libs, I found an article saying you have to edit /etc/ld.so.conf.d/.conf and add the path to the lib. So I created the file and added the path /snap/core18/2344/usr/lib/x86_64-linux-gnu/libssl.so.1.1.

No success

plutoniumApples
  • 59
  • 1
  • 1
  • 3
  • It looks like you also created the issue on GitHub about this. Please avoid cross-posting between different places. I'll paste my answer here so it's more available. – Jon C May 25 '22 at 16:26
  • 1
    I try this solution https://askubuntu.com/questions/1403778/upgrading-to-ubuntu-22-04-causes-libcrypto-errors-apt-dpkg-broken And it works fine for me – G. Sofien May 28 '22 at 00:50
  • Does this answer your question? [libssl.so.1.1: cannot open shared object file: No such file or directory](https://stackoverflow.com/questions/72133316/libssl-so-1-1-cannot-open-shared-object-file-no-such-file-or-directory) – David Maze Feb 13 '23 at 11:43

2 Answers2

2

This fixes it (a problem with packaging in 22.04):

wget http://nz2.archive.ubuntu.com/ubuntu/pool/main/o/openssl/libssl1.1_1.1.1l-1ubuntu1.6_amd64.deb

sudo dpkg -i libssl1.1_1.1.1l-1ubuntu1.6_amd64.deb

PS: If the link is expired, check http://nz2.archive.ubuntu.com/ubuntu/pool/main/o/openssl/?C=M;O=D for a valid one.

Koops
  • 422
  • 3
  • 11
  • ERROR 303: Not Found. :( – Kyle Baker Aug 02 '22 at 23:59
  • I would really recommend to use ubuntu lxd / lxc to play around with solana or the token cli. Your error is probably because the link has been depreciated. I really really recommed the lxd. Its basically a ubuntu virtual machine with only the minimal specs. You can remote ssh and play around with it without worrying about errors or messing up your machine. If you do, you can delete it and start again. – Koops Aug 06 '22 at 06:19
  • if you do, run it as a super user `lxc exec -- sudo -i` – Koops Aug 06 '22 at 06:21
  • I have no interest in the same context, I just wanted libssl1.1. I eventually found a different link with a deb available. Yes, this link died because of that version of ubuntu being deprecated, I was just putting the comment there for others to know. – Kyle Baker Aug 07 '22 at 23:31
-1

I managed to fix the issue by running everything locally rather than on my ec2 instance. I know its not the solution to the problem, but perhaps consider switching the environment as a solution

plutoniumApples
  • 59
  • 1
  • 1
  • 3