[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=245876#comment-245876 ] 

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

Oh, that makes sense, sorry about the confusion. I've attached the shorter versions of the debug log files- unfortunately the full logs are much too large to be attached. Hopefully they are of some help. As for our setup, we're running on a VM with the following:

Hypervisor:    VMware ESXi, 5.5.0, 1623387 
Model:    PowerEdge R720 
Processor Type:    Intel(R) Xeon(R) CPU E5-2609 0 @ 2.40GHz 
Utilizing both mysql and conf files.

This build in particular is used in a 24/7 call center environment with roughly 20 users utilizing an autodialer service. Call flow consists of incoming calls ringing into a queue of about 14 people utilizing a ring-all strategy. Typically there are no more than a couple dozen calls during peak times (this includes calls waiting in queue). Lately we've begun seeing consistent issues around 8:30 - 9:00 a.m. log time (it also occurs at other times of the day, but most consistently here.) 

Please let me know if there is any other further information I can provide that will be of assistance!
(still working on getting that debug log)

> 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: 2018_12_28_crash(standard).zip, 2018_12_31_crash(debug).zip, 2019_01_01_crash(debug).zip
>
>
> 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)