[asterisk-bugs] [Asterisk 0010019]: Asterisk hang/stop working on console suspend

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=10019 
====================================================================== 
Reported By:                darren1713
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   10019
Category:                   Core/General
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
Asterisk Version:           1.4.4 
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!):  
Disclaimer on File?:        Yes 
Request Review:              
====================================================================== 
Date Submitted:             06-20-2007 10:25 CDT
Last Modified:              03-31-2008 04:19 CDT
====================================================================== 
Summary:                    Asterisk hang/stop working on console suspend
Description: 
Reproduce problem:
1) Start screen "screen"
2) Start asterisk "asterisk -ggvvvvvvc"
3) Press Ctrl-A then Escape to suspend console

This doesn't sound like a big problem, but it is because this same
situation happens when you ssh into a box, loose the connection because of
internet failure, or whatever other reason.

After 5-10 minutes of asterisk trying to write to the suspended console,
everything hangs, nothing crashes, but asterisk stops making calls,
accepting calls, or doing any sort of processing.

My first evaluation of this is that there are blocking writes to the
console, and there are no checks to see if the file descriptor can write or
not.
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
duplicate of        0010010 Asterisk eating 100% CPU
====================================================================== 

---------------------------------------------------------------------- 
 tzafrir - 03-31-08 04:19  
---------------------------------------------------------------------- 
The logger normally runs in a separate thread. Perhaps the issue that a
certain lock is held by the thread writing to the console, and now other
threads wait on that lock?

An obvious workaround for your issue is, well, not to use -c . Or use -F
to force Asterisk to daemonize.

This avoids the need for screen. You can still tail -f log files as you
please.

If you have any separate issues, please open separate bugs for them. At
first glance it appears to be a valid issue (but I haven't tried to
reproduce it yet). 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
03-31-08 04:19  tzafrir        Note Added: 0084769                          
======================================================================