[asterisk-bugs] [JIRA] (ASTERISK-28093) pbx: Deadlock from holding channel lock when it shouldn't be
Joshua C. Colp (JIRA)
noreply at issues.asterisk.org
Mon Oct 15 05:36:55 CDT 2018
[ https://issues.asterisk.org/jira/browse/ASTERISK-28093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joshua C. Colp updated ASTERISK-28093:
--------------------------------------
Status: Open (was: Triage)
> pbx: Deadlock from holding channel lock when it shouldn't be
> ------------------------------------------------------------
>
> Key: ASTERISK-28093
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-28093
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Core/PBX
> Affects Versions: 13.18.5, 13.22.0, 13.23.1
> Environment: Debian 8.11 64 bits
> Intel(R) Xeon(R) CPU E5-2660 v4 @ 2.00GHz - 8 cores
> 32GB RAM
> Reporter: Nicolas Tanski
> Assignee: Unassigned
> Labels: crash, deadlock
> Attachments: backtrace-threads.txt, messages-20181005
>
>
> Hi Team,
> we are experiencing frequent crash issues in the Asterisk instance, we are using our own dialer solution with AMI protocol.
> The Asterisk service operates on average with 250 simultaneous calls, 40 record calls, the load is between 1 and 3, in some cases the load quickly rises to 10, which causes the rejection of new calls and the instance of Asterisk does not respond.
> We were only able to restart the service by killing the Asterisk service with the Kill PID command.
> It was enabled the flags DONT_OPTIMIZE, BETTER_BACKTRACES and MALLOC_DEBUG to try identify the problem.
> Summary
> Average simultaneous calls: 347
> Average record calls: 40
> Load Average: > 1 and < 3
> High Load Average: 25.26
> After the crash in Asterisk, we execute the commands and the service returns to normal operation
> \# kill -9 PID_ASTERISK
> \# /etc/init.d/asterisk start
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list