Help - task processor queue reached

General
1

I’m running freePBX 17 and have been running it for about 4/5 weeks now on a VM running 30gb storage and 12gb ram. I have around 30 sip phones and at most probably only have 4 to 5 max calls at once.

Today I decided to run the Asterisk CLI in SSH and I noticed a warning error that kept popping up every few minutes saying:

taskprocessor_push: The ‘stasis/pool-control’ task processor queue reached 500 scheduled tasks again

I then ran this command:

asterisk -rx "core show taskprocessors"

And this was the result:

stasis/pool-control    77937811   0   2467   450   500

Processed: 77937811
In Queue: 0
Max Depth: 2467
Low Water: 450
High Water: 500

I then rebooted the server and when it came back up. With system on idle (office is closed, no one using the system) and with my PHP script that calls AMI completely disabled, I ran this command when server came back online:

asterisk -rx "core show taskprocessors" | grep -c '^stasis/p:'

and the result showed 79 then climbed to 80 little while later.

Also monitored by running this:

asterisk -rx "core show taskprocessors"

And the total processed for stasis/pool-control seems like the tally is increasing even though system is pretty much idle with no one using it.

Can anyone please advise? Max Depth: 2467 seems like the biggest red flag and concerned when it will just climb again.

Would really appreciate some help trying to solve this.

Thank you in advance :pray:

2

I ran this command:

asterisk -rx "core show taskprocessors" | grep stasis/p:

And i basically have an stasis/p:endpoint:PJSIP/ for each extension like this:

stasis/p:endpoint:PJSIP/301-0000001d                                            1          0          1        450        500

I then have these four:

stasis/p:endpoint:PJSIP/dpma_endpoint-00000044                                  1          0          1        450        500
stasis/p:endpoint:PJSIP/SIPTrunk-00000043                                       1          0          1        450        500
stasis/p:manager:core-000000dc                                                436          0         56        450        500
stasis/p:manager:core-000000dd                                                221          0          8        450        500

Then for each extension I seem to have a MWI but I dont use voicemail subscription. so is this using up the stasis pool?

stasis/p:mwi:all/401@default-000000b7						2          0          1        450        500

Monitoring it, using this command:

asterisk -rx "core show taskprocessors" | grep -c '^stasis/p:'

Seems to only be showing it increase. So it seems like the pool just gets clogged up.

Is there anything I can do to optimize this? should I increase the 500 limit?

3

*** UPDATE ***

I just analysed the daily full log files and searched for the stasis warning and observed the following pattern:

  • The warnings start appearing daily around 8:55 AM, before the office opens at 9 AM.
  • They continue throughout the working day, often just minutes apart.
  • The warnings stop appearing after office hours (around 5 PM).
  • On one occasion, the logs showed warnings continuing until 9 PM.

No warnings appear on weekends or during inactive periods.

Combined with normal office-day call activity, voicemail interactions, device registrations, and FreePBX modules seem to generate enough real-time events to overload the stasis message pool. Will this have a performance issue on the system or effect end-users ?

The issue is clearly tied to active hours and real-world call flow, not rogue scripts or background jobs.

Should I leave it as it is or is it advisable to increase the 500 threshold? I have 12gb ram on the VM with 2 VCores so would it be advisable to increase this? Or can I somehow turn off unnessary tasks that use up the pool threshold?

All I am using the system for is SIP Yealink phones to dial internal and external. Only two dedicated extensions have voicemail to email but they aren’t extensions that have a SIP phone. I am just using them as a Voice Mailbox account. All other extensions have voicemail disabled per extension.