[asterisk-bugs] [JIRA] (ASTERISK-26387) Asterisk segfaults shortly after starting even with no active calls.

[Richard Mudgett (JIRA)]

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

Richard Mudgett commented on ASTERISK-26387:
--------------------------------------------

Both ASTERISK-26387 and ASTERISK-26344 are likely the same issue.  I have been studying the logs from both issues.  I have noticed that on the ASTERISK-26387 logs there are OPTIONS ping responses for endpoint qualification that are being processed by a different serializer than the request.  This can cause reentrancy problems (e.g. crashes).  The outgoing OPTIONS requests go out on a pjsip/default serializer while the response is processed by a pjsip/distributor serializer because the distributor cannot find the original serializer that sent the request.  I also noticed that when this happened the updated contact status was reporting for an endpoint that needed DNS resolution (sip:sbc.anveno.com was one).  On the ASTERISK-26344 logs a similar thing is happening but I see it for outbound registration requests needing DNS resolution.  The REGISTER response is being processed by a pjsip/distributor serializer while the request went out on a pjsip/outreg serializer.

> Asterisk segfaults shortly after starting even with no active calls. 
> ---------------------------------------------------------------------
>
>                 Key: ASTERISK-26387
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26387
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>    Affects Versions: 13.11.0, 13.11.1, 13.11.2
>         Environment: Debian 8.5
>            Reporter: Harley Peters
>            Assignee: Unassigned
>         Attachments: backtrace-GIT-13-64b43d4M.txt, backtrace-GIT-13-64b43d4-with-console-logging-files.txt, backtrace.txt, backtrace.txt, combined-GIT-13-64b43d4.log, console-GIT-13-64b43d4.log, debug-GIT-13-64b43d4.log, gdb.txt, gdb.txt, security-GIT-13-64b43d4.log
>
>
> Asterisk segfaults shortly ( within minutes ) after starting even with no active calls.
> segfault at 78 ip 00007fbeec6a0da4 sp 00007fbed27b2960 error 4 in libasteriskpj.so.2[7fbeec600000+16a000]
> traps: asterisk[25526] general protection ip:7f1cd6ed9274 sp:7f1cbc0d9b50 error:0 in libpthread-2.19.so[7f1cd6ecf000+18000] 
> Asterisk 13.10.0 runs fine.



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