[asterisk-bugs] [JIRA] (ASTERISK-26025) core: Asterisk doesn't start correctly in kickstart post-install script

[George Joseph (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-26025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=230755#comment-230755 ] 

George Joseph commented on ASTERISK-26025:
------------------------------------------

I should be able to test this tonight but IIRC it had something to do with /dev or /sys not being fully populated.  The ctl file is a socket unlike the pid file which is a plain file, so there's more to it than just having permissions to create an entry in the directory.


> core: Asterisk doesn't start correctly in kickstart post-install script
> -----------------------------------------------------------------------
>
>                 Key: ASTERISK-26025
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26025
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/General
>    Affects Versions: 13.9.1
>         Environment: Scientific Linux (RHEL) 6.7
>            Reporter: Michael Newton
>            Assignee: Unassigned
>         Attachments: full
>
>
> Our provisioning process includes a Kickstart post script that compiles, installs, and starts Asterisk before installing FreePBX. This works very well under Asterisk 11 but fails under Asterisk 13. The FreePBX installer attempts to run {{asterisk -rx 'core show version'}} before installation, and complains that it cannot.
> Investigating this failure, I found that Asterisk starts up, but does not create {{/var/run/asterisk/asterisk.ctl}} so no remote connections can be created. I've verified that {{/var/run/asterisk/asterisk.pid}} is created, and the output from {{ps}} shows that Asterisk continues running. Setting the Asterisk logging level to debug shows no errors occurring at startup.
> Once the server is rebooted, and no longer in Kickstart, the control file is created without issue.



--
This message was sent by Atlassian JIRA
(v6.2#6252)