[asterisk-bugs] [JIRA] (ASTERISK-26601) res_pjsip: task_processors in queue pjsip stop working

[Joshua Colp (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-26601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joshua Colp updated ASTERISK-26601:
-----------------------------------

    Assignee: Carl Fortin
      Status: Waiting for Feedback  (was: Triage)

Nothing stands out in the log and while the taskprocessors list shows some things in queue, there's nothing huge.

What we'd need when Asterisk is in this state is a backtrace[1] to confirm that something internally is hung. With the information provided there's nothing really we can narrow down or look into.

[1] https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace#GettingaBacktrace-GettingInformationForADeadlock

> res_pjsip: task_processors in queue pjsip stop working
> ------------------------------------------------------
>
>                 Key: ASTERISK-26601
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26601
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>    Affects Versions: 14.1.1
>         Environment: Asterisk Realtime 14.1.0 rc1
>  PJSIP Driver
> mysql Ver 14.14
> 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: Carl Fortin
>         Attachments: full, task_procesor.txt
>
>
> 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)