[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:50 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 10:50  
---------------------------------------------------------------------- 
Ok, you're right. In that case, the last two cores (gdb) I attached are the
ones that you should look at. They happened on 1.20.1

Regarding core show locks, since it crashes, I don't have a way to get on
the CLI for core show locks. Also, I can't tell about the locks being
normal locks or "deadlocks"? Because on the CLI, when I had detect_deadlock
on, 10 out of 10 lock lines that showed up had Deadlock written in there. I
think I put it down in the pastebin as well. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
05-30-08 10:50  Yourname       Note Added: 0087552                          
======================================================================