# Failed to execute in CentOS 8.3.2011

**URL:** <https://discourse.slicer.org/t/failed-to-execute-in-centos-8-3-2011/15310>\
**Category:** Support\
**Created:** [January 1, 2021, 8:12pm UTC](https://discourse.slicer.org/t/failed-to-execute-in-centos-8-3-2011/15310 "2021-01-01T20:12:15Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![endi](https://avatars.discourse-cdn.com/v4/letter/e/65b543/32.png) [@endi](https://discourse.slicer.org/u/endi)\
**Post date:** [January 1, 2021, 8:12pm UTC](https://discourse.slicer.org/t/failed-to-execute-in-centos-8-3-2011/15310/1 "2021-01-01T20:12:15Z")

</div>

I downloaded the latest stable release and was not able to get Slicer to execute. The error message received was

/u/software/slicer/Slicer-4.11.20200930-linux-amd64/bin/SlicerApp-real: error while loading shared libraries: libnsl.so.1: cannot open shared object file: No such file or directory

I was not able to download libnsl.slo.1 from the Centos 8 repos.

Does anyone on the list have Centos 8.3.2011 that might be able to help.

Thanks ahead of time!!!

Greg Ennis

---

<div class="post-metadata">

**Author:** ![endi](https://avatars.discourse-cdn.com/v4/letter/e/65b543/32.png) [@endi](https://discourse.slicer.org/u/endi)\
**Post date:** [January 1, 2021, 8:51pm UTC](https://discourse.slicer.org/t/failed-to-execute-in-centos-8-3-2011/15310/2 "2021-01-01T20:51:01Z")

</div>

The same results occurred with downloading the unstable release.  
/u/software/slicer/Slicer-4.13.0-2020-12-31-linux-amd64/bin/SlicerApp-real: error while loading shared libraries: libnsl.so.1: cannot open shared object file: No such file or directory

---

<div class="post-metadata">

**Author:** ![endi](https://avatars.discourse-cdn.com/v4/letter/e/65b543/32.png) [@endi](https://discourse.slicer.org/u/endi)\
**Post date:** [January 1, 2021, 9:07pm UTC](https://discourse.slicer.org/t/failed-to-execute-in-centos-8-3-2011/15310/3 "2021-01-01T21:07:16Z")

</div>

> [@endi](#):
>
> libnsl.so.1

I found BUG # 1814151  
[https://bugzilla.redhat.com/show\_bug.cgi?id=1814151](https://bugzilla.redhat.com/show_bug.cgi?id=1814151)

After installing libnsl via  
dnf install libnsl

I was still unable to use Slice  
u/software/slicer/Slicer-4.13.0-2020-12-31-linux-amd64/bin/SlicerApp-real: symbol lookup error:/lib64/libk5crypto.so.3: undefined symbol: EVP\_KDF\_ctrl, version OPENSSL\_1\_1\_1b

---

<div class="post-metadata">

**Author:** ![endi](https://avatars.discourse-cdn.com/v4/letter/e/65b543/32.png) [@endi](https://discourse.slicer.org/u/endi)\
**Post date:** [January 1, 2021, 10:14pm UTC](https://discourse.slicer.org/t/failed-to-execute-in-centos-8-3-2011/15310/4 "2021-01-01T22:14:23Z")

</div>

Additional research identified the problem

> **[1829790 – libk5crypto.so.3: undefined symbol: EVP\_KDF\_ctrl, version...](https://bugzilla.redhat.com/show_bug.cgi?id=1829790)**

I deleted the libcrypto.so.1.1.s in the Slicer subdirectory and was able to get ./Slicer to execute.

Hope this is helpful to other Centos 8 users.

Greg

---

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [January 2, 2021, 12:49am UTC](https://discourse.slicer.org/t/failed-to-execute-in-centos-8-3-2011/15310/5 "2021-01-02T00:49:59Z")

</div>

@jcfr Is there anything we can do about this or we should just document this in linux install instructions as a workaround? Is there any better way of packaging than what we do now? Should we choose a few linux distributions that we officially support and let users build from source on all others?