[asterisk-bugs] [JIRA] (ASTERISK-28229) Asterisk not responding/reloading

[Jerry Corrion (JIRA)]

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

Jerry Corrion commented on ASTERISK-28229:
------------------------------------------

I don't believe the issue would have been happening during this backtrace (but we also wouldn't have a way to know until it crashed, either). The problem itself hasn't shown in a few days, so we're back to playing the waiting game. Is it safe to run Asterisk with all the debug flags on while we wait for this to happen? The article you linked earlier indicated the following... {quote}Enabling DEBUG_THREADS can seriously impact performance and should only be enabled if you suspect a deadlock may be occurring.{quote}
The article doesn't go into detail about how performance can be impacted, so we didn't think it was a good idea to keep this running on a production machine, since none of us knew what to expect. If we do keep this running, how would performance be impacted? Would we expect calls to drop/delay, or would this just be an instance of high CPU use? 

It bears mentioning, but this PBX is used at a call center for public safety events and we cannot have extended downtime - for this reason, we use monit on the system to reboot asterisk once it experiences an issue. Am I correct in assuming that to get the data you need, we will need to let this system go down without an automatic reboot so we can get the deadlock information while it's in this state?

> Asterisk not responding/reloading
> ---------------------------------
>
>                 Key: ASTERISK-28229
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28229
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/General, Core/PBX, PBX/General
>    Affects Versions: 13.22.0
>         Environment: CentOS 6.5 (Final), 4GB RAM, 2 core processor, 40GB HD FreePBX 12.0.33
>            Reporter: Jerry Corrion
>            Assignee: Jerry Corrion
>         Attachments: 2018_12_28_crash(standard).zip, 2018_12_31_crash(debug).zip, 2019_01_01_crash(debug).zip, ast_coredumper, core-asterisk-running-2019-01-07T11-47-29-0800-brief.txt, core-asterisk-running-2019-01-07T11-47-29-0800-full.txt, core-asterisk-running-2019-01-07T11-47-29-0800-locks.txt, core-asterisk-running-2019-01-07T11-47-29-0800-thread1.txt, core-asterisk-running-2019-01-07T11-53-43-0800-brief.txt, core-asterisk-running-2019-01-07T11-53-43-0800-full.txt, core-asterisk-running-2019-01-07T11-53-43-0800-locks.txt, core-asterisk-running-2019-01-07T11-53-43-0800-thread1.txt
>
>
> Asterisk is reloading itself, sometimes several times a day. We do receive notifications from monit when this happens (failed protocol test [SIP] at [127.0.0.1]:5060 [UDP/IP] -- SIP: error receiving data -- Resource temporarily unavailable) and it will restart itself. We've been looking through logs trying to find something that triggers this. The best we can get is Asterisk stops communicating/responding to SIP until asterisk is reloaded. 



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