Summary:	ASTERISK-26550: segfault error 6 in asterisk[400000+2b8000]
Reporter:	PAUL GIORDANO (paulgiordano)	Labels:
Date Opened:	2016-11-02 14:49:16	Date Closed:	2020-01-14 11:13:41.000-0600
Priority:	Major	Regression?
Status:	Closed/Complete	Components:	CDR/General
Versions:	13.9.1	Frequency of Occurrence	Occasional
Related Issues:	is related to ASTERISK-26421 Segmentation Fault with ARI originate into mixing bridge with 43 clients
Environment:	SHMZ release 6.5 (Final) Linux kernel 2.6.32-431.el6.x86-64 4GB memory 4CPU asterisk13-13.9.1-1.shmz65.1.115.x86_64	Attachments:	( 0) backtrace.txt
Description:	asterisk[45832]: segfault at 7f9fb45f4ff8 ip 00000000005e23ae sp 00007f9fb45f5000 error 6 in asterisk[400000+2b8000] Occurs occasionally, every few days.
Comments:	By: Asterisk Team (asteriskteam) 2016-11-02 14:49:17.190-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: PAUL GIORDANO (paulgiordano) 2016-11-02 14:52:26.979-0500 backtrace from latest failure/core By: Richard Mudgett (rmudgett) 2016-11-02 15:16:35.350-0500 The crash is because of a very long CDR chain being destroyed and blowing the stack. Are you by chance supplying your own channel unique ids that aren't that unique?  See ASTERISK-26421 By: PAUL GIORDANO (paulgiordano) 2016-11-03 08:20:41.030-0500 We aren't suppling channel ids - it's a pretty generic install. What can I supply that would help fix this? By: Richard Mudgett (rmudgett) 2016-11-03 08:56:04.764-0500 The Asterisk Issue Guidelines is a good place to see what we almost always need.  Really. In your particular case we need debug logs showing how you are using Asterisk to get these long CDR chains.  In addition, the fix for ASTERISK-26421 made it so even if you get these long CDR chains it shouldn't blow the stack. https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information By: Asterisk Team (asteriskteam) 2016-11-17 12:00:00.894-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