[Home]

Summary:ASTERISK-28482: Asterisk 13.22.0 Segmentation fault PJSIP TLS+SRTP about 60 endpoints
Reporter:Ivan Shugaley (hiroshi.titan@gmail.com)Labels:pjsip
Date Opened:2019-07-17 03:43:37Date Closed:2019-08-02 12:00:02
Priority:MajorRegression?
Status:Closed/CompleteComponents:Channels/chan_pjsip
Versions:13.22.0 Frequency of
Occurrence		One Time
Related
Issues:
Environment:centos 7 freepbxdistroAttachments:( 0) core-2019-07-16T10-24-46+0300-brief.txt
( 1) core-2019-07-16T10-24-46+0300-full.txt
( 2) core-2019-07-16T10-24-46+0300-locks.txt
( 3) core-2019-07-16T10-24-46+0300-thread1.txt
Description:Hi!
We get Segmentation fault on freepbx distro after half year stable operation.
FreePBX 14.0.11
Asterisk 13.22.0
We use TLS+SRTP for all endpoints on PJSIP

/var/log/asterisk/full
[2019-07-16 10:24:45] ERROR[17503] astobj2.c: FRACK!, Failed assertion user_data is NULL (0)
[2019-07-16 10:24:45] VERBOSE[17503] logger.c: Got 26 backtrace records

/var/log/messages
Jul 16 10:24:45 freepbx kernel: asterisk[17503]: segfault at 30 ip 00000000005c80ef sp 00007f8701a1f7c0 error 4 in asterisk[400000+38d000]

core-2019-07-16T10-24-46+0300-brief.txt
core-2019-07-16T10-24-46+0300-full.txt
core-2019-07-16T10-24-46+0300-locks.txt
core-2019-07-16T10-24-46+0300-thread1.txt
Comments:By: Asterisk Team (asteriskteam) 2019-07-17 03:43:38.788-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].

Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur.
By: George Joseph (gjoseph) 2019-07-17 08:19:35.517-0500

As I mentioned in the community post...  Can you upgrade to the most recent stable version of Asterisk and see if you still get the segfault?  If you do, you'll also need to install the FreePBX debug symbols so we can get a better backtrace.

By: Ivan Shugaley (hiroshi.titan@gmail.com) 2019-07-18 11:03:23.824-0500

I will upgrade asterisk in maintenance window. Then I will send feedback.
By: Asterisk Team (asteriskteam) 2019-08-02 12:00:01.803-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