[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:all-tabpanel ]

George Joseph updated ASTERISK-26025:
-------------------------------------

    Status: Waiting for Feedback  (was: Open)

I finally got a chance to test this in a kickstart environment and I didn't have any problem starting asterisk.   My kickstart installs asterisk from RPM but I was able to ssh into the box before the reboot, chroot, and start asterisk as the asterisk user.  I then ssh'd again and ran asterisk -R.

What was the exact command used to create the asterisk user and group.
What's the exact command used to start asterisk.
What are the permissions on /var/run/asterisk or /run/asterisk, whichever you use?
Can you "su - asterisk" and do a "mksock /var/run/asterisk/test.ctl"?





A few things you can check...
permissions on var/run/asterisk  

> 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: George Joseph
>         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)