Summary:	ASTERISK-25597: Remote console freeze after 'core stop gracefully' and then further command attempts
Reporter:	Tyler Cambron (tcambron)	Labels:
Date Opened:	2015-11-30 11:07:09.000-0600	Date Closed:
Priority:	Trivial	Regression?
Status:	Open/New	Components:	Core/General
Versions:	13.6.0	Frequency of Occurrence	Constant
Related Issues:	is related to ASTERISK-25646 CLI output after "core stop gracefully" on a remote console is confusing and inconsistent with root console behavior
Environment:		Attachments:
Description:	[edit by Rusty - I was able to reproduce this about one time out of twenty. It appears to me that the console freezes. This only appears to happen on a remote console (for me). I was able to reconnect with another console and run "core stop now" to stop Asterisk immediately. Though, I'm not sure that should be possible, or that we should expect any response to commands after running "core stop gracefully". It appears to be unimportant what channels are up or what they are doing, as long as Asterisk is still waiting to halt.] After placing two local channels into a confbridge, I used 'core stop gracefully' to try and shut down Asterisk. When I received no response, which might be expected since it is trying to be graceful, I tried a 'core stop now', but nothing happened. I then used 'core show channels' to see if my channels were still up, but Asterisk gave no response. After another minute or two, the command line was completely frozen and I could not even type. I then had to use killall to kill Asterisk. Here is my dialplan: {noformat} [default] exten => 100,1,NoOp()    same => n,StatsD(g,confBridgeUsers,+1,1)    same => n,Set(CHANNEL(hangup_handler_push)=default,200,1);    same => n,ConfBridge(1000)    same => n,StatsD(g,confBridgeUsers,-1,1)    same => n,Hangup() exten => 200,1,NoOp()    same => n,StatsD(g,confBridgeUsers,-1,1)    same => n,Hangup() {noformat}
Comments: