| Summary: | ASTERISK-28516: Crash Under AMI Taskprocessor Backup | ||
| Reporter: | Joshua Elson (joshelson) | Labels: | |
| Date Opened: | 2019-08-29 14:02:11 | Date Closed: | 2019-09-17 12:00:03 |
| Priority: | Major | Regression? | |
| Status: | Closed/Complete | Components: | Core/ManagerInterface |
| Versions: | 16.4.0 | Frequency of Occurrence | |
| Related Issues: | |||
| Environment: | CentOS 7 | Attachments: | ( 0) brief.txt ( 1) full.txt ( 2) locks.txt ( 3) thread1.txt |
| Description: | Seeing an interesting and possibly reproducible crash under a significant AMI taskprocessor backup. Crash path seems directly unrelated, but we can generate this condition with significant numbers of concurrent connection attempts to the AMI interface while the box is under "normal" other call load. | ||
| Comments: | By: Asterisk Team (asteriskteam) 2019-08-29 14:02:12.842-0500 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 Elson (joshelson) 2019-08-29 14:04:56.137-0500 Backtrace here. By: Joshua C. Colp (jcolp) 2019-09-03 05:50:54.183-0500 What is the specific conditions/scenario that reproduces this? For example the crash itself occurred within MixMonitor usage, not AMI, so full information is needed. By: Asterisk Team (asteriskteam) 2019-09-17 12:00:02.895-0500 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 | ||