| Summary: | ASTERISK-27556: consumes high process in core show task processors [stasis-core & stasis-core-processors] | ||
| Reporter: | Omar Galaviz (ogalaviz) | Labels: | pjsip |
| Date Opened: | 2018-01-05 15:40:00.000-0600 | Date Closed: | 2020-01-14 10:25:25.000-0600 |
| Priority: | Critical | Regression? | No |
| Status: | Closed/Complete | Components: | . I did not set the category correctly. |
| Versions: | 14.7.2 | Frequency of Occurrence | Constant |
| Related Issues: | |||
| Environment: | system operating centos 7.4, FREEPBX 14, ASTERISK 14.7.2 HP PROLIANT DL160 Intel XEON E5-2609v4 8-Core 8GB DDR4, hard disk SATA 7200 RPM | Attachments: | |
| Description: | The average call is 120 concurrent calls with g729
the extensions are of type chan_sip, there is no pjsip configured. Our central is configured up to 20 queues for 105 agents Our problem arises with an exponential increase of processes statis-core and statis-core-controls, that happens once the queues are activated and the agents are connected to them. core show taskprocessers stasis-core 950186630 0 173 450 500 stasis-core-control 1834102157 0 2862 450 500 the calls are hung, high jitter and the asterisk is saturated, we must continuously restart asterisk. please, can you help us, what should we do to minimize this impact and reduce the processes in the aforementioned processes thanks.... | ||
| Comments: | By: Asterisk Team (asteriskteam) 2018-01-05 15:40:01.493-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: Kevin Harwell (kharwell) 2018-01-09 17:53:27.948-0600 The current issue description is too broad in scope. Unfortunately, we cannot work on this because your description did not include enough information. Please read over the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] which discusses the information necessary for your issue to be resolved and the format that information needs to be in. We would be grateful if you would then provide a more complete description of the problem. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected and the location of documentation that led you to that expectation. 3. The behavior you actually encountered. To demonstrate the issue in detail, please include Asterisk log files generated per the instructions on the wiki, [collecting debug information|https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information]. If applicable, please ensure that protocol-level trace debugging is enabled, e.g., 'sip set debug on' if the issue involves chan_sip, and configuration information such as dialplan and channel configuration. As it currently stands this seems more like a support request vs. a bug. You might be better served asking about your problem in a different forum. At the very least someone in one of those forums might be able to help you narrow the scope a bit and determine if you are dealing with an actual bug. The Asterisk community provides support over IRC, mailing lists, and forums as described at http://asterisk.org/community. The Asterisk issue tracker is used specifically to track issues concerning bugs and documentation errors. Please see the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] for instruction on the intended use of the Asterisk issue tracker. Thanks! By: Asterisk Team (asteriskteam) 2018-01-24 12:00:01.359-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 | ||