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

Richard Mudgett (JIRA) noreply at issues.asterisk.org
Fri Jan 13 22:31:10 CST 2017


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

Richard Mudgett commented on ASTERISK-26601:
--------------------------------------------

I don't think the app_voicemail task processor is backing up a second time when PJSIP stops working.  However, I have created a patch to log the warning each time a task processor hits its high water mark \[1] to create a high water alert instead of only once per Asterisk restart.  Without this patch, you would actually have to enable at least {{core set debug 3}} logging to know if the high water limit was hit again.  Given that this takes a couple weeks to happen that could fill up a hard drive with logs.

Have you verified if packets are reaching the Asterisk server?
A pcap would show the packets reaching the server.
{{pjsip set logger on}} will show if Asterisk is even seeing packets.
At least {{core set debug 3}} will output messages \[2] if it ignores incoming messages due to a task processor high water alert.

\[1] https://gerrit.asterisk.org/#/c/4721/
\[2] https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information

> 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, core-show-locks.txt, Debug_Asterisk_Backtrace.sh, Debug_log.txt, extconfig.conf, full, res_odbc.conf, sorcery.conf, task_procesor.txt, Task_processors_list2.txt, Task_processors_list.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