[asterisk-bugs] [JIRA] (ASTERISK-27314) chan_sip: Crash/Deadlock with realtime peers (MySQL)

[Kevin Harwell (JIRA)]

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

Kevin Harwell commented on ASTERISK-27314:
------------------------------------------

[~Cyril.r] since you state that going back to 13.9.1 works fine it's possible that a problem was introduced sometime between that version and the current one. If you could narrow down which version specifically it might help find the change that may be causing this. So for instance 13.17.2 is the current version, but does it happen in 13.13.0? If so then the change was before that version, 13.11.0?, etc...

Another thing you could try as well is see if this happens with the pjsip channel driver.

> chan_sip: Crash/Deadlock with realtime peers (MySQL)
> ----------------------------------------------------
>
>                 Key: ASTERISK-27314
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27314
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: General
>    Affects Versions: 14.5.0, 14.6.2, 15.0.0
>         Environment: Linux Ubuntu 16.04.3 LTS (4.4.0-96-generic)
>            Reporter: Cyril Ramière
>            Assignee: Unassigned
>            Severity: Critical
>              Labels: crash, deadlock
>         Attachments: asterisk-2017-10-04T15-15-31+0200.coredumps.tar.gz, asterisk.zip, core-asterisk-running-2017-10-04T15-15-31+0200-brief.txt, core-asterisk-running-2017-10-04T15-15-31+0200-full.txt, core-asterisk-running-2017-10-04T15-15-31+0200-full.txt, core-asterisk-running-2017-10-04T15-15-31+0200-locks.txt, core-asterisk-running-2017-10-04T15-15-31+0200-thread1.txt, core-asterisk-running-2017-10-04T15-15-31+0200.zip, core_show_locks.txt
>
>
> Hi, 
> I think I found a problem with asterisk > 13.x (tested on 14.5.0 & 14.6.2 & 15.0.0) & MySQL realtime.
> When there are two (or more) incoming calls made almost simultaneously, or the server is "under load", the asterisk server stops responding to INVITEs almost instantaneously, locks one CPU to 100%, then acts strange (it is not fully locked but it doesn't accept new calls, while keeping active calls up)
> Found out that when asterisk is "stuck", doing "realtime mysql status" in the console causes a segfault or freeze the console input.
> After digging through the problem, it seems that the "sippeers => mysql,asterisk,sipUsers" line in extconfig.conf is causing all the troubles.
> Note : sql schema should be fine, I used the file path/to/src/asterisk-x.x.x/contrib/realtime/mysql/mysql_config.sql, connection to the server is fine too.
> Even with an empty table the problem happens.
> I made my tests with SIPP to reproduce the issue, here is the command (or you can just "load" the server with real calls):
> (limit=10 calls at rate 3calls/sec to exten 1000)
> sipp -sn uac -d 600000 -s "1000" 10.1.1.104 -l 10 -r 3 -mp 5606
> Configuration is : 
> Ubuntu 16.04.3 LTS (4.4.0-96-generic)
> - sip.conf : my trunk
> - extensions.conf : static dialplan for test + switch realtime (not used for the test)
> - extconfig.conf : use for MOH, extensions, peers (problem here)
> - res_mysql.conf : our SQL server
> The exact same configurations is fine on our older asterisks V13.9.1 (no problems).
> Here are the "core show locks" result, dumps attached to the ticket.
> core show locks
> [Edit by Rusty - Removed and attached to issue as core_show_locks.txt - Please attached all lengthy debug to the ticket]



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