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

[Kevin Harwell (JIRA)]

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

Kevin Harwell commented on ASTERISK-28229:
------------------------------------------

[~dice_telephony], just want to clarify to make sure. Is Asterisk actually crashing or is it "hanging"/stuck and another process is stopping and then restarting Asterisk?

I noticed this in one of the log files (2018_12_31_crash.txt) right before a restart:
{noformat}
[2018-12-31 09:15:11] WARNING[12694] db.c: Couldn't bind key to stmt: out of memory
{noformat}
What's the memory and cpu utilization look like on the system and by Asterisk? You can use something like "top" to see how much memory is available, being used, and free.

> 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: Unassigned
>         Attachments: ast_coredumper, 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-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-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-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)