Customer box (100% PJSIP) stopped accepting calls this morning - looking through the logs, I am seeing a lot of warnings about stasis/m:
taskprocessor.c: The ‘stasis/m:channel:all-00000103’ task processor queue reached 500 scheduled tasks again.
It’s always the 102 or 103 processor - Here are their stats after the box has been up for about 2 hours:
Processor Processed In Queue Max Depth Low water High water
stasis/m:channel:all-000000fd 5 0 2 450 500
stasis/m:channel:all-00000100 4 0 2 450 500
stasis/m:channel:all-00000101 349791 0 981 450 500
stasis/m:channel:all-00000102 349790 0 1092 450 500
stasis/m:channel:all-00000107 1 0 1 450 500
Just noticed that 103 is not running now? What do these processors do?
But it’s not the same processor and I have made sure there are no loops and already had gotten rid of all the extraneous stuff as suggested.
I also looked here: Asterisk Task Processor Queue Size Warnings ⋆ Asterisk
But I kind of need CDR’s - Do I need CEL? Some threads say kill it, but other threads say eventually CDR is going away so I don’t know what to believe on that account.
This is the first actual production CRASH I have had in probably 8 years - freaked me out! Asterisk 18.2.2/FreePBX15 - everything current with all modules and packages up to date.
fwconsole restart said it could not stop Asterisk so that is why I rebooted.
They have no Queues - Only Ring Groups. They are using Sangoma Connect with 9 users and 25 regular extensions.
They do do 3 things weird:
- All Calls Ring All Phones - Crazy, I know but they insist.
- They do All-Pages (every extension) about 15 times an hour after they park a call.
- Two extensions are a BLF on every single phone there.
Machine is a Hyper-V machine with 8G and 4 Processors - CPU never gets above 5% in top.
Any ideas? I can’t have it crashing…