[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 10:15 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.
====================================================================== 

---------------------------------------------------------------------- 
 putnopvut - 05-30-08 10:15  
---------------------------------------------------------------------- 
The initial problem you reported sounds like a deadlock to me. The core
show locks output when this happens will probably be most useful. I realize
that you've already submitted a core show locks from 1.4.18, but
considering that the output of the command has been modified to be more
specific and not give as many potentially spurious pieces of information,
it would be very helpful if I saw this output from 1.4.20.1 since it sounds
like that's what you're using now.