[asterisk-bugs] [JIRA] (ASTERISK-28997) res_pjsip: Asterisk locks up and stops processing any SIP requests

[Yury Kirsanov (JIRA)]

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

Yury Kirsanov commented on ASTERISK-28997:
------------------------------------------

Joshua,
I've removed that module from loading, it looks that we had sorcery.conf from very old Asterisk version unchanged, I can confirm that current Asterisk release don't have sorcery.conf configured for PJSIP. We had to load res_sorcery_memory_cache.so because of the fact we had old sorcery.conf configured for PJSIP and PJSIP wasn't loading without this memory cache. Now I have disabled sorcery configuration by putting a blank sorcery.conf and was able to load Asterisk with PJSIP successfully. I will monitor it and report here if it crashes/locks up. Thanks a lot for your help!


> res_pjsip: Asterisk locks up and stops processing any SIP requests
> ------------------------------------------------------------------
>
>                 Key: ASTERISK-28997
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28997
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_pjsip, Resources/res_sorcery_memory_cache
>    Affects Versions: 16.11.1
>         Environment: Ubuntu Linux 18.04.4 LTS, kernel 4.15.0-111-generic
>            Reporter: Yury Kirsanov
>            Assignee: Unassigned
>            Severity: Minor
>              Labels: fax
>         Attachments: backtrace-threads.txt, taskprocessors.txt, threads.txt
>
>
> Hi,
> We have a problem with one of many of our Asterisk-based servers. From time to time it just locks up and stops processing SIP messages, complaining about pjsip/distributor queue has reached 500 scheduled tasks. We have several servers based on same Asterisk version with exactly the same environment, but different Asterisk configuration files, some have more SIP devices and more complex dial plans, some has less.
> This issue happens at any time of the day and I don't see any way to reproduce it. There is no segfault generated as Asterisk keeps running, the only thing is that all distributor queues are overflown for some reason.
> After Asterisk restart it starts to work like nothing happened. I've checked all network interfaces and there is no DDoS attack or anything like that.
> Our Asterisk is patched with ASTERISK-28923 patch and it's the same server that was segfaulting before. Other similar servers are running unpatched version of Asterisk 16.11.1.
> I'm attaching debug logs that I was able to grab during this lockup. Asterisk was compiled with 'NO_DEBUG' option.
> Please let me know if I can provide any additional information or recompile Asterisk with some additional debug versions. Thanks!



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