[Home]

Summary:ASTERISK-28486: Randomly generated segfault in asterisk process
Reporter:Viacheslav Iaradaikin (viaradaikin)Labels:
Date Opened:2019-07-24 05:46:52Date Closed:2019-07-24 09:13:03
Priority:MajorRegression?
Status:Closed/CompleteComponents:Bridges/bridge_simple
Versions:13.22.0 Frequency of
Occurrence
Occasional
Related
Issues:
duplicatesASTERISK-28140 repeated segmentation faults
Environment:Deployed in VMware on a Physical server: IBM 3650 2*4Core CPU 4 GB RAM SAS storage OS info: uname -a Linux PBX-CA_PUB.local 3.10.0-957.21.3.el7.x86_64 #1 SMP Tue Jun 18 16:35:19 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux cat /etc/*-release NAME="Sangoma Linux" VERSION="7 (Core)" ID="sangoma" ID_LIKE="centos rhel fedora" VERSION_ID="7" PRETTY_NAME="Sangoma Linux 7 (Core)" ANSI_COLOR="0;31" CPE_NAME="cpe:/o:sangoma:sng:7::server:utf8" HOME_URL="https://distro.sangoma.net/" BUG_REPORT_URL="https://issues.sangoma.net/" CENTOS_MANTISBT_PROJECT="Sangoma-7" CENTOS_MANTISBT_PROJECT_VERSION="7" REDHAT_SUPPORT_PRODUCT="sangoma" REDHAT_SUPPORT_PRODUCT_VERSION="7" Sangoma Linux release 7.5.1805 (Core) Sangoma Linux release 7.5.1805 (Core) Sangoma Linux release 7.5.1805 (Core) Attachments:( 0) core.PBX-CA_PUB.local-2019-07-24T09-40-17+0300-brief.txt
( 1) core.PBX-CA_PUB.local-2019-07-24T09-40-17+0300-locks.txt
( 2) core.PBX-CA_PUB.local-2019-07-24T09-40-17+0300-thread1.txt
Description:Segmentation fault error in asterisk process occuring occasionaly nearly every day.
From /var/log/messages
Jul 23 08:34:27 PBX-CA_PUB kernel: asterisk[14329]: segfault at c000c0e0 ip 000000000062ba14 sp 00007f0998e116e0 error 4 in asterisk[400000+38d000]
Jul 23 13:39:35 PBX-CA_PUB kernel: asterisk[3034]: segfault at 28 ip 000000000069b02b sp 00007fcb3b0480b0 error 6
Jul 23 13:39:35 PBX-CA_PUB kernel: asterisk[2858]: segfault at 28 ip 000000000069b02b sp 00007fcb3946a550 error 6
Jul 23 13:39:35 PBX-CA_PUB kernel: asterisk[2979]: segfault at 28 ip 000000000069b02b sp 00007fcb39754aa0 error 6
Jul 24 09:40:17 PBX-CA_PUB kernel: asterisk[22834]: segfault at 0 ip           (null) sp 00007fb0be999fe8 error 4 in asterisk[400000+38d000]
Comments:By: Asterisk Team (asteriskteam) 2019-07-24 05:46:53.513-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-24 09:13:04.009-0500

This issue was fixed in Asterisk 13.24.0.  Please upgrade to the latest Asterisk version.

If the segfaults continue, you can re-open this issue but you'll need to provide backtraces that have symbols in them.
https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace