[Home]

Summary:ASTERISK-25350: Asterisk crashes
Reporter:Carl Fortin (phonefxg)Labels:
Date Opened:2015-08-28 05:37:17Date Closed:2015-08-28 05:52:56
Priority:MajorRegression?
Status:Closed/CompleteComponents:
Versions:13.4.0 Frequency of
Occurrence
Related
Issues:
duplicatesASTERISK-25148 res_pjsip NULL channel audit
Environment:Asterisk Realtime 13.4 PJSIP Driver mysql Ver 14.14 pjproject 2.3 spandsp 0.0.6 jansson 2.7 CentOS 6.6 64 bits on Vmware Number of endpoints : > 700 Numbers of calls : 3000/day Our Hardware: Phones : Cisco SPA514G FW: 7.5.7 ATA : Audiocodes MP124 T1 : Mediatrix 3532 ISDN to SIP gateway CPU : Quadcore Intel(R) Xeon(R) CPU E5-2650 RAM : 8 GBAttachments:( 0) Asterisk_log_crash_line_285.txt
( 1) backtrace.txt
Description:Asterisk crashed two times in the last 2 months. The first crash happened after running asterisk over a month without any issue. The second crash happened two weeks later. Could someone look at my backtraces from the last crash and see what might be wrong?

I am running version 13.4 with the following patches:

https://issues.asterisk.org/jira/browse/ASTERISK-25168





Comments:By: Asterisk Team (asteriskteam) 2015-08-28 05:37:18.531-0500

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

By: Carl Fortin (phonefxg) 2015-08-28 05:38:55.547-0500

Backtraces from the crash and full debug log.
Nothing in mmlog except for new session

By: Joshua C. Colp (jcolp) 2015-08-28 05:53:10.081-0500

This was already fixed in 13.5.0.