[asterisk-bugs] [JIRA] (ASTERISK-29316) Asterisk service is failed due to segmentation fault about twice a week

[Asterisk Team (JIRA)]

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

Asterisk Team commented on ASTERISK-29316:
------------------------------------------

This issue has been reopened as a result of your commenting on it as the reporter. It will be triaged once again as applicable.

> Asterisk service is failed due to segmentation fault about twice a week
> -----------------------------------------------------------------------
>
>                 Key: ASTERISK-29316
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-29316
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: CDR/cdr_pgsql, Channels/chan_pjsip, Functions/func_odbc, Resources/res_odbc
>    Affects Versions: 16.10.0
>         Environment: OS:CentOS 7.7 64-bit
>            Reporter: JUNKO MITANI
>            Assignee: Unassigned
>         Attachments: core-asterisk-9903.zip
>
>
> Asterisk service is failed due to segmentation fault about twice a week.
> I do not know the cause and it improves by restarting Asterisk service.
> The output result of the command(systemctl) when it occurs is as follows.
> # systemctl status asterisk
> ● asterisk.service - Asterisk PBX and Telephony Daemon
>    Loaded: loaded (/usr/lib/systemd/system/asterisk.service; enabled; vendor preset: disabled)
>    Active: failed (Result: signal) since 金 2021-02-26 10:00:40 JST; 9min ago
>   Process: 7456 ExecStop=/usr/sbin/asterisk -rx core stop now (code=exited, status=0/SUCCESS)
>   Process: 9903 ExecStart=/usr/sbin/asterisk -fg -C /etc/asterisk/asterisk.conf (code=killed, signal=SEGV)
>  Main PID: 9903 (code=killed, signal=SEGV)
> The beginning of the full text generated by using "ast_coredumper" from the acquired core dump is as follows.
> !@!@!@! full.txt !@!@!@!
> $3 = {si_signo = 11, si_errno = 0, si_code = 1, _sifields = {_pad = {24, 0, 0, 0, -1136214576, -29869, -1802902391, -1, 0 <repeats 20 times>}, _kill = {si_pid = 24, si_uid = 0}, _timer = {si_tid = 24, si_overrun = 0, si_sigval = {sival_int = 0, sival_ptr = 0x0}}, _rt = {si_pid = 24, si_uid = 0, si_sigval = {sival_int = 0, sival_ptr = 0x0}}, _sigchld = {si_pid = 24, si_uid = 0, si_status = 0, si_utime = -4880004445158506496, si_stime = -7743406802930267309}, _sigfault = {si_addr = 0x18}, _sigpoll = {si_band = 24, si_fd = 0}}}
> Signal        Stop	Print	Pass to program	Description
> SIGSEGV       Yes	Yes	Yes		Segmentation fault
> It may be caused by stopping the service with the "systemctl stop asterisk" command in the test.
> Is it possible to have the cause investigated based on the acquired core dump?
> Regards



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