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

[Richard Mudgett (JIRA)]

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

Richard Mudgett edited comment on ASTERISK-20945 at 1/17/13 11:07 AM:
----------------------------------------------------------------------

This issue also exists in 11.2.0.  The patch works for the splash screen, but still does not solve the /etc/init.d/asterisk start error.  I worked around this on my installation by replacing start() with this
{noformat}
start() {
        ###adjust file/directory permissions on each startup

#       echo "Initiating Start of Asterisk: "

#       echo -n "Adjusting file/directory permissions:                         "
#       . /etc/rc.d/init.d/asterisk-permissions && echo "OK" || echo "FAILED"

#       echo -n "Setting ulimits:                                              "
        ulimit -n 32768 -c unlimited && echo  "" || echo "FAILED"

        # Start daemons.
        echo -n $"Starting asterisk: "
        ASTARGS="-g "
        if [ -f $SAFE_ASTERISK ] ; then
                DAEMON=$SAFE_ASTERISK
                ASTARGS="-g "
        fi
#       if [ $AST_USER ] ; then
#               ASTARGS="-U $AST_USER"
#       fi
#       if [ $AST_GROUP ] ; then
#               ASTARGS="$ASTARGS -G $AST_GROUP"
#       fi
        if [ $AST_CONFIG ]; then
                ASTARGS="$ASTARGS -C $AST_CONFIG"
        fi
### here we go!
        $DAEMON $ASTARGS
        RETVAL=$?
        [ $RETVAL -eq 0 ] && touch /var/lock/subsys/asterisk
        echo

#       echo -n "decrease the verbosity level to zero:                         "
        $DAEMON -rx 'set verbose 0' > /dev/null &2>1 && echo  "" || echo "FAILED"
        return $RETVAL
}
{noformat}

                
      was (Author: sethsdad):
    This issue also exists in 11.2.0.  The patch works for the splash screen, but still does not solve the /etc/init.d/asterisk start error.  I worked around this on my installation by replacing start() with this
start() {
        ###adjust file/directory permissions on each startup

#       echo "Initiating Start of Asterisk: "

#       echo -n "Adjusting file/directory permissions:                         "
#       . /etc/rc.d/init.d/asterisk-permissions && echo "OK" || echo "FAILED"

#       echo -n "Setting ulimits:                                              "
        ulimit -n 32768 -c unlimited && echo  "" || echo "FAILED"

        # Start daemons.
        echo -n $"Starting asterisk: "
        ASTARGS="-g "
        if [ -f $SAFE_ASTERISK ] ; then
                DAEMON=$SAFE_ASTERISK
                ASTARGS="-g "
        fi
#       if [ $AST_USER ] ; then
#               ASTARGS="-U $AST_USER"
#       fi
#       if [ $AST_GROUP ] ; then
#               ASTARGS="$ASTARGS -G $AST_GROUP"
#       fi
        if [ $AST_CONFIG ]; then
                ASTARGS="$ASTARGS -C $AST_CONFIG"
        fi
### here we go!
        $DAEMON $ASTARGS
        RETVAL=$?
        [ $RETVAL -eq 0 ] && touch /var/lock/subsys/asterisk
        echo

#       echo -n "decrease the verbosity level to zero:                         "
        $DAEMON -rx 'set verbose 0' > /dev/null &2>1 && echo  "" || echo "FAILED"
        return $RETVAL
}

                  
> "Unable to connect to remote asterisk" message on service asterisk start, even though service is running
> --------------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-20945
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-20945
>             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: Warren Selby
>         Attachments: ASTERISK-20945-1.8-mjordan.diff, asterisk-20945-remote-intro-msg.diff
>
>
> 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