Summary:	ASTERISK-25534: Core dump on RTCP report/DNS lookup
Reporter:	Morten Tryfoss (mtryfoss)	Labels:
Date Opened:	2015-11-09 05:17:38.000-0600	Date Closed:	2020-01-14 11:14:05.000-0600
Priority:	Critical	Regression?
Status:	Closed/Complete	Components:	General
Versions:	13.6.0	Frequency of Occurrence	One Time
Related Issues:
Environment:		Attachments:	( 0) backtrace.txt
Description:	Asterisk crashed. There might have been a slight drop on the connectivity against the DNS server at the point, but the host it tried lookup on (it's own hostname) is added to /etc/hosts too. No info in the logs at the time of the crash. It happened in the middle of the night with just about one simultaneous call on the system.
Comments:	By: Asterisk Team (asteriskteam) 2015-11-09 05:17:39.728-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: Rusty Newton (rnewton) 2015-11-09 09:54:30.896-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-11-09 13:36:13.084-0600 In addition please provide a debug log[1] captured before the crash. [1]: https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information By: Morten Tryfoss (mtryfoss) 2015-11-09 14:31:03.171-0600 Sorry. Forgot to upload the backtrace. By: Morten Tryfoss (mtryfoss) 2015-11-09 14:32:14.321-0600 And i do not have any debug logs related to the crash. By: Rusty Newton (rnewton) 2015-11-09 17:06:56.878-0600 Your backtrace appears to contain a memory corruption. We need one or both of the following items to continue investigation of the issue: 1. Valgrind output. See https://wiki.asterisk.org/wiki/display/AST/Valgrind for instructions on how to use Valgrind with Asterisk. 2. MALLOC_DEBUG output. See https://wiki.asterisk.org/wiki/display/AST/MALLOC_DEBUG+Compiler+Flag for instructions on how to use the MALLOC_DEBUG option. Note that MALLOC_DEBUG and Valgrind are mutually exclusive options. Valgrind output is preferable, but will be more system resource intensive and may be difficult to get on a production system. In such a case, you may have better luck getting the necessary output from MALLOC_DEBUG. By: Rusty Newton (rnewton) 2015-11-09 17:08:01.010-0600 Regarding the above request for valgrind or MALLOC_DEBUG output.. if you can't reproduce the issue then we probably won't have anywhere to go from here.. we may have to wait until someone runs into it frequently enough to get the necessary debug. By: Morten Tryfoss (mtryfoss) 2015-11-10 01:00:29.404-0600 Thanks for the feedback. Combined, these nodes handles > 500.000 answered calls every day, and this is the first crash of this type. I'll probably just wait and see if it happens again. By: Rusty Newton (rnewton) 2015-11-10 09:49:07.118-0600 Alrighty let us know. By: Asterisk Team (asteriskteam) 2015-11-24 12:00:22.240-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