bcftools: error while loading shared libraries: libcrypto.so.1.0.0: cannot open shared object file: No such file or directory
3
1
Entering edit mode
3 months ago
Michal Nevo ▴ 30

Hello,

I have samtools version 1.12 h9aed4be_1 bioconda

I have installed bcftools version 1.8 h4da6232_3 bioconda

and when I try to run bcftools I get :

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

My channels order is:

conda config --show channels channels:

  • conda-forge
  • bioconda
  • defaults
  • nvidia

what can I do?

bcftools libcrypto.so.1.0.0 • 2.3k views
ADD COMMENT
0
Entering edit mode

what does

ldconfig -p | grep libcrypto

tell you?

ADD REPLY
0
Entering edit mode

ldconfig -p | grep libcrypto

    libcrypto.so.10 (libc6,x86-64) => /lib64/libcrypto.so.10
    libcrypto.so.1.1 (libc6,x86-64) => /lib64/libcrypto.so.1.1
    libcrypto.so (libc6,x86-64) => /lib64/libcrypto.so
ADD REPLY
0
Entering edit mode

did you try jared.andrews07 's installation instructions?

ADD REPLY
1
Entering edit mode

I am working with a remote server of the university so I don't have the option to use sudo apt .. I usually use conda install

ADD REPLY
0
Entering edit mode

I tried ...conda install -c anaconda openssl

ADD REPLY
3
Entering edit mode
3 months ago
Carambakaracho ★ 2.7k

I can't believe this never bit me, this bug has quite a discussion on github, this comment might have a solution for you:

conda install -c bioconda samtools openssl=1.0

Otherwise you might be able to link the newer library to the older version, as suggested a bit earlier in above linked discussion

ADD COMMENT
2
Entering edit mode

Nice find. There is also mamba, which is both (much) faster than conda and more adept at resolving conflicts like this. It often resolves many conda issues out of the box.

ADD REPLY
0
Entering edit mode

Yes, I am familiar with this discussion and I have tried all the suggestions mentioned there. The only thing that helped me is to create a new environment and reinstall everything ..

ADD REPLY
3
Entering edit mode
3 months ago

Is there a reason you are using bcftools 1.8 from three years ago?

If you install samtools and bcftools afresh today:

conda create -n sambcfenv samtools bcftools

then you get up to date versions of samtools and bcftools (1.13, released last week) with fewer bugs and more features. They have been built recently with the current conda packages and are free from this libcrypto problem, which is a thing of the past.

ADD COMMENT
0
Entering edit mode

Thank you!! I just created a new environment and it works :)

ADD REPLY
0
Entering edit mode

Hi, I am also running into this issue now, but for some reason, even this doesn't seem to fix it anymore. When I create a new environment with just bcftools, then bcftools works (but it's still version 1.8; I won't upgrade to 1.13). But when I create a new environment just like you said, it still gives me this libcrypto problem. I can create a separate environment for every step in my pipeline, but for now, I prefer for it all to be in the same environment. Any new tips that might fix this?

ADD REPLY
2
Entering edit mode

If you are getting bcftools 1.8, it's probably because you do not have the conda-forge channel added. See bioconda's channel setup instructions.

ADD REPLY
0
Entering edit mode

That was it, thank you!

ADD REPLY
0
Entering edit mode
3 months ago

You're probably missing libssl1.0.0. Install via sudo apt-get install libssl1.0.0 libssl-dev (on linux).

ADD COMMENT

Login before adding your answer.

Traffic: 1856 users visited in the last hour
Help About
FAQ
Access RSS
API
Stats

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.

Powered by the version 2.3.6