Red Hat Bugzilla – Bug 1471722
systemd unit probably needs to have more requisites
Last modified: 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):
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
Asterisk starts but doesn't connect to SIP provider. Once booted, restarting Asterisk is successful.
Message such as:
[Jul 17 01:26:51] ERROR netsock2.c: getaddrinfo("sip.sip-provider.example.com", "(null)", ...): Name or service not known
Should restart and work without intervention. Shouldn't be name resolution errors in the log.
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.