[asterisk-bugs] [JIRA] (ASTERISK-28209) Repeated SegFaults on 16.1.0; stable on 13.24.0

Gregory Massel (JIRA) noreply at issues.asterisk.org
Sat Dec 15 04:51:47 CST 2018


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

Gregory Massel commented on ASTERISK-28209:
-------------------------------------------

The dialplan is not one that you're going to be able to replicate. It is complex uses a large number of func_odbc queries to dynamically route calls. 
The last dial plan action relating to these calls looks like this:

[Dec 13 08:42:17] VERBOSE[18865][C-00000539] pbx.c: Executing [s at swvpbx-sub-dialout:56] Dial("PJSIP/floraniche307-00000c25", "PJSIP/0216718077/sip:0333457349 at 196.216.192.4:5060,120,") in new stack
[Dec 13 08:42:17] VERBOSE[18865][C-00000539] app_dial.c: Called PJSIP/0216718077/sip:0333457349 at 196.216.192.4:5060

based on:

same  =>   n,Dial(PJSIP/${TRUNK}/sip:${NUMBER_DIALLED}@196.216.192.1:5060,120,${CALLOPT})

where ${CALLOPT} was empty, ${TRUNK} was 0216718077 and ${NUMBER_DIALLED} was 0333457349
in each and every case

> Repeated SegFaults on 16.1.0; stable on 13.24.0
> -----------------------------------------------
>
>                 Key: ASTERISK-28209
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28209
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: . I did not set the category correctly.
>    Affects Versions: 16.1.0
>         Environment: Ubuntu 16.04 LTS, E3-1285, 32GB RAM
>            Reporter: Gregory Massel
>            Assignee: Unassigned
>              Labels: fax, pjsip
>         Attachments: core-dump-2018-12-13-08h04-brief.txt, core-dump-2018-12-13-08h04-full.txt, core-dump-2018-12-13-08h04-locks.txt, core-dump-2018-12-13-08h04-thread1.txt, core-dump-2018-12-13-08h42-brief.txt, core-dump-2018-12-13-08h42-full.txt, core-dump-2018-12-13-08h42-locks.txt, core-dump-2018-12-13-08h42-thread1.txt, t38call2.pcap, t38call.pcap
>
>
> After upgrading to 16.1.0, Asterisk crashed six times in the space of an hour. After downgrading to 13.24.0, it has been rock solid for a number of days. Prior to that it was on 13.23.1 and rock solid for weeks.
> I cannot isolate which component is causing the issue, however, the one possible area in which this server is unique (versus another similar server that is running stable on 16.1.0) is that it uses res_odbc and func_odbc extensively. But blaming those components would be speculative.
> I have attached two backtraces from two different crash events.



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



More information about the asterisk-bugs mailing list