Bug 1409524

Summary: Asterisk fails to start (error while loading shared libraries: libasteriskssl.so)
Product: [Fedora] Fedora Reporter: Chris <huor.carnesir>
Component: asteriskAssignee: Jared Smith <jsmith.fedora>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 25CC: bazanluis20, g.devel, itamar, jsmith.fedora, rbryant
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-12 10:18:28 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Chris 2017-01-02 11:45:50 UTC
Description of problem:
Asterisk doesn't start

Version-Release number of selected component (if applicable):
13.9.1-1.fc25.1

How reproducible:
always

Steps to Reproduce:
1. Install asterisk (e.g. dnf install asterisk)
2. Run asterisk (either systemctl start asterisk or just asterisk in a terminal)

Actual results:
Just an error message
asterisk: error while loading shared libraries: libasteriskssl.so: cannot open shared object file: No such file or directory

Expected results:
A running asterisk

Additional info:
It seems libasteriskssl.so is provided by asterisk-devel, which is not installed automatically with asterisk. The error persist after installing asterisk-devel tough.

ldd /usr/sbin/asterisk 
        linux-vdso.so.1 (0x00007ffe775b2000)
        libasteriskssl.so => not found
        libxml2.so.2 => /lib64/libxml2.so.2 (0x00007f41cde60000)
        libdl.so.2 => /lib64/libdl.so.2 (0x00007f41cdc5c000)
        libsqlite3.so.0 => /lib64/libsqlite3.so.0 (0x00007f41cd985000)
        libssl.so.10 => /lib64/libssl.so.10 (0x00007f41cd713000)
        libcrypto.so.10 => /lib64/libcrypto.so.10 (0x00007f41cd2b1000)
        libjansson.so.4 => /lib64/libjansson.so.4 (0x00007f41cd0a4000)
        libuuid.so.1 => /lib64/libuuid.so.1 (0x00007f41cce9f000)
        libcrypt.so.1 => /lib64/libcrypt.so.1 (0x00007f41ccc69000)
        libcap.so.2 => /lib64/libcap.so.2 (0x00007f41cca64000)
        libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f41cc846000)
        libm.so.6 => /lib64/libm.so.6 (0x00007f41cc53b000)
        libresolv.so.2 => /lib64/libresolv.so.2 (0x00007f41cc320000)
        libedit.so.0 => /lib64/libedit.so.0 (0x00007f41cc0e9000)
        libc.so.6 => /lib64/libc.so.6 (0x00007f41cbd23000)
        libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f41cbb0c000)
        libz.so.1 => /lib64/libz.so.1 (0x00007f41cb8f6000)
        liblzma.so.5 => /lib64/liblzma.so.5 (0x00007f41cb6ce000)
        /lib64/ld-linux-x86-64.so.2 (0x000055db287d3000)
        libgssapi_krb5.so.2 => /lib64/libgssapi_krb5.so.2 (0x00007f41cb481000)
        libkrb5.so.3 => /lib64/libkrb5.so.3 (0x00007f41cb19b000)
        libcom_err.so.2 => /lib64/libcom_err.so.2 (0x00007f41caf97000)
        libk5crypto.so.3 => /lib64/libk5crypto.so.3 (0x00007f41cad66000)
        libfreebl3.so => /lib64/libfreebl3.so (0x00007f41cab63000)
        libncurses.so.6 => /lib64/libncurses.so.6 (0x00007f41ca938000)
        libtinfo.so.6 => /lib64/libtinfo.so.6 (0x00007f41ca70c000)
        libkrb5support.so.0 => /lib64/libkrb5support.so.0 (0x00007f41ca4fd000)
        libkeyutils.so.1 => /lib64/libkeyutils.so.1 (0x00007f41ca2f9000)
        libselinux.so.1 => /lib64/libselinux.so.1 (0x00007f41ca0d2000)
        libpcre.so.1 => /lib64/libpcre.so.1 (0x00007f41c9e5d000)

Comment 1 Chris 2017-01-02 12:23:45 UTC
Seems the shared object is actually there, just the symlink libasteriskssl.so is missing.

cd /lib64/
ln -s libasteriskssl.so.1 libasteriskssl.so

fixes the issue. No need for the -devel package after all.

Comment 2 Chris 2017-01-17 21:45:15 UTC
Is somebody looking into this? It's not really a complicated one to fix but a rather severe bug since a stock asterisk installation will simply refuse to work.

Comment 3 Benny Amorsen 2017-11-15 08:57:34 UTC Comment hidden (spam)
Comment 4 Fedora End Of Life 2017-11-16 18:31:56 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 5 Fedora End Of Life 2017-12-12 10:18:28 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.