[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:all-tabpanel ]

Jerry Corrion updated ASTERISK-28229:
-------------------------------------

    Attachment: core-asterisk-running-2019-01-10T11-53-34-0800-thread1.txt
                core-asterisk-running-2019-01-10T11-53-34-0800-locks.txt
                core-asterisk-running-2019-01-10T11-53-34-0800-full.txt
                core-asterisk-running-2019-01-10T11-53-34-0800-brief.txt
                core-asterisk-running-2019-01-10T11-49-33-0800-thread1.txt
                core-asterisk-running-2019-01-10T11-49-33-0800-locks.txt
                core-asterisk-running-2019-01-10T11-49-33-0800-full.txt
                core-asterisk-running-2019-01-10T11-49-33-0800-brief.txt
                core-asterisk-running-2019-01-10T09-05-23-0800-thread1.txt
                core-asterisk-running-2019-01-10T09-05-23-0800-locks.txt
                core-asterisk-running-2019-01-10T09-05-23-0800-full.txt
                core-asterisk-running-2019-01-10T09-05-23-0800-brief.txt

> 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, core-asterisk-running-2019-01-10T09-05-23-0800-brief.txt, core-asterisk-running-2019-01-10T09-05-23-0800-full.txt, core-asterisk-running-2019-01-10T09-05-23-0800-locks.txt, core-asterisk-running-2019-01-10T09-05-23-0800-thread1.txt, core-asterisk-running-2019-01-10T11-49-33-0800-brief.txt, core-asterisk-running-2019-01-10T11-49-33-0800-full.txt, core-asterisk-running-2019-01-10T11-49-33-0800-locks.txt, core-asterisk-running-2019-01-10T11-49-33-0800-thread1.txt, core-asterisk-running-2019-01-10T11-53-34-0800-brief.txt, core-asterisk-running-2019-01-10T11-53-34-0800-full.txt, core-asterisk-running-2019-01-10T11-53-34-0800-locks.txt, core-asterisk-running-2019-01-10T11-53-34-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)