| Summary: | ASTERISK-27535: Asterisk crash with segmentation fault in libpthread-2.19.so | ||
| Reporter: | Sandip B (snbarot) | Labels: | |
| Date Opened: | 2017-12-28 19:35:54.000-0600 | Date Closed: | 2020-01-14 11:13:24.000-0600 |
| Priority: | Major | Regression? | No |
| Status: | Closed/Complete | Components: | Core/General |
| Versions: | 14.3.0 | Frequency of Occurrence | One Time |
| Related Issues: | |||
| Environment: | Operating system : Ubuntu 14.04.5 LTS (GNU/Linux 3.13.0-32-generic x86_64) Asterisk Version : 14.3.0 DAHDI Version: 2.9.1 Echo Canceller: MG2 | Attachments: | ( 0) core.zip |
| Description: | Hi there,
our asterisk server (version 14.3.0 ) crashed abruptly and following lines logged in system log files. *************Dec 23 15:31:40 ubuntu kernel: [532105.894950] show_signal_msg: 6 callbacks suppressed Dec 23 15:31:40 ubuntu kernel: [532105.894966] asterisk[15797]: segfault at 10 ip 00007f1700bfd404 sp 00007f166c659fb0 error 4 in libpthread-2.19.so[7f1700bf3 000+19000]**************** Are you able to help to find out what has caused the crash and what corrective actions can be taken to avoid such crash in future ? | ||
| Comments: | By: Asterisk Team (asteriskteam) 2017-12-28 19:35:55.924-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) 2017-12-28 19:46:19.778-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: Joshua C. Colp (jcolp) 2017-12-28 19:47:04.200-0600 As well the version of Asterisk you have provided is no longer supported. Please upgrade to the latest release of 15. By: Sandip B (snbarot) 2017-12-28 20:00:11.827-0600 thanks Joshua for the steps : 1. A backtrace generated from a core dump using the instructions provided on the Asterisk wiki [1]. => I have enabled it now, but the crash happened only once in 1 year of operation of the server and not able to replicate the issue any more. 2. Specific steps taken that lead to the crash. => Nothing changed specifically recently. Calls were running ok till crash . 3. All configuration information necesary to reproduce the crash. => unfortunately not able to reproduce the crash. Is there anything can be found out from the logged message when last crash happened ? By: Joshua C. Colp (jcolp) 2017-12-28 20:01:47.316-0600 The message indicates that it crashed as a result of something in threading. That's it. By: Joshua C. Colp (jcolp) 2017-12-28 20:02:21.266-0600 Without a backtrace we can't do anything with this issue but I'll assign it back to you in case you can get it. By: Asterisk Team (asteriskteam) 2018-01-12 12:00:01.993-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 By: Sandip B (snbarot) 2018-01-18 21:54:31.704-0600 We have the issue recurred and backtrace is attached herewith. Are you able to check to assist us further ? By: Asterisk Team (asteriskteam) 2018-01-18 21:54:31.819-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. By: Kevin Harwell (kharwell) 2018-01-19 11:17:40.210-0600 You've just attached the core file, but no backtrace. You'll need to extract the backtrace from the core file. See the following wiki pages on how to collect and extract backtraces for Asterisk: https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace https://wiki.asterisk.org/wiki/pages/viewpage.action?pageId=5243139 Also per the Asterisk versions page [1], the maintenance (bug fix) support for the Asterisk branch you are using has ended. For continued maintenance support please move to a supported branch of Asterisk. After testing with a supported branch, if you find this problem has not been resolved, please open a new issue against the latest version of that Asterisk branch. Thanks! [1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Versions By: Asterisk Team (asteriskteam) 2018-02-02 12:00:00.528-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 | ||