Summary: | ASTERISK-28204: Asterisk Restarted | Crashes chan_sip.c | ||
Reporter: | Vivek K Mishra (vvkmishra77@gmail.com) | Labels: | |
Date Opened: | 2018-12-10 06:29:56.000-0600 | Date Closed: | 2018-12-10 06:39:12.000-0600 |
Priority: | Major | Regression? | No |
Status: | Closed/Complete | Components: | Channels/chan_sip/General |
Versions: | 15.3.0 | Frequency of Occurrence | Occasional |
Related Issues: | |||
Environment: | CentOS release 6.9 (Final) 64 Bits Asterisk Version : 15.3.0 | Attachments: | |
Description: | [Dec 10 15:16:28] ERROR[3033][C-00003863] chan_sip.c: FRACK!, Failed assertion bad magic number 0xba05e7da for object 0x7fad6c034e98 (0)
[Dec 10 15:16:28] VERBOSE[3033][C-00003863] logger.c: Got 12 backtrace records [Dec 10 15:16:28] VERBOSE[3033][C-00003863] logger.c: #0: [0x45b2f6] /usr/sbin/asterisk(__ao2_ref+0xa6) [0x45b2f6] [Dec 10 15:16:28] VERBOSE[3033][C-00003863] logger.c: #1: [0x7faee622ad49] /usr/lib/asterisk/modules/chan_sip.so(+0x27d49) [0x7faee622ad49] [Dec 10 15:16:28] VERBOSE[3033][C-00003863] logger.c: #2: [0x7faee62811d6] /usr/lib/asterisk/modules/chan_sip.so(+0x7e1d6) [0x7faee62811d6] [Dec 10 15:16:28] VERBOSE[3033][C-00003863] logger.c: #3: [0x4acd9e] /usr/sbin/asterisk(ast_hangup+0x2ae) [0x4acd9e] [Dec 10 15:16:28] VERBOSE[3033][C-00003863] logger.c: #4: [0x5716b6] /usr/sbin/asterisk() [0x5716b6] [Dec 10 15:16:28] VERBOSE[3033][C-00003863] logger.c: #5: [0x572b2b] /usr/sbin/asterisk() [0x572b2b] [Dec 10 15:16:28] VERBOSE[3033][C-00003863] logger.c: #6: [0x5e930e] /usr/sbin/asterisk() [0x5e930e] | ||
Comments: | By: Asterisk Team (asteriskteam) 2018-12-10 06:29:57.989-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: Joshua C. Colp (jcolp) 2018-12-10 06:37:03.067-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: Malcolm Davenport (mdavenport) 2018-12-10 06:37:10.899-0600 Per the release timeline here: https://wiki.asterisk.org/wiki/display/AST/Asterisk+Versions Asterisk 15 no longer receives bug-fixes. Versions currently receiving bug-fixes include the 13-branch and 16-branch. As well, 15.3 wasn't the latest version of Asterisk 15. And, bear in mind that chan_sip is not supported by the Asterisk core development team; rather, someone outside of that team would need to take interest in the issue. By: Joshua C. Colp (jcolp) 2018-12-10 06:39:12.500-0600 As I misread 15.3.0 as the latest 16 release, I'm closing out this issue per what Malcolm stated. If you can reproduce this using a supported version with the information I requested then open a new issue with it. By: Vivek K Mishra (vvkmishra77@gmail.com) 2018-12-10 06:50:39.356-0600 Ohhhh Sorry!!! I've made myself out from the similar issues many times with the stable version. Thanks for your valuable time and taking me in a right direction. By: Asterisk Team (asteriskteam) 2018-12-10 06:50:39.495-0600 This issue has been reopened as a result of your commenting on it as the reporter. It will be triaged once again as applicable. |