[asterisk-bugs] [JIRA] (ASTERISK-28431) Asterisk memory increases and CentOS OEM killer kills Asterisk process

[Asterisk Team (JIRA)]

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

Asterisk Team commented on ASTERISK-28431:
------------------------------------------

Suspended due to lack of activity. This issue will be automatically re-opened if the reporter posts a comment. If you are not the reporter and would like this re-opened please create a new issue instead. If the new issue is related to this one a link will be created during the triage process. Further information on issue tracker usage can be found in the Asterisk Issue Guidlines [1].

[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines

> Asterisk memory increases and CentOS OEM killer kills Asterisk process
> ----------------------------------------------------------------------
>
>                 Key: ASTERISK-28431
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28431
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: General
>    Affects Versions: 13.25.0
>         Environment: CentOS 7.6.1810 core
> kernel 3.10.0-957.el7.x86_64
> RAID1 configured for OS and RAID5 configured for data
>            Reporter: Deepak Lohani
>            Assignee: Deepak Lohani
>              Labels: pjsip
>         Attachments: End_Date_31May.zip, Hardware info.log, memory_23_May_2019.txt, memory_30_May_2019.txt, Top_30-05-2019-1700.jpg
>
>
> We are continuously facing an issue of High RAM consumption over Asterisk 13.25.0 with Centos 7.6. Here Asterisk will consume all available RAM (32GB) of our server over a 15 days period,
> and consume whole swap portion too.In such scenario OOM-killer invoked by Centos kills the process which has consumed highest memory i.e Asterisk.
> After that server will resume total RAM and runs smoothly.



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