[asterisk-bugs] [JIRA] (ASTERISK-30294) Many "task processor queue reached 500 scheduled tasks again" messages might cause Asterisk down.

[Asterisk Team (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-30294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=260610#comment-260610 ] 

Asterisk Team commented on ASTERISK-30294:
------------------------------------------

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. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed.

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.

Please note that by submitting data, code, or documentation to Sangoma through JIRA, you accept the Terms of Use present at [https://www.asterisk.org/terms-of-use/|https://www.asterisk.org/terms-of-use/].

> Many "task processor queue reached 500 scheduled tasks again" messages might cause Asterisk down.
> -------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-30294
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-30294
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_stasis, Resources/res_stasis_device_state
>    Affects Versions: 16.16.1
>         Environment: CentOS 7.9.2009
> Issabel PBX + Asterisk 16.16.1
>            Reporter: Noppakoon Khamklin
>            Severity: Critical
>
> We got too many messages about task processor like this.
> [2022-11-08 13:31:00] WARNING[19354][C-000125c3] taskprocessor.c: The 'stasis/m:cache_pattern:1/channel:all-000003af' task processor queue reached 500 scheduled tasks again.
> And few of this below.
> [2022-11-08 13:42:55] WARNING[315] taskprocessor.c: The 'stasis/m:devicestate:all-00000003' task processor queue reached 500 scheduled tasks again.
> And at around 13:38, there were UREACHABLE alerts of all extensions (around 4xx IP Phone).  Then around 13:42:xx, all IP Phones were back Reachable again and all operation were back to normal.  During 4 or 5 mins, the Asterisk stopped working temporarily.  
> From the forum, it seems to be the workload issue but don't know how to investigate further and no clear solution.
> 1. We want to know what operation exactly caused the task processor messages and asterisk crash. 
> 2. Also are there documentation about "stasis/m:cache_pattern:1/channel:all-000003af" and "stasis/m:devicestate:all-00000003" so we can understand how to troubleshoot the problem?
> This problem already happened 3 times and we don't know when it will happen again.



--
This message was sent by Atlassian JIRA
(v6.2#6252)