https://bugzilla.novell.com/show_bug.cgi?id=752951 https://bugzilla.novell.com/show_bug.cgi?id=752951#c0 Summary: network:telephony:asterisk-1_8/asterisk: systemd can't handle asterisk due to pid-file path mismatch Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: All OS/Version: openSUSE 12.1 Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software AssignedTo: jengelh@medozas.de ReportedBy: Yarny@public-files.de QAContact: opensuse-communityscreening@forge.provo.novell.com CC: michael.kromer@millenux.com Found By: Other Blocker: No After starting the asterisk process, systemd waits for a pid-file in /var/run/asterisk.pid. I think systemd gets this idea from the comments of /etc/init.d. Line 9 reads
# pidfile: /var/run/asterisk.pid and I couln't find any other place where systemd might find this path. Unfortunatelly, /etc/asterisk/asterisk.conf contains the configuration line astrundir => /run/asterisk causing asterisk to create the pidfile in /run/asterisk instead. After 180 seconds, the service startup times out and asterisk.service enters the failed state.
Remark: Fixing the "# pidfile:" line in /etc/init.d/asterisk apparently fixes the bug, however, starting asterisk now causes another irritating message in /var/log/messages:
... systemd[1]: asterisk.service: Supervising process 1234 which is not our child. We'll most likely not notice when it exits. This is maybe caused by the safe_asterisk mechanism ..?
-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.