[Home]

Summary:ASTERISK-28937: Task processor queue reached 500 scheduled tasks
Reporter:Shubham Agarwal (shubham.agarwal)Labels:
Date Opened:2020-06-07 12:31:35Date Closed:2020-06-22 12:00:01
Priority:MinorRegression?
Status:Closed/CompleteComponents:pjproject/pjsip
Versions:15.5.0 Frequency of
Occurrence		Frequent
Related
Issues:
Environment:Centos7Attachments:
Description:We are using realtime PJSIP. We are noticing task processor warning after which Asterisk disconnects to all the endpoints and stop accepting any new request.
We are using Asterisk 15.5 and Centos 7.

taskprocessor.c: The ‘pjsip/distributor-00000167’ task processor queue reached 500 scheduled tasks.

We are facing this issue very frequently. Please help us to get out of this.
Comments:By: Asterisk Team (asteriskteam) 2020-06-07 12:31:36.539-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: George Joseph (gjoseph) 2020-06-08 08:19:07.124-0500

First, 15.5.0 is two years old and not longer supported.  I'd suggest upgrading to the latest version of Asterisk 16.  Having said that, there are generally 2 reasons for pjsip taskprocessor backups...  Slow DNS queries and slow database queries.

* When did this issue start happening?
* What changed between being stable and the issue happening?
* Local or remote database server?
* If remote, ping times between the Asterisk server and the database server.
* Database software and version.
* If using ODBC, ODBC version.

To get a better understanding of what's going on, follow the instructions linked below to get a backtrace of the running Asterisk instance at the time the issue is happening.  This will give us a better idea of a root cause.

https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace

By: Asterisk Team (asteriskteam) 2020-06-22 12:00:00.738-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