pacman depends on libcrypto.so.1.1

rmc · 2017-04-24 14:48:51

pacman depends on libcrypto.so.1.1 DO NOT upgrade pacman!!

At least for now.

If you do, pacman can't start because this version of the shared library is not installed.

Kind regards,
Rory McGuire

Repository : core
Name : pacman
Version : 5.0.1-5
Description : A library-based package manager with dependency support
Architecture : x86_64
URL : http://www.archlinux.org/pacman/
Licenses : GPL
Groups : base base-devel
Provides : pacman-contrib
Depends On : bash glibc libarchive curl gpgme pacman-mirrorlist
archlinux-keyring
Optional Deps : None
Conflicts With : pacman-contrib
Replaces : pacman-contrib
Download Size : 731.45 KiB
Installed Size : 4530.00 KiB
Packager : Pierre Schmitz <pierre@archlinux.de>
Build Date : Sat 11 Feb 2017 01:49:05 PM SAST
Validated By : MD5 Sum SHA-256 Sum Signature

Mod note: Removed alarmist title. --WorMzy

Last edited by WorMzy (2017-04-24 15:00:31)

Scimmia · 2017-04-24 14:53:43

If you updated your entire system like you're supposed to, that version of the library would be installed.

WorMzy · 2017-04-24 14:55:08

You should get an update for openssl during the same upgrade transaction (currently updating to 1.1.0.e-1). If you didn't, then your mirror is broken.

You can fix your system by updating it from a liveCD.

cfr · 2017-04-24 15:09:26

There was a problem with today's update in terms of synchronisation, though it did not affect pacman in my case. However, after updating the system, I had a boot failure due to lack of older libraries required for various things. Updating again and rebooting resolved the issue, but clearly I was lucky that pacman was not affected. (Especially since I don't have the liveCD or, for that matter, a CD drive. Presumably I could make a USB instead, though.)

Scimmia · 2017-04-24 15:13:36

AFAIK, most of the issues were with a very small lag between repos. Pacman should not be affected except in EXTREMELY rare cases, bad mirrors, or partial updates.

Norkos · 2017-04-24 15:40:45

Im ran into the same issue today and e.g. nodejs stopt working. Downgrade openssl from pacman cache worked as an hotfix for me.

How can i prevent this happening again?
I used Pamac, but was there any hint in the output of pacman?

Scimmia · 2017-04-24 15:45:35

Norkos wrote:

Im ran into the same issue today and e.g. nodejs stopt working. Downgrade openssl from pacman cache worked as an hotfix for me.
How can i prevent this happening again?
I used Pamac, but was there any hint in the output of pacman?

Completely different issue, and your "hotfix" probably broke a lot of other things.

aknarts · 2017-04-24 16:03:09

Scimmia wrote:

Norkos wrote:
Im ran into the same issue today and e.g. nodejs stopt working. Downgrade openssl from pacman cache worked as an hotfix for me.
How can i prevent this happening again?
I used Pamac, but was there any hint in the output of pacman?
Completely different issue, and your "hotfix" probably broke a lot of other things.

It was a valid solution to the issue, if you were able to do so and did a full system upgrade after this.

By the way I always do full system upgrade and still was hit by this issue, multiple packages broke, not just pacman.

Norkos · 2017-04-24 16:09:14

@Scimmia
This was my error: "node: error while loading shared libraries: libcrypto.so.1.0.0: cannot open shared object file: No such file or directory"
So yes other issue, but same reason, or?

Hotfix:
Yes, I know, but panic
When the mirror was synced I installed the openssl.1.1 again (from cache) and done than a upgrade (-Syu).
And now everything is fine again (at least it seems so)

Trilby · 2017-04-24 17:39:38

Norkos, that's a related problem - but actually the oposite. The OP here has a pacman upgrade without the corresponding openssl upgrade on his mirror. You received the openssl update but not a new nodejs.

It's all from the small lag Scimmia referred to (more specifically to some mirrors coincidentally last syncing *during* that lag period). The solution remains the same update your system with a recently synced mirror.

grism · 2017-04-24 20:40:27

I had the same issue as OP: "error while loading shared libraries: libcrypto.so.1.0.0: cannot open shared object file: No such file or directory"

To fix pacman I did the following:

I downloaded openssl from packages and did the following.
cd /tmp
tar xJf ~/Downloads/openssl-1.1.0.e-1-x86_64.pkg.tar.xz
cd /usr/lib
sudo ln -s /tmp/usr/lib/libcrypto.so.1.1 libcrypto.so.1.1
sudo pacman -U /var/cache/pacman/pkg/pacman-5.0.1-4-x86_64.pkg.tar.xz
sudo rm libcrypto.so.1.1

