Hi, good morning,
I have searching but i didn’t the solution. I have a new asterisk pbx with Asterisk 13.21 and i receive many messages about stasis-core and stasis-core-control taskprocessors:
WARNING taskprocessor.c: The ‘stasis-core’ task processor queue reached 500 scheduled tasks again.
WARNING taskprocessor.c: The ‘stasis-core-control’ task processor queue reached 500 scheduled tasks again.
We have modules.conf with stasis noload and we don’t use any API that use it so that i don’t know why asterisk show this. Can you help me?
Stasis in this context refers to the message bus internally in Asterisk which is used by many things. These messages seem to indicate that something which is handling messages is taking a substantial amount of time, causing things to pile up. I’d suggest first upgrading to the latest 13 which has performance improvements in this area, if that does not work then you’d need to describe and provide information about how exactly you are using Asterisk.
First of all, thanks for the reply. Ok, first we upgrade the asterisk firmware.
Other thing that I see, are generating many subprocesses of each extension that I don’t know exactly where they can come from and that accumulate until the service is restarted, for example:
subp:00000101130-000003d0 57 0 1 450 500
subp:00000101130-000003e1 56 0 1 450 500
subp:00000101130-000003f7 55 0 1 450 500
subp:00000101130-0000040e 54 0 1 450 500
subp:00000101130-0000042e 53 0 1 450 500
subp:00000101130-00000442 52 0 1 450 500
subp:00000101130-00000456 51 0 1 450 500
They are not subprocesses but internal subscriptions for the endpoint. Without knowledge of how Asterisk is used it’s hard to be able to say whether it’s abnormal or not.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.