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

[Danny Nicholas (JIRA)]

Danny Nicholas created ASTERISK-20962:
-----------------------------------------

             Summary: 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: 1.8.20.0
         Environment: CentOS 5.8
Kernel - 2.6.18-308.24.1.el5PAE

            Reporter: Danny Nicholas


Installed asterisk 1.8.19.1, worked fine. Installed 1.8.20.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}

I don't have any peers setup yet, or even any dialplan configured to test, but when I go through the logs, I don't find any errors or warnings that I'm not expecting.

I've gone back to the asterisk 1.8.19.1 install and everything works as expected (no error messages, full splash about license / version on connection to console, etc).  I performed make clean in my 1.8.20 source directory, then ./configure, make menuselect, make, make install, and even make config, and I'm still seeing this message pop up when restarting / starting the service. 

I went through the CHANGELOG.TXT for 1.8.20.0 and it appears there are some items talking about changing the way the process starts up (commit r376428), but I'm not enough of a coder to understand if those would cause what I'm seeing.  

--
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