[asterisk-bugs] [JIRA] (ASTERISK-30249) Asterisk segfault - libcrypto.so

[Asterisk Team (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-30249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=260362#comment-260362 ] 

Asterisk Team commented on ASTERISK-30249:
------------------------------------------

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. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed.

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.

Please note that by submitting data, code, or documentation to Sangoma through JIRA, you accept the Terms of Use present at [https://www.asterisk.org/terms-of-use/|https://www.asterisk.org/terms-of-use/].

> Asterisk segfault - libcrypto.so
> --------------------------------
>
>                 Key: ASTERISK-30249
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-30249
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: . I did not set the category correctly.
>    Affects Versions: 16.27.0
>         Environment: Asterisk 16.27.0
> Current PBX Version:
> 15.0.23
> Current System Version:
> 12.7.8-2203-2.sng7
> OS: 
> 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/"
>            Reporter: Scanline Tech
>
> Getting frequent segfault errors in libsssl.so.1.0.2, libcrypto.so.1.0.2k, libc-2.17.so
> our company certificates are valid and placed inside: 
> /etc/asterisk/keys
> /var/log/messages-20220918.gz:Sep 15 21:44:07 la-dmzsipsrv01 kernel: asterisk[29403]: segfault at 221 ip 00007fa05601809c sp 00007f9f119cfa20 error 4 in libcrypto.so.1.0.2k[7fa055ef2000+236000]
> /var/log/messages-20220918.gz:Sep 16 09:55:35 la-dmzsipsrv01 kernel: asterisk[124233]: segfault at 44 ip 00007f86b8b3209c sp 00007f8577b1ca20 error 4 in libcrypto.so.1.0.2k[7f86b8a0c000+236000]
> /var/log/messages-20220925.gz:Sep 22 04:58:40 la-dmzsipsrv01 kernel: asterisk[88556]: segfault at 1fa9 ip 00007f9673cce065 sp 00007f95da32f930 error 4 in libssl.so.1.0.2k[7f9673ca6000+67000]
> /var/log/messages-20220925.gz:Sep 22 09:42:46 la-dmzsipsrv01 kernel: asterisk[3006]: segfault at 45 ip 00007faa7bfdd09c sp 00007fa9340f1a20 error 4 in libcrypto.so.1.0.2k[7faa7beb7000+236000]
> /var/log/messages-20220925.gz:Sep 22 10:40:58 la-dmzsipsrv01 kernel: asterisk[53386]: segfault at 119 ip 00007f172e76faec sp 00007f15ef7b1a58 error 4 in libc-2.17.so[7f172e6ea000+1c3000]
> /var/log/messages-20220925.gz:Sep 23 06:05:03 la-dmzsipsrv01 kernel: asterisk[86277]: segfault at 2f9 ip 00007fba0ee34aec sp 00007fb8cf446a58 error 4 in libc-2.17.so[7fba0edaf000+1c3000]



--
This message was sent by Atlassian JIRA
(v6.2#6252)