This made my pacman functional again. Lesson learned. Don't update pacman without deps.

Trilby · 2017-04-24 21:04:47

What? you deleted the lib at the last step? That would not work.

grism · 2017-04-24 21:28:45

It worked because I didn't actually install the library. I created a soft link temporarily in the lib path. Once I fixed pacman and resolved my original error and proceeded with my update pacman cleverly reminded me that I still had the temporary link in place.

I should also clarify that libcrypto.so.1.0 was still in /usr/lib and that is why forcing pacman back to the previous version worked.

Last edited by grism (2017-04-24 21:33:34)

Trilby · 2017-04-24 21:41:55

Oops, quite right. I misread that a bit. That still seems like an odd approach to me, but on second look it seems perfectly fine. I was thinking you put the symlink in place in order to upgrade the openssl package (not to downgrade pacman), then deleted the lib.

ZeroLinux · 2017-04-25 07:43:46

Now after the same issue and after recreating links manually to libcrypto and libssl I have a problem:

апр 25 10:36:51 zenbook systemd[1]: Stopped Simple Desktop Display Manager.
апр 25 10:36:51 zenbook systemd[1]: Started Simple Desktop Display Manager.
апр 25 10:36:51 zenbook sddm[1262]: /usr/bin/sddm: /usr/lib/libcrypto.so.1.0.0: version `OPENSSL_1.0.2d' not found (required by /usr/lib/libQt5Network.so.5)
апр 25 10:36:51 zenbook sddm[1262]: /usr/bin/sddm: /usr/lib/libssl.so.1.0.0: version `OPENSSL_1.0.2d' not found (required by /usr/lib/libQt5Network.so.5)
апр 25 10:36:51 zenbook systemd[1]: sddm.service: Main process exited, code=exited, status=1/FAILURE
апр 25 10:36:51 zenbook systemd[1]: sddm.service: Unit entered failed state.
апр 25 10:36:51 zenbook systemd[1]: sddm.service: Failed with result 'exit-code'.

$ sudo pacman -Q openssl
openssl 1.1.0.e-1

How can I fix it?

Last edited by ZeroLinux (2017-04-25 07:45:18)

jasonwryan · 2017-04-25 07:45:54

You have a thread, don't hijack and crosspost: https://wiki.archlinux.org/index.php/Co … _hijacking
https://wiki.archlinux.org/index.php/Co … ss-posting

ZeroLinux · 2017-04-25 07:51:58

jasonwryan wrote:

You have a thread, don't hijack and crosspost: https://wiki.archlinux.org/index.php/Co … _hijacking
https://wiki.archlinux.org/index.php/Co … ss-posting

Thanks. I am desperate. I'll try to avoid

rmc · 2017-04-25 10:38:29

WorMzy wrote:

You should get an update for openssl during the same upgrade transaction (currently updating to 1.1.0.e-1). If you didn't, then your mirror is broken.
You can fix your system by updating it from a liveCD.

Thanks, there was a part of my Dockerfile that only had `pacman -Sy` in it that explains that. I had checked on my main system after I saw the error and the update looked the same so I avoided it, and posted issue on forum.

With Docker I can just re-run the build, I posted in order to warn others and to find out what happened.

Thanks!

produnis · 2017-04-26 18:01:45

I crashed my system, so that every sudo, pacman or ssh command returns a

pacman: error while loading shared libraries: libcrypto.so.1.0.0: cannot open shared object file: No such file or directory
pacman: error while loading shared libraries: libssl.so.1.0.0: cannot open shared object file: No such file or directory

I fixed it by linking:

$ su root
$ cd /usr/lib

$ ln -s /var/lib/archbuild/multilib-x86_64/produnis/usr/lib/libcrypto.so.1.0.0 .
$ ln -s /var/lib/archbuild/multilib-x86_64/produnis/usr/lib/libssl.so.1.0.0 .

(where "produnis" is your username)

Last edited by produnis (2017-04-26 18:02:11)

Scimmia · 2017-04-26 18:08:19

Wow, that's one of the more horrible things I've seen. Don't do that.

produnis · 2017-04-26 18:17:05

I was able to run pacman und sudo again.
So, what I did after linking:

Terminal 1:

$ pacman -Syu
# (don't press "y" to install, yet)

Terminal 2:

$ rm /usr/lib/libcrypto.so.1.0.0 /usr/lib/libssl.so.1.0.0

Terminal 1:

Typ "y" to perform upgrade

This way I was able to upgarde via pacman, und it restored my system.

cfr · 2017-04-26 21:59:19

Trilby wrote:

It's all from the small lag Scimmia referred to (more specifically to some mirrors coincidentally last syncing *during* that lag period). The solution remains the same update your system with a recently synced mirror.

