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

[Gregory Massel (JIRA)]

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

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

Also what is different on this server versus the other (that is stable), is that this one qualifies its pjsip contacts.

I note that there has been a fair amount of work in the qualification code for Asterisk 16.1.0.

It would appear that the above calls are all T.38 and all to/from the same destination, however, critically it also appears that there may have been a qualification event at the same time as the calls that may have seen the contact as being unreachable.

> 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)