[asterisk-bugs] [JIRA] (ASTERISK-26601) app_voicemail: task_processor backed up

Richard Mudgett (JIRA) noreply at issues.asterisk.org
Fri Jan 20 11:03:10 CST 2017


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

Richard Mudgett edited comment on ASTERISK-26601 at 1/20/17 11:01 AM:
----------------------------------------------------------------------

I just got the bug 15 minutes ago. I had the following warning sent to me by Graylog:

The 'pjsip/mwi-00000501' task processor queue reached 500 scheduled tasks...

I can now confirm that nothing is happening in the console and packets are not reaching the server.(see Console_output.txt)
Check my bash script,  to see how I have extracted the backtraces and other files.

The problem points toward the mwi.

Could this be the fact that our Cisco phone behave the way described in this  issue:

ASTERISK-26548







was (Author: phonefxg):
I just got the bug 15 minutes ago. I had the following warning sent to me by Graylog:

The 'pjsip/mwi-00000501' task processor queue reached 500 scheduled tasks...

I can now confirm that nothing is happening in the console and packets are not reaching the server.(see Console_output.txt)
Check my bash script,  to see how I have extracted the backtraces and other files.

The problem points toward the mwi.

Could this be the fact that our Cisco phone behave the way described in this  issue:

https://issues.asterisk.org/jira/browse/ASTERISK-26548






> app_voicemail: task_processor backed up
> ---------------------------------------
>
>                 Key: ASTERISK-26601
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26601
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_voicemail, Resources/res_pjsip
>    Affects Versions: 14.1.1
>         Environment: Asterisk Realtime 14.1.0 rc1
> PJSIP Driver
> mysql Ver 5.1.73
> pjproject 2.5.5
> spandsp 0.0.6
> jansson 2.7
> CentOS 6.6 64 bits on Vmware
> Number of phones : 700
> Average concurrent calls: 16
>            Reporter: Carl Fortin
>            Assignee: Unassigned
>         Attachments: backtrace-threads.txt, backtrace-threads.txt, Channel_list.txt, Console_output.txt, core-show-locks.txt, core-show-locks.txt, Debug_Asterisk_Backtrace.sh, Debug_log.txt, extconfig.conf, full, full-log-before- restarting.txt, messages.txt, res_odbc.conf, sorcery.conf, task_procesor.txt, Task_processors_list2.txt, Task_processors_list.txt, Task_processors_list.txt, Task_Processor_Starting_Asterisk.txt, voicemail.conf, voicemail_messages.sql, voicemail_users.sql
>
>
> I had Asterisk 14.1.0-rc1  running for 3 weeks, and all of the sudden PJSIP stopped working. Nothing in the console.
> I had time to save the task_processor output before restarting asterisk.
> After doing a restart to get the system back on I can see this in the log files:
> taskprocessor.c: The 'app_voicemail' task processor queue reached 500 scheduled tasks.
> I did not find any message concerning taskprocessor before the system stopped functioning.
> I'm aware that I am running an RC release, but looking at the release note, there were nothing concerning deadlock so I was thinking updating later.
>  



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



More information about the asterisk-bugs mailing list