[asterisk-bugs] [JIRA] (ASTERISK-20962) CLONE - "Unable to connect to remote asterisk" message on service asterisk start, even though service is running

[Matt Jordan (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-20962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt Jordan closed ASTERISK-20962.
----------------------------------

    Resolution: Duplicate
    
> CLONE - "Unable to connect to remote asterisk" message on service asterisk start, even though service is running
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-20962
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-20962
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/General
>    Affects Versions: 11.2.0
>         Environment: Suse Enterprise 11.0
> 2.6.32.12-0.7-default #1 SMP 2010-05-20 11:14:20 +0200 x86_64 x86_64 x86_64 GNU/Linux
>            Reporter: Danny Nicholas
>
> Installed asterisk 11.0.0, worked fine. Installed 11.2.0, and started seeing the following issues, with the same config files for both:
> When I start the asterisk service using "service asterisk start" from the command line, this is the output:
> {noformat}
> [root at pbx ~]# service asterisk start
> Unable to connect to remote asterisk (does /var/run/asterisk/asterisk.ctl exist?)
> Starting asterisk:
> {noformat}
> However, the /var/run/asterisk/asterisk.ctl file is being created and the process is starting:
> {noformat}
> [root at pbx ~]# ls -lh /var/run/asterisk/
> total 4.0K
> srwxr-xr-x 1 root root 0 Jan 16 12:07 asterisk.ctl
> -rw-r--r-- 1 root root 6 Jan 16 12:07 asterisk.pid
> {noformat}
> However, I'm no longer getting the usual splash message when I connect to the asterisk console...this is what I get:
> {noformat}
> [root at pbx ~]# asterisk -r
> Verbosity is at least 3
> pbx*CLI>
> {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira