| Summary: | ASTERISK-28712: Possible freeze in app_queue | ||
| Reporter: | Martin Nyström (martin.nystrom) | Labels: | |
| Date Opened: | 2020-01-24 09:20:32.000-0600 | Date Closed: | 2020-02-07 12:00:00.000-0600 |
| Priority: | Minor | Regression? | |
| Status: | Closed/Complete | Components: | Applications/app_queue |
| Versions: | 13.24.0 | Frequency of Occurrence | Occasional |
| Related Issues: | |||
| Environment: | Centos 7.5Asterisk 13.24.0 with Realtime | Attachments: | |
| Description: | Hello,
We are randomly experiencing freezes in what it seems app_queue. It manifests itself with not letting new calls entering any queue, no new calls passed to the agents. Existing calls work just fine i.e. already ongoing. Typing in cli “queue show X” locks the CLI. Only way to release the issue to restart asterisk with “systemctl restart asterisk” for an example. For Incoming calls passed through AGI this is the last we see for each call {noformat} [2020-01-21 14:02:33] VERBOSE[32522][C-0001ad37] res_agi.c: AGI Script Executing Application: (QUEUE) Options: (Incoming1,xXr,,,3600,,,v-mixmonit,,) {noformat} For direct calls to a queue this is the last we see {noformat} [2020-01-21 14:11:59] VERBOSE[12588][C-0001ae8c] pbx_realtime.c: Executing [+44HIDDDEN@from-voip-provider:9] Set("SIP/siptrunk-0002f6a7", " ANSWER=1") [2020-01-21 14:11:59] VERBOSE[12588][C-0001ae8c] pbx_realtime.c: Executing [+44HIDDDEN @from-voip-provider:10] Queue("SIP/siptrunk-0002f6a7", "Incoming1,xX,,,300,,,,,") [2020-01-21 14:12:53] VERBOSE[25425][C-0001ae8c] chan_sip.c: Sending to 13.48HIDDEN:5060 (NAT) [2020-01-21 14:12:53] VERBOSE[25425][C-0001ae8c] chan_sip.c: Scheduling destruction of SIP dialog '37257e8f6af95992127284ce06dae69a@18.194HIDDEN:5060' in 6400 ms (Method: BYE) [2020-01-21 14:12:53] VERBOSE[25425][C-0001ae8c] chan_sip.c: {noformat} Yes, the last line is empty after chan_sip.c, the call gets no further. We are not sure to replicate this and it occurs sporadically. When it occurs, what measures can I do to capture more information? We cannot run Asterisk in debug mode if it impacts performance as this issue can take weeks to occur again. Am putting this as a Minor, as we do not know yet what is causing it. /M | ||
| Comments: | By: Asterisk Team (asteriskteam) 2020-01-24 09:20:33.497-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]. Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur. By: Joshua C. Colp (jcolp) 2020-01-24 09:26:43.090-0600 We suspect that you have a deadlock occurring within Asterisk. Please follow the instructions on the wiki [1] for obtaining debug relevant to a deadlock. Once you have that information, attach it to the issue. Be sure the instructions are followed exactly as the debug may otherwise not be useful. Thanks! [1] https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace#GettingaBacktrace-GettingInformationForADeadlock By: Asterisk Team (asteriskteam) 2020-02-07 12:00:00.540-0600 Suspended due to lack of activity. This issue will be automatically re-opened if the reporter posts a comment. If you are not the reporter and would like this re-opened please create a new issue instead. If the new issue is related to this one a link will be created during the triage process. Further information on issue tracker usage can be found in the Asterisk Issue Guidlines [1]. [1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines | ||