Bug 1471722 - systemd unit probably needs to have more requisites
systemd unit probably needs to have more requisites
Status: NEW
Product: Fedora EPEL
Classification: Fedora
Component: asterisk (Show other bugs)
epel7
All Linux
unspecified Severity urgent
: ---
: ---
Assigned To: Jared Smith
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-07-17 06:42 EDT by Brian J. Murrell
Modified: 2017-07-17 06:42 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Brian J. Murrell 2017-07-17 06:42:48 EDT
Description of problem:
On system reboot, Asterisk does not start properly.  Typically SIP channels are unconnected.

Version-Release number of selected component (if applicable):
asterisk-13.11.1-1.el7

How reproducible:
100%

Steps to Reproduce:
1. Build from https://src.fedoraproject.org/cgit/rpms/asterisk.git/ on EL7
2. Configure, including a SIP channel, using hostname(s) for the target
3. Reboot system

Actual results:
Asterisk starts but doesn't connect to SIP provider.  Once booted, restarting Asterisk is successful.
Message such as:
[Jul 17 01:26:51] ERROR[4193] netsock2.c: getaddrinfo("sip.sip-provider.example.com", "(null)", ...): Name or service not known

Expected results:
Should restart and work without intervention.  Shouldn't be name resolution errors in the log.

Additional info:
I suspect that the system unit file for Asterisk probably needs to wait for more services to be up before allowing Asterisk to be started.  At minimum, I would think you want any name resolution services up.

Note You need to log in before you can comment on or make changes to this bug.