Is there any way of checking whether a mirror is recently synced before updating? Is this something I could ask pacman to check, for example?

Trilby · 2017-04-26 22:17:42

It's not something that normally matters. Again, it's really not the time from the last sync of the mirror, it's that some mirrors coincientally synced during the period when the repos were not quite right (I think core and/or extra were ahead of community briefly).

Opting for the most recent mirror will not protect one from such problems - it really was just a packaging snafu an not a normal occurrence. For example, if core and/or extra were not lined up with community between 1am and 2am, then at 1:59am, having the most recently synced mirror would actually be the cause of trouble, while having a mirror that had not synced in several hours would protect you from the problem. Those roles might reverse a couple hours later though.

In short, snafus like the one that led to the present problems are inherently unpredictable and are no more likely to affect more recently or less recently synced mirrors: they'd just be affected different times. Once the problem was known, then one would want a mirror that had synced after the problem was resolved, hence the advice to ensure mirrors were "recently" synced.

There are other reasons to keep your mirrors up to date, but that's what tools like reflector are for.

tjeffress · 2017-04-28 17:37:39

grism wrote:

I had the same issue as OP: "error while loading shared libraries: libcrypto.so.1.0.0: cannot open shared object file: No such file or directory"
To fix pacman I did the following:
I downloaded openssl from packages and did the following.
cd /tmp
tar xJf ~/Downloads/openssl-1.1.0.e-1-x86_64.pkg.tar.xz
cd /usr/lib
sudo ln -s /tmp/usr/lib/libcrypto.so.1.1 libcrypto.so.1.1
sudo pacman -U /var/cache/pacman/pkg/pacman-5.0.1-4-x86_64.pkg.tar.xz
sudo rm libcrypto.so.1.1
This made my pacman functional again. Lesson learned. Don't update pacman without deps.

Thank you! This took me in the right direction, although I had to also simlink the libssl package as well. I was worried I would have to do a complete reinstall to recover from this.

lesto · 2017-05-08 19:02:13

Trilby wrote:

It's not something that normally matters. Again, it's really not the time from the last sync of the mirror, it's that some mirrors coincientally synced during the period when the repos were not quite right (I think core and/or extra were ahead of community briefly).

Wouldn't this avoided if pacman would have specify the depency on the right version of openssl?

Arch Linux

#1 2017-04-24 14:48:51

pacman depends on libcrypto.so.1.1

#2 2017-04-24 14:53:43

Re: pacman depends on libcrypto.so.1.1

#3 2017-04-24 14:55:08

Re: pacman depends on libcrypto.so.1.1

#4 2017-04-24 15:09:26

Re: pacman depends on libcrypto.so.1.1

#5 2017-04-24 15:13:36

Re: pacman depends on libcrypto.so.1.1

#6 2017-04-24 15:40:45

Re: pacman depends on libcrypto.so.1.1

#7 2017-04-24 15:45:35

Re: pacman depends on libcrypto.so.1.1

#8 2017-04-24 16:03:09

Re: pacman depends on libcrypto.so.1.1

#9 2017-04-24 16:09:14

Re: pacman depends on libcrypto.so.1.1

#10 2017-04-24 17:39:38

Re: pacman depends on libcrypto.so.1.1

#11 2017-04-24 20:40:27

Re: pacman depends on libcrypto.so.1.1

#12 2017-04-24 21:04:47

Re: pacman depends on libcrypto.so.1.1

#13 2017-04-24 21:28:45

Re: pacman depends on libcrypto.so.1.1

#14 2017-04-24 21:41:55

Re: pacman depends on libcrypto.so.1.1

#15 2017-04-25 07:43:46

Re: pacman depends on libcrypto.so.1.1

#16 2017-04-25 07:45:54

Re: pacman depends on libcrypto.so.1.1

#17 2017-04-25 07:51:58

Re: pacman depends on libcrypto.so.1.1

#18 2017-04-25 10:38:29

Re: pacman depends on libcrypto.so.1.1

#19 2017-04-26 18:01:45

Re: pacman depends on libcrypto.so.1.1

#20 2017-04-26 18:08:19

Re: pacman depends on libcrypto.so.1.1

#21 2017-04-26 18:17:05

Re: pacman depends on libcrypto.so.1.1

#22 2017-04-26 21:59:19

Re: pacman depends on libcrypto.so.1.1

#23 2017-04-26 22:17:42

Re: pacman depends on libcrypto.so.1.1

#24 2017-04-28 17:37:39

Re: pacman depends on libcrypto.so.1.1

#25 2017-05-08 19:02:13

Re: pacman depends on libcrypto.so.1.1

Board footer