| Summary: | ASTERISK-26682: Device State stay stuck - maybe deadlock | ||
| Reporter: | Alex (alexeuro) | Labels: | agentstatus deadlock |
| Date Opened: | 2016-12-28 12:25:27.000-0600 | Date Closed: | 2016-12-29 17:41:52.000-0600 |
| Priority: | Major | Regression? | |
| Status: | Closed/Complete | Components: | |
| Versions: | 11.20.0 | Frequency of Occurrence | Frequent |
| Related Issues: | |||
| Environment: | Asterisk 11.20.0 Mysql 5.6 CentOS release 6.7 | Attachments: | ( 0) backtrace-threads.txt ( 1) core-show-locks.txt ( 2) core-show-threads.txt |
| Description: | The issue afflict a system that is a x86_64 machine used as callcenter.
Each Agent is assigned to many queues. Occasionally appears this issue: Asterisk doesn't read the correct state of the agents. It seems like asterisk queue some process and execute them with some delay. Behaviour: The free agents/users seem to be still connected, only they do not receive calls anymore. The state of SIP device stuck to "inuse" causing asterisk not to send anymore call to the agent using this SIP Phone. Some agents cannot change they state from ready to pause. Sometimes if they are in conversation they are paused from asterisk while in conversation because a pause input they released minutes before and managed by asterisk after minutes. We think that asterisk deadlocks. We attach reports of gdb -ex "thread apply all bt" --batch /usr/sbin/asterisk `pidof asterisk` > /tmp/backtrace-threads.txt asterisk -rx "core show locks" > /tmp/core-show-locks.txt asterisk -rx "core show threads" > /tmp/core-show-threads.txt this seems related to https://issues.asterisk.org/jira/browse/ASTERISK-12036?jql=text%20~%20%22cannot%20pause%22 | ||
| Comments: | By: Asterisk Team (asteriskteam) 2016-12-28 12:25:27.659-0600 Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report. Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process]. By: Alex (alexeuro) 2016-12-28 12:28:05.660-0600 backtrace-threads.txt core-show-locks.txt core-show-threads.txt By: Rusty Newton (rnewton) 2016-12-29 17:41:24.716-0600 Per the Asterisk versions page [1], the maintenance (bug fix) support for the Asterisk branch you are using has ended. For continued maintenance support please move to a supported branch of Asterisk. After testing with a supported branch, if you find this problem has not been resolved, please open a new issue against the latest version of that Asterisk branch. Thanks! [1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Versions | ||