| Summary: | ASTERISK-28737: Asterisk 13.28.0 repeatable crashes | ||||
| Reporter: | Martin Nyström (martin.nystrom) | Labels: | webrtc | ||
| Date Opened: | 2020-02-12 03:25:15.000-0600 | Date Closed: | 2020-02-12 04:55:14.000-0600 | ||
| Priority: | Critical | Regression? | |||
| Status: | Closed/Complete | Components: | Bridges/bridge_simple | ||
| Versions: | 13.28.0 | Frequency of Occurrence | Frequent | ||
| Related Issues: |
| ||||
| Environment: | Linux sys1 3.10.0-1062.9.1.el7.x86_64 #1 SMP Fri Dec 6 15:49:49 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux CentOS Linux release 7.7.1908 (Core) Asterisk 13.28.0 REALTIME | Attachments: | ( 0) core.sys1-2020-02-12T09-02-23+0000-brief.txt ( 1) core.sys1-2020-02-12T09-02-23+0000-full.txt ( 2) core.sys1-2020-02-12T09-02-23+0000-locks.txt ( 3) core.sys1-2020-02-12T09-02-23+0000-thread1.txt | ||
| Description: | Hello,
First I am unsure of the components so if someone with insights on the crash dumps can specify this further it would be great. We're experienceing repeatable crashes, constantly every 10-15 minutes. I am yet to figure out the exact scenario that causes this. I ran with DONT_OPTIMIZE & MALLOC_DEBUG but the /var/log/asterisk/mmlog produced nothing. We first suspected a memory issue but we migrated the asterisk to an entire new server and the issues followed us there. The agents are running WebRTC. I saw some dtls errors in the gdb asterisk debugger. | ||||
| Comments: | By: Asterisk Team (asteriskteam) 2020-02-12 03:25:17.464-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]. 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: Joshua C. Colp (jcolp) 2020-02-12 04:55:14.857-0600 The way DTLS works has been rewritten in recent versions, and this problem solved there. | ||||