[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:42 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:42  
---------------------------------------------------------------------- 
Okay, I think there may be some miscommunication going on here. Any time
you use chan_agent, there's going to be a lot of locking that goes on. If
you have DETECT_DEADLOCKS turned on, you noticed that the CLI reported tons
of potential deadlocks. This happens simply when an agent is on the phone,
and unfortunately, this is actually by design.

When I referred to the deadlock reported, I meant the problem where you
attempted to reload app_queue and the CLI seemed completely unresponsive.
When this happens again, then that's when I need to see the core show locks
output. What you've given me appears to be the state of things when calls
are passing normally to agents. If I've not analyzed this correctly, please
let me know. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
05-30-08 10:42  putnopvut      Note Added: 0087551                          
======================================================================