[asterisk-bugs] [Asterisk 0012308]: high SIP call volume locks Asterisk 1.4.19rc3

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12308 
====================================================================== 
Reported By:                mflorell
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   12308
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   crash
Priority:                   normal
Status:                     new
Asterisk Version:           1.4.19-rc3 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             03-26-2008 11:23 CDT
Last Modified:              03-26-2008 15:46 CDT
====================================================================== 
Summary:                    high SIP call volume locks Asterisk 1.4.19rc3
Description: 
I am able to reliably lock up Asterisk and send the loadavg on the server
to 100.00 and higher within 5 minutes of starting performance testing with
300+ channels(all SIP). With IAX, even at higher call volumes, it does not
crash at all.

Here is a link to the 20,000+ line GDB output:
http://www.eflo.net/files/Asterisk_1.4.19rc3_crash_gdb_2008-03-26.txt

I tried doing a "core show threads" but Asterisk was not responding.


====================================================================== 

---------------------------------------------------------------------- 
 putnopvut - 03-26-08 15:46  
---------------------------------------------------------------------- 
mflorell:

The second backtrace you linked to has a bunch of threads waiting on
locks, and so I'd be interested in seeing the output of "core show locks"
once the lockup has happened. I see from your initial report, though, that
this may not be possible since you said that Asterisk was not responsive
when you entered commands.

As another suggestion, if you can reliably reproduce this, could you not
load any modules you aren't actively using for the test? There are a lot of
IAX2 threads in this backtrace, and from what I understand, you aren't
actually using IAX2 for this test. If you could trim down the number of
modules being used when you cause the lockup, you may be able to get a much
less massive backtrace. Of course, if you are using IAX2 channels in your
test, then that suggestion won't work well.

The problem right now is that with 284 threads in the backtrace, it's
incredibly difficult to tell where the problems are occurring. Either "core
show locks" or a smaller backtrace would make things much more manageable
if possible. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
03-26-08 15:46  putnopvut      Note Added: 0084623                          
======================================================================