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

[noreply at bugs.digium.com]

The following issue has been REOPENED. 
====================================================================== 
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-18-2008 10:37 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
====================================================================== 

---------------------------------------------------------------------- 
 darren1713 - 03-18-08 10:37  
---------------------------------------------------------------------- 
Sorry I didn't keep up with this bug report, but this problem is not a
duplicate of bug 0010010. * does not consume 100% cpu when this happens, it
just stops accepting calls, stops responding, and just hangs.

This is still reproducible in SVN-trunk

I have not dug through the source on this, but since the logger is not
vital for anything, if it can't write to the console or a file, it should
just forget it and continue on, allowing * to continue.

Two other logger problems:
http://bugs.digium.com/view.php?id=1 rm /var/log/asterisk/full while * is
running
* will not re-open the log file and continue

http://bugs.digium.com/view.php?id=2 rm/var/log/asterisk/full, then in *
console, logger reload
* will still not re-open the log file and continue. If I open logger.conf,
and change the filename to "full2" and then logger reload, it will then
create and open /var/log/asterisk/full2 and continue logging.

This may seem irrelevant but considering we have a production system that
sometimes needs to be debugged, the "everything" log can easily be 1GB per
day, so this log file needs to be removed and restarted without killing *
for us to debug with something manageable. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
03-18-08 10:37  darren1713     Status                   closed => new       
03-18-08 10:37  darren1713     Resolution               duplicate => reopened
03-18-08 10:37  darren1713     Note Added: 0084139                          
======================================================================