[asterisk-bugs] [JIRA] (ASTERISK-28368) Low performance. Many errors taskprocessor

[Alexandre Keller (JIRA)]

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

Alexandre Keller commented on ASTERISK-28368:
---------------------------------------------

I  do have the same issues with Asterisk 16.17.0 using WebRTC + PJSIP endpoints.

Any ideas?

> Low performance. Many errors taskprocessor 
> -------------------------------------------
>
>                 Key: ASTERISK-28368
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28368
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: pjproject/pjsip
>    Affects Versions: 16.2.1
>         Environment: Centos7  kernel 3.10.0-862.9.1.el7.x86_64
> FreePBX  14.0.5.25
> FOP2
> pjsip 2.8
>            Reporter: Nikolay shakin
>            Assignee: Unassigned
>            Severity: Major
>              Labels: pjsip
>         Attachments: debug_log_taskproc.zip, full.zip, Screenshot_44.png, Screenshot_45.png, Screenshot_47.png, Screenshot_48.png
>
>
> I use Asterisk with FreePBX for call-center about 50 users and 30-50 calls. 
> A Dialplan of the server is ordinary(generated by FreePBX) + few web-hooks added by me, I use queues with rrmemory strategy. 
> I have many warnings at log, and a problem with pjsip, sometime we don't answer to invites at the time (delay more then 3 seconds), and other side think we are dead. If I ping taskprocessor of the trunk (core ping  taskprocessor subp:PJSIP/trunk_name-22222) at the moment, it shows 5 seconds delay. 
> What did I tried:
> -change hardware (another server)
> -disable CDR
> -disable CEL
> -enable all possible AMI filters
> -increase threadpool pjsip
> But it does not help, I still have the problem.
> And one more strange thing, CPU load is too high for 30 calls, I have almost  the same configuration on asterisk 13(chan_sip) and there are no similar problems or CPU usage.
> I have warnings like this:
> {quote}
> [2019-04-02 10:29:16] WARNING[61361][C-00001f86]: taskprocessor.c:913 taskprocessor_push: The 'stasis-core-control' task processor queue reached 500scheduled tasks again.
> [2019-04-02 10:30:04] WARNING[16800]: taskprocessor.c:913 taskprocessor_push: The 'subm:manager_topic-00000006' task processor queue reached 3000 scheduled tasks again.
> [2019-04-02 10:30:14] WARNING[62357][C-00001fa4]: taskprocessor.c:913 taskprocessor_push: The 'subm:manager_topic-00000006' task processor queue reached 3000 scheduled tasks again.
> [2019-04-02 10:30:50] WARNING[63620][C-00001fbd]: taskprocessor.c:913 taskprocessor_push: The 'subp:ast_channel_topic_all-000023d8' task processor queue reached 500 scheduled tasks.
> [2019-04-02 10:30:50] WARNING[63620][C-00001fbd]: taskprocessor.c:913 taskprocessor_push: The 'subp:ast_channel_topic_all-0000209e' task processor queue reached 500 scheduled tasks again.
> [2019-04-02 10:32:34] WARNING[65533][C-00001fec]: taskprocessor.c:913 taskprocessor_push: The 'subm:manager_topic-00000006' task processor queue reached 3000 scheduled tasks again.
> {quote}
> The worst thing is I can't even get normal log, because if I enable pjsip logger and core debug I have logger errors like these: 
> {quote}
> [2019-04-02 12:01:47] WARNING[24275]: logger: ***: Log queue threshold (1000) exceeded.  Discarding new messages.
> [2019-04-02 12:01:47] WARNING[16799]: logger: ***: Logging resumed.  220 messages discarded.{quote}



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