| Summary: | ASTERISK-25454: Crashing possibly related to cdr_manager | ||
| Reporter: | Zane Conkle (zconkle) | Labels: | |
| Date Opened: | 2015-10-08 10:40:46 | Date Closed: | 2020-01-14 11:13:49.000-0600 |
| Priority: | Major | Regression? | |
| Status: | Closed/Complete | Components: | |
| Versions: | 13.6.0 | Frequency of Occurrence | |
| Related Issues: | |||
| Environment: | Attachments: | ( 0) backtrace-2015-10-08.txt ( 1) cdr_manager-diff.txt | |
| Description: | This is the second time asterisk has crashed within 12 hours of enabling cdr_manager. What is weird is the coredump references a segfault at chan_pjsip.c:1750 and I do not see any threads accessing cdr. It makes me think the issue may be non-related to cdr_manager.
We made a very simple change and added linkedid to cdr_manager.c so I am attaching that change along with the backtrace. | ||
| Comments: | By: Asterisk Team (asteriskteam) 2015-10-08 10:40:47.769-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: Rusty Newton (rnewton) 2015-10-09 12:55:53.541-0500 Jcolp looked over the trace and the root cause is not obvious, so we'll need further information to assist. Can you provide a debug log for the next crash so we can see what was happening right before the crash? https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information In addition, please make sure to recompile with DONT_OPTIMIZE and BETTER_BACKTRACES. By: Asterisk Team (asteriskteam) 2015-10-24 12:00:20.447-0500 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 | ||