> Am 20.07.2017 um 08:13 schrieb Michael Knill
> <[email protected]>:
>
> core show taskprocessors
>
> Processor Processed In Queue Max
> Depth Low water High water
> subm:ast_channel_topic_all-00000039 5188 0
> 631 450 500
> subm:ast_channel_topic_all-cached-00000034 8091 0
> 1031 450 500
> subm:ast_channel_topic_all-cached-00000036 8090 0
> 1031 450 500
>
> Why so many?
>
> Regards
> Michael Knill
Michael,
are you using PJSIP or chan_sip on the Asterisk 13 box?
I run Asterisk 13 for about a year successfully on my office PBX with chan_sip.
Here is a list of a few modules that I don't load in Asterisk 13:
-----
noload => res_mwi_external.so ; Asterisk 13
noload => res_mwi_external_ami.so ; Asterisk 13
noload => res_ari_mailboxes.so ; Asterisk 13
noload => res_pjsip*.so ; Asterisk 13
noload => func_pjsip*.so ; Asterisk 13
noload => res_pjsip_phoneprov_provider.so ; Asterisk 13
noload => res_pktccops.so
noload => cel_custom.so
-----
Maybe that changes something.
Otherwise we could compare some configs …
For comparison:
-----
core show taskprocessors
Processor Processed In Queue Max Depth
Low water High water
...
...
subm:ast_channel_topic_all-0000007d 6440 0 15
450 500
subm:ast_channel_topic_all-cached-00000076 9520 0 25
450 500
subm:ast_channel_topic_all-cached-00000078 9519 0 25
450 500
...
...
135 taskprocessors
-----
> -----Original Message-----
> From: Michael Knill <[email protected]>
> Reply-To: AstLinux List <[email protected]>
> Date: Thursday, 20 July 2017 at 3:52 pm
> To: AstLinux List <[email protected]>
> Subject: Re: [Astlinux-users] Getting errors after upgrade to 1.2.10 Asterisk
> 13
>
> Nope removing all those modules didn't fix it. Sigh!
>
> Regards
> Michael Knill
>
> -----Original Message-----
> From: Michael Knill <[email protected]>
> Reply-To: AstLinux List <[email protected]>
> Date: Thursday, 20 July 2017 at 2:50 pm
> To: AstLinux List <[email protected]>
> Subject: Re: [Astlinux-users] Getting errors after upgrade to 1.2.10 Asterisk
> 13
>
> No I don't want to stay with 11 as its basically EoS and I want to move
> forward with the next LTS release.
> We are going to have a big push in the near future to get new systems in and
> I don't want to be going through this headache with more systems (
>
> Yes it could be something to do with my configuration. Hmm slow AMI handler.
> That's a thought!
> From the URL you posted, I also decided I would remove ARI modules as well. I
> don't see me using it in the near future as I can do everything via AMI.
>
> Regards
> Michael Knill
>
> -----Original Message-----
> From: Lonnie Abelbeck <[email protected]>
> Reply-To: AstLinux List <[email protected]>
> Date: Thursday, 20 July 2017 at 1:12 pm
> To: AstLinux List <[email protected]>
> Subject: Re: [Astlinux-users] Getting errors after upgrade to 1.2.10 Asterisk
> 13
>
> Michael,
>
> Is rolling back to Asterisk 11 a possibility for you, or are you using some
> of the new 13 features ?
>
> If you are the only person reporting this task processor warning in AstLinux,
> it may be a configuration issue, slow AMI handler, etc. unique to your setup.
>
> http://lists.digium.com/pipermail/asterisk-dev/2016-June/075616.html
>
> Lonnie
>
>
> On Jul 19, 2017, at 9:33 PM, Michael Knill
> <[email protected]> wrote:
>
>> No nothing I could find that actually helped. I really cant see that it is a
>> resource issue.
>> I have posted a message on the forum but Im not hopeful (
>>
>> In a bit of a pickle as I have a major customer waiting for this release.
>>
>> Regards
>> Michael Knill
>>
>> -----Original Message-----
>> From: Lonnie Abelbeck <[email protected]>
>> Reply-To: AstLinux List <[email protected]>
>> Date: Thursday, 20 July 2017 at 10:36 am
>> To: AstLinux List <[email protected]>
>> Subject: Re: [Astlinux-users] Getting errors after upgrade to 1.2.10
>> Asterisk 13
>>
>> Michael,
>>
>> Is there any pattern to get the warnings, like low RAM or low-end CPU ?
>>
>> Try googling "task processor queue reached 500 scheduled tasks again" ,
>> there are a lot of results related to this.
>>
>> Lonnie
>>
>>
>> On Jul 19, 2017, at 7:06 PM, Michael Knill
>> <[email protected]> wrote:
>>
>>> Ah I am getting it on my non VM sites too. I will try with PJSIP, HEP and
>>> CEL modules not loaded.
>>> Its statsis that is complaining but I actually cant work out whether I need
>>> it or not? It's the new message bus architecture but is it in place of the
>>> old or just a new one you can use?
>>> I use CDR and AMI so I need some form of this messaging architecture!
>>>
>>> Regards
>>> Michael Knill
>>>
>>> -----Original Message-----
>>> From: Michael Knill <[email protected]>
>>> Reply-To: AstLinux List <[email protected]>
>>> Date: Thursday, 20 July 2017 at 8:02 am
>>> To: AstLinux List <[email protected]>
>>> Subject: Re: [Astlinux-users] Getting errors after upgrade to 1.2.10
>>> Asterisk 13
>>>
>>> Thanks Lonnie. Perfect info.
>>> I will let you know how I go.
>>>
>>> Regards
>>> Michael Knill
>>>
>>> -----Original Message-----
>>> From: Lonnie Abelbeck <[email protected]>
>>> Reply-To: AstLinux List <[email protected]>
>>> Date: Wednesday, 19 July 2017 at 10:29 pm
>>> To: AstLinux List <[email protected]>
>>> Subject: Re: [Astlinux-users] Getting errors after upgrade to 1.2.10
>>> Asterisk 13
>>>
>>> Hi Michael,
>>>
>>> Not an issue with Asterisk 11 :-)
>>>
>>> Here is what Digium says about taskprocessors warnings ...
>>>
>>> Asterisk Task Processor Queue Size Warnings
>>> http://blogs.asterisk.org/2016/07/13/asterisk-task-processor-queue-size-warnings/
>>>
>>> Is the VM configured with only one CPU or core ?
>>>
>>> Lonnie
>>>
>>>
>>>
>>> On Jul 19, 2017, at 7:10 AM, Michael Knill
>>> <[email protected]> wrote:
>>>
>>>> Hi all
>>>>
>>>> Im not getting these errors on any other sites I have upgraded including a
>>>> VM site like this one but here they are:
>>>>
>>>> Jul 19 14:22:40 3017-Biz_Doctor-CM1 local0.warn asterisk[1107]:
>>>> WARNING[8574][C-000001aa]: taskprocessor.c:888 in taskprocessor_push: The
>>>> 'subm:ast_channel_topic_all-cached-00000079' task processor queue reached
>>>> 500 scheduled tasks again.
>>>> Jul 19 14:22:40 3017-Biz_Doctor-CM1 local0.warn asterisk[1107]:
>>>> WARNING[8576][C-000001aa]: taskprocessor.c:888 in taskprocessor_push: The
>>>> 'subm:ast_channel_topic_all-0000007e' task processor queue reached 500
>>>> scheduled tasks again.
>>>> Jul 19 14:49:51 3017-Biz_Doctor-CM1 local0.warn asterisk[1107]:
>>>> WARNING[8787][C-000001b0]: taskprocessor.c:888 in taskprocessor_push: The
>>>> 'subm:ast_channel_topic_all-cached-0000007b' task processor queue reached
>>>> 500 scheduled tasks again.
>>>>
>>>> Im struggling to find what they mean. Any ideas anyone?
>>>>
>>>> Regards
>>>> Michael Knill
Michael
http://www.mksolutions.info
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Astlinux-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to
[email protected].
