[asterisk-bugs] [JIRA] (ASTERISK-25646) CLI output after "core stop gracefully" on a remote console is confusing and different than that on root console

Rusty Newton (JIRA) noreply at issues.asterisk.org
Wed Dec 23 21:21:33 CST 2015


Rusty Newton created ASTERISK-25646:
---------------------------------------

             Summary: CLI output after "core stop gracefully" on a remote console is confusing and different than that on root console
                 Key: ASTERISK-25646
                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-25646
             Project: Asterisk
          Issue Type: Bug
      Security Level: None
            Reporter: Rusty Newton
            Severity: Trivial


h2. Behavior when running on a root console.

{noformat}
*CLI> core stop gracefully
Waiting for inactivity to perform halt...

{noformat}

If you attempt to run other commands after running "core stop gracefully" at the root console you get no response. Nor do you get returned to the CLI prompt.

{noformat}
*CLI> core stop gracefully
Waiting for inactivity to perform halt...

core show channels

{noformat}

This makes it pretty clear that no further commands are accepted. Though it would be nice if it said that.

h2. Behavior when running on a remote console.

{noformat}
CentOSLab*CLI> core stop gracefully
CentOSLab*CLI>
{noformat}

Running commands after "core stop gracefully" on a remote console results in a return to the CLI prompt. It appears as if the command is accepted, yet you receive no output in response to the commands.

{noformat}
CentOSLab*CLI> core show channels
CentOSLab*CLI>
{noformat}

This is confusing behavior and doesn't match what we see on the root console. 

Ideally the behavior would be the same between the two and the notification after command execution should be explicit about what to expect.

e.g. "Stopping gracefully. Waiting for all channels to hang up before halting. No further commands will be accepted."

I believe this has been this way for a while but I'm going to mark it as a bug since the behavior is confusing and (based on user reports) results in uncertainty as to the state of the system.



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



More information about the asterisk-bugs mailing list