| Summary: | ASTERISK-27227: Frequent Crash (Possibly due to unbundled PJSIP) | ||
| Reporter: | Scott Pabin (tuxd00d) | Labels: | |
| Date Opened: | 2017-08-28 21:08:29 | Date Closed: | 2020-01-14 11:14:03.000-0600 |
| Priority: | Minor | Regression? | |
| Status: | Closed/Complete | Components: | pjproject/pjsip |
| Versions: | 13.13.0 14.6.0 | Frequency of Occurrence | Frequent |
| Related Issues: | |||
| Environment: | Ubuntu 14.04.5 on OpenVZ | Attachments: | ( 0) asterisk-ASTERISK-27227-2-results.tar.gz ( 1) asterisk-ASTERISK-27227-results.tar.gz |
| Description: | Console and log do not indicate shutdown or failure. Safe_asterisk log indicates "Asterisk ended with exit status 139, Asterisk exited on signal 11., Automatically restarting Asterisk."
New install with only a few PJSIP endpoints. No dialplan yet. | ||
| Comments: | By: Asterisk Team (asteriskteam) 2017-08-28 21:08:29.912-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: Scott Pabin (tuxd00d) 2017-08-28 21:14:19.140-0500 This backtrace (27227) is running 13.13-Cert4. By: Scott Pabin (tuxd00d) 2017-08-29 17:59:02.489-0500 This backtrace (27227-2) is from another OpenVZ container but running 14.06.0. By: Scott Pabin (tuxd00d) 2017-08-29 18:04:18.126-0500 I've recompiled both, 13.13-Cert4 and 14.06.0, ensuring that 'configure' used '--with-pjproject-bundled'. The issue has yet to present again with either. By: Scott Pabin (tuxd00d) 2017-08-30 11:32:22.674-0500 Both systems running for almost 24 hours, without issue. Perhaps it was related to possibly unbundled PJSIP. However, if it was unbundled PJSIP causing the issue, it is not ideal for Asterisk to *silently* die without any log entry. Therefore I've downgraded the severity to 'minor' as the bundling appears to fix the issue. By: Joshua C. Colp (jcolp) 2017-08-30 11:45:53.377-0500 Unfortunately when an application is terminated as a result of a segmentation fault the entire application immediately terminates - there is no ability for Asterisk to log or output anything as it is no longer running. By: Rusty Newton (rnewton) 2017-09-01 14:45:34.663-0500 Scott are you able to reproduce the issue or describe how we can ? If not, I'm not sure where to go with this one. By: Asterisk Team (asteriskteam) 2017-09-16 12:00:02.474-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 | ||