[Home]

Summary:ASTERISK-25643: Internal Chan / PJSIP Cause code related Crash
Reporter:Bill Brigden (billbrigden)Labels:
Date Opened:2015-12-22 06:49:34.000-0600Date Closed:2020-01-14 11:13:54.000-0600
Priority:MajorRegression?
Status:Closed/CompleteComponents:Channels/chan_pjsip
Versions:13.6.0 Frequency of
Occurrence		Frequent
Related
Issues:
Environment:Linux Deb 7.8Attachments:( 0) stack.txt
Description:Hi,

I've been getting random crashes on a server that has fairly simple dialplan, PJSIP extensions (using ODBC / Sorcery).

I've recompiled with debug flags, etc - attached is a stacktrace. There are no entries written to the debug log that correlate.
Comments:By: Asterisk Team (asteriskteam) 2015-12-22 06:49:35.278-0600

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: Bill Brigden (billbrigden) 2015-12-22 06:50:13.820-0600

Stacktrace
By: Rusty Newton (rnewton) 2015-12-22 19:02:59.849-0600

Thank you for the crash report. However, we need more information to investigate the crash. Please provide:

1. A backtrace generated from a core dump using the instructions provided on the Asterisk wiki [1].
2. Specific steps taken that lead to the crash.
3. All configuration information necesary to reproduce the crash.

Thanks!

[1]: https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace


By: Rusty Newton (rnewton) 2015-12-22 19:03:10.050-0600

We require additional debug to continue with triage of your issue. Please follow the instructions on the wiki [1] for how to collect debugging information from Asterisk. For expediency, where possible, attach the debug with a '.txt' file extension so that the debug will be usable for further analysis.

Thanks!

[1] https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information


By: Rusty Newton (rnewton) 2015-12-22 19:04:57.522-0600

I posted two comments above. Please provide a new trace according to the instructions above and a debug log that correlates to the crash.  Please don't make an excerpt, just grab the last few minutes of the log before the crash. If there is sensitive information please only sanitize that information.
By: Asterisk Team (asteriskteam) 2016-01-06 12:00:20.399-0600

Suspended due to lack of activity. This issue will be automatically re-opened if the reporter posts a comment. If you are not the reporter and would like this re-opened please create a new issue instead. If the new issue is related to this one a link will be created during the triage process. Further information on issue tracker usage can be found in the Asterisk Issue Guidlines [1].

[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines