Arch Linux

jungliztik

Member

From: UK

Registered: 2017-04-13

Posts: 7

[Solved] New install - loading shared libraries: libssl.so.1.1

Hello,

I've just replaced my previous arch install after getting a new storage device and the install all went smoothly.

One thing I have been getting several times on the new build is complaints ' error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such file or directory'.  I got this after installing and attempting to launch virtualbox and now when attempting to launch siege.  The virtualbox scenario was resolved by removing the package (which was installed using pacman) and then installing the virtualbox-bin package using yaourt.

I have openssl 1.0.2k installed:

djs@penguin# openssl version                                                                                                                                                       8:21
OpenSSL 1.0.2k  26 Jan 2017 

I've tried using strace to determine where it's hitting issues:

djs@penguin# strace -e open siege                                                                                                                                                                                                         8:27
open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
open("/usr/lib/libpthread.so.0", O_RDONLY|O_CLOEXEC) = 3
open("/usr/lib/tls/x86_64/libssl.so.1.1", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
open("/usr/lib/tls/libssl.so.1.1", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
open("/usr/lib/x86_64/libssl.so.1.1", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
open("/usr/lib/libssl.so.1.1", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
siege: error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such file or directory
+++ exited with 127 +++
zsh: exit 127   strace -e open siege

Looking under /usr/lib for packages named 'libssl*', I could see the following:

djs@penguin# sudo find /usr/lib/ -iname 'libssl*'                                                                                                                                                                                         8:29
/usr/lib/pkgconfig/libssl.pc
/usr/lib/libssl.so
/usr/lib/libssl.so.1.0.0
/usr/lib/libssl3.so

I looked at creating symlinks to see if I could bypass/fool the system (I hate this prospect, consider it to be hacky but in an attempt to progress on with my task, thought it worth a go).... So I created two new symlinks:

[root@penguin lib]# ln -s libssl.so.1.0.0 libssl.so.1.1
[root@penguin lib]# ln -s libcrypto.so.1.0.0 libcrypto.so.1.1

However, while this removed the error and allowed siege to 'start', it still wouldn't actually allow me to do anything (as expected).  I have subsequently removed the symlinks which I created.

Any thoughts or help would be really appreciated.

Last edited by jungliztik (2017-04-13 13:02:59)

arojas

Developer

From: Spain

Registered: 2011-10-09

Posts: 2,098

Re: [Solved] New install - loading shared libraries: libssl.so.1.1

Please post your pacman.conf

jungliztik

Member

From: UK

Registered: 2017-04-13

Posts: 7

Re: [Solved] New install - loading shared libraries: libssl.so.1.1

Sure.

djs@penguin# cat /etc/pacman.conf                                                                                                                                                                                                         8:51
#
# /etc/pacman.conf
#
# See the pacman.conf(5) manpage for option and repository directives

#
# GENERAL OPTIONS
#
[options]
# The following paths are commented out with their default values listed.
# If you wish to use different paths, uncomment and update the paths.
#RootDir     = /
#DBPath      = /var/lib/pacman/
#CacheDir    = /var/cache/pacman/pkg/
#LogFile     = /var/log/pacman.log
#GPGDir      = /etc/pacman.d/gnupg/
#HookDir     = /etc/pacman.d/hooks/
HoldPkg     = pacman glibc
#XferCommand = /usr/bin/curl -C - -f %u > %o
#XferCommand = /usr/bin/wget --passive-ftp -c -O %o %u
#CleanMethod = KeepInstalled
#UseDelta    = 0.7
Architecture = auto

# Pacman won't upgrade packages listed in IgnorePkg and members of IgnoreGroup
#IgnorePkg   =
#IgnoreGroup =

#NoUpgrade   =
#NoExtract   =

# Misc options
#UseSyslog
#Color
#TotalDownload
CheckSpace
#VerbosePkgLists

# By default, pacman accepts packages signed by keys that its local keyring
# trusts (see pacman-key and its man page), as well as unsigned packages.
SigLevel    = Required DatabaseOptional
LocalFileSigLevel = Optional
#RemoteFileSigLevel = Required

# NOTE: You must run `pacman-key --init` before first using pacman; the local
# keyring can then be populated with the keys of all official Arch Linux
# packagers with `pacman-key --populate archlinux`.

#
# REPOSITORIES
#   - can be defined here or included from another file
#   - pacman will search repositories in the order defined here
#   - local/custom mirrors can be added here or in separate files
#   - repositories listed first will take precedence when packages
#     have identical names, regardless of version number
#   - URLs will have $repo replaced by the name of the current repo
#   - URLs will have $arch replaced by the name of the architecture
#
# Repository entries are of the format:
#       [repo-name]
#       Server = ServerName
#       Include = IncludePath
#
# The header [repo-name] is crucial - it must be present and
# uncommented to enable the repo.
#

# The testing repositories are disabled by default. To enable, uncomment the
# repo name header and Include lines. You can add preferred servers immediately
# after the header, and they will be used before the default mirrors.

#[testing]
#Include = /etc/pacman.d/mirrorlist

[core]
Include = /etc/pacman.d/mirrorlist

[extra]
Include = /etc/pacman.d/mirrorlist

[community-testing]
Include = /etc/pacman.d/mirrorlist

[community]
Include = /etc/pacman.d/mirrorlist

# If you want to run 32 bit applications on your x86_64 system,
# enable the multilib repositories as required here.

#[multilib-testing]
#Include = /etc/pacman.d/mirrorlist

[multilib]
Include = /etc/pacman.d/mirrorlist

# An example of a custom package repository.  See the pacman manpage for
# tips on creating your own repositories.
#[custom]
#SigLevel = Optional TrustAll
#Server = file:///home/custompkgs

hcjl

Member

From: berlin

Registered: 2007-06-29

Posts: 330

Re: [Solved] New install - loading shared libraries: libssl.so.1.1

why do you have community-testing repo enabled?

Last edited by hcjl (2017-04-13 12:31:23)

jungliztik

Member

From: UK

Registered: 2017-04-13

Posts: 7

Re: [Solved] New install - loading shared libraries: libssl.so.1.1

Off hand, I cannot remember!

I backed up my old machine and in the attempt to expedite getting back up and running (this is my work machine), I copied the file into the new installation.  *balls*  I'm guessing that could be a culprit?

Slithery

Administrator

From: Norfolk, UK

Registered: 2013-12-01

Posts: 5,776

Re: [Solved] New install - loading shared libraries: libssl.so.1.1

If you have [community-testing] enabled then you need to enable [testing] as well, you have to enable both or neither.

---

No, it didn't "fix" anything. It just shifted the brokeness one space to the right. - jasonwryan
Closing -- for deletion; Banning -- for muppetry. - jasonwryan

aur - dotfiles

jungliztik

Member

From: UK

Registered: 2017-04-13

Posts: 7

Re: [Solved] New install - loading shared libraries: libssl.so.1.1

OK, thank you.  I'm going to err on the side of caution and remove the testing repository.

jungliztik

Member

From: UK

Registered: 2017-04-13

Posts: 7

Re: [Solved] New install - loading shared libraries: libssl.so.1.1

Bingo!
Having commented out the [community-testing] entry in pacman.conf, run

sudo pacman -Syy

and then reinstalled the siege package with

sudo pacman -S siege

, it all appears to be working! :-)  (I appreciate that the reinstall may have been necessary but I wanted to be thorough)

Thank you very much to everyone who answered and helped get this fixed for me!

WorMzy

Forum Moderator

From: Scotland

Registered: 2010-06-16

Posts: 11,858

Website

Re: [Solved] New install - loading shared libraries: libssl.so.1.1

In that case make sure to roll back your system to non-testing packages: https://wiki.archlinux.org/index.php/Of … positories

And please remember to mark your thread as solved by editing the first post and amending the topic title.

---

Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.