[asterisk-bugs] [Asterisk 0016452]: Lots of crashes after upgrading to latest 1.6.0.20-rc1

Asterisk Bug Tracker noreply at bugs.digium.com
Wed Dec 16 10:35:48 CST 2009


A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16452 
====================================================================== 
Reported By:                corruptor
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   16452
Category:                   Core/General
Reproducibility:            always
Severity:                   crash
Priority:                   normal
Status:                     acknowledged
Asterisk Version:           1.6.0.20-rc1 
JIRA:                       SWP-551 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-12-16 04:23 CST
Last Modified:              2009-12-16 10:35 CST
====================================================================== 
Summary:                    Lots of crashes after upgrading to latest
1.6.0.20-rc1
Description: 
I've tried to upgrade my asterisk 1.6.19 to latest RC. Asterisk crashes
every 30-40 minutes. There are about 15 concurrent calls. All calls are
recorded using MixMonitor. Asterisk crashes after hanging up one of the
calls.
I upload the backtrace.
Asterisk 1.6.19 same config works ok.
====================================================================== 

---------------------------------------------------------------------- 
 (0115329) corruptor (reporter) - 2009-12-16 10:35
 https://issues.asterisk.org/view.php?id=16452#c115329 
---------------------------------------------------------------------- 
I use Centos 5.
I've uploaded second backtrace. It's seemed for me different, Maybe it may
help.
I've noticed this happens on our outgoing calls. I've uploaded part of
full log related to first backtrace. Asterisk has crashed after last
message in this log. It doesn't meter if call was answered or not. 

I use database connectivity. We write QueueLog messages straight to
database MySQL. You can see that in full log. It seems to work ok. I also
write CDR to MySQL. (works ko also).

Unfortunately I am not able upload other backtraces because I have
installed earlier version. I can try tomorrow. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-12-16 10:35 corruptor      Note Added: 0115329                          
======================================================================




More information about the asterisk-bugs mailing list