[asterisk-bugs] [Asterisk 0012709]: reload stops all action on CLI

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12709 
====================================================================== 
Reported By:                Yourname
Assigned To:                putnopvut
====================================================================== 
Project:                    Asterisk
Issue ID:                   12709
Category:                   Applications/app_cdr
Reproducibility:            random
Severity:                   crash
Priority:                   normal
Status:                     assigned
Asterisk Version:           1.4.18 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             05-22-2008 23:02 CDT
Last Modified:              05-30-2008 13:45 CDT
====================================================================== 
Summary:                    reload stops all action on CLI
Description: 
Mailing list:
http://lists.digium.com/pipermail/asterisk-users/2008-May/212281.html

After doing a few changes in queues.conf, I tried reload app_queue.so,
nothing happened on CLI. So I tried reload, and nothing happened. Something
similar happened to be long ago, and from then I knew something bad is
going to happen like no calls can come in or go out, agents login or out,
etc..

These commands go by and NOTHING happens on the CLI. Even stop now didn't
work. So I ctrl+c out of the CLI and then 'service asterisk stop'. Seems
like it did, but on the shell it kept doing the "Asterisk died with
code..." 

So I attempted to stop asterisk again, and also tried killall asterisk.
Finally it all worked, and then I safe_asterisk'd. Been scared to reload
ever since.
====================================================================== 

---------------------------------------------------------------------- 
 Yourname - 05-30-08 13:45  
---------------------------------------------------------------------- 
Gotcha
Let me address your para http://bugs.digium.com/view.php?id=2.
I tried doing the core show locks way back when this actually happened,
nothing worked. And I opened a new CLI, that didn't help either. 

The first 2 backtraces I uploaded were not enabled with DO_CRASH. So those
will be helpful to you. However, they were on 1.4.18.
And then someone told me to enable DO_CRASH, and that's the 3rd bt that I
submitted. Then, Corydon asked for core show locks, and that's the 4th
file. 

Finally, I tried updating, and coming to 1.4.20.1, I still noticed the
deadlocks. (Now I know about the reasons) I don't remember if DOCRASH was
still enabled.

...and as they say, rest is history.
Summary: First two files should show you some good info, but they were on
1.4.18.1 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
05-30-08 13:45  Yourname       Note Added: 0087566                          
======================================================================