You are not logged in.

#1 2019-11-16 09:11:06

callmelord
Member
Registered: 2019-11-16
Posts: 5

nodejs can't running after upgrade

sudo hexo
node: /usr/local/lib/libcrypto.so.1.1: version `OPENSSL_1_1_1b' not found (required by node)

how to solve it
thanks

Offline

#2 2019-11-16 09:16:52

arojas
Developer
From: Spain
Registered: 2011-10-09
Posts: 1,645

Re: nodejs can't running after upgrade

Remove the openssl that you installed manually and use the official package

Offline

#3 2019-11-16 09:33:15

callmelord
Member
Registered: 2019-11-16
Posts: 5

Re: nodejs can't running after upgrade

arojas wrote:

Remove the openssl that you installed manually and use the official package

I use the official package, like pacman -S openssl, but nothing changed.

Last edited by callmelord (2019-11-16 09:47:04)

Offline

#4 2019-11-16 10:32:53

ayekat
Member
Registered: 2011-01-17
Posts: 1,359
Website

Re: nodejs can't running after upgrade

/usr/local/lib/libcrypto.so.1.1 is certainly not installed by a package.


{,META,RE}PKGBUILDSpacman-hacks (includes makemetapkg and remakepkg) │ dotfiles

Offline

#5 2019-11-16 10:39:03

callmelord
Member
Registered: 2019-11-16
Posts: 5

Re: nodejs can't running after upgrade

ayekat wrote:

/usr/local/lib/libcrypto.so.1.1 is certainly not installed by a package.

I know what you mean, But /usr/local/lib/libcrypto.so.1.1 is existed, why /usr/local/lib/libcrypto.so.1.1: version `OPENSSL_1_1_1b' not found (required by node).

Last edited by callmelord (2019-11-16 10:39:42)

Offline

#6 2019-11-16 10:47:47

ayekat
Member
Registered: 2011-01-17
Posts: 1,359
Website

Re: nodejs can't running after upgrade

/usr/local/lib/libcrypto.so.1.1: version `OPENSSL_1_1_1b' not found (required by node)

Is that the exact error message? What is the command you run?

I know what you mean,

I'll be a bit snarky and claim you don't. Where does that file come from? Why is it there? Why do you want to keep a file around that is not installed by any Arch Linux package, given that it obviously causes issues?

I don't know what npm does, or why it would even use that file there (/usr/local/lib is actually not checked by the dynamic loader AFAIK, so you or something else sets a custom LD_LIBRARY_PATH, or something was just installed that way). It's difficult to tell what's going on for software you have installed manually, through some other means than the distribution's package manager, because nobody can reproduce that problem, and so nobody can help you beyond "remove that file".


{,META,RE}PKGBUILDSpacman-hacks (includes makemetapkg and remakepkg) │ dotfiles

Offline

#7 2019-11-16 11:05:04

callmelord
Member
Registered: 2019-11-16
Posts: 5

Re: nodejs can't running after upgrade

I'll be a bit snarky and claim you don't. Where does that file come from? Why is it there? Why do you want to keep a file around that is not installed by any Arch Linux package, given that it obviously causes issues?

Sorry,"I know what you mean" is that I understand what kind of information you convery to me, not that I want to express my understanding of this. I really dont understand these so I ask for help from you. Thank you very much for your help, and I apologize for the sentence I said.

Last edited by callmelord (2019-11-16 11:05:58)

Offline

#8 2019-11-16 12:12:03

callmelord
Member
Registered: 2019-11-16
Posts: 5

Re: nodejs can't running after upgrade

I remove libcrypto.so.1.1 underunder /usr/local/lib, it works.
The file was found, but the version number is different, so there is a conflict.

Offline

Board footer

Powered by FluxBB