[asterisk-bugs] [JIRA] (ASTERISK-24360) Asterisk deadlock
VoIPCamp (JIRA)
noreply at issues.asterisk.org
Fri Sep 26 13:21:30 CDT 2014
[ https://issues.asterisk.org/jira/browse/ASTERISK-24360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
VoIPCamp updated ASTERISK-24360:
--------------------------------
Attachment: core.ast1113.26sep-00.gdb.txt
GDB output of:
(gdb) bt
(gdb) bt full
(gdb) thread apply all bt
(gdb) info threads
> Asterisk deadlock
> -----------------
>
> Key: ASTERISK-24360
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-24360
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Applications/app_mixmonitor, Channels/chan_agent, Core/Channels, Core/ManagerInterface
> Affects Versions: 11.11.0, 11.12.0, 11.12.1, 11.13.0
> Environment: Centos release 6.5
> GNU/Linux 2.6.32-431.29.2.el6.x86_64
> Intel(R) Xeon(R) CPU E5506 @ 2.13GHz 8Gb RAM
> Reporter: VoIPCamp
> Attachments: core.ast1113.26sep-00.gdb.txt
>
>
> We originate calls using AMI with about 130 agents logged in (using AgentLogin) and recording with MixMonitor before entering any of the about 30 Queues. This is easily reproducible and happens twice a day in two different machines with similar specs.
> When in deadlock it's not possible to originate or receive more calls and it's confirmed by a "core show channels" in CLI where there is not output.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list