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

[Richard Mudgett (JIRA)]

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

Richard Mudgett edited comment on ASTERISK-28431 at 5/30/19 11:03 AM:
----------------------------------------------------------------------

I've looked through the logs you've provided, and noticed that {{chan_sip.c}}, {{res_rtp_asterisk.c}}, and {{smoother.c}} seem to be the main sources of memory consumption. Here's some things that can help track the problem down:
# Try PJSIP. If this is a chan_sip issue, PJSIP is the correct solution for it, as chan_sip is now under extended support [1].
# If possible, try using a different system or virtual environment and seeing if the problem persists. We want to eliminate the possibility that it's not Asterisk causing the problem.
# Provide output of {{memory show allocations}} the same way you did with {{memory show summary}}, with a large enough amount of time between them so that we can compare allocations.
# If you're using conferencing, are you using dialplan to set them up dynamically? For example:
{code}
...
same => n,SET(CONFBRIDGE(menu,0)=hello-world)
...
{code}
There's a known memory leak with this [2].
# Can you provide any other information that may be impacting the system? Other programs running in conjunction with Asterisk, any custom patches you might have applied to your build, or anything along those lines that we should be aware of?

[1]: https://wiki.asterisk.org/wiki/display/AST/Asterisk+Module+Support+States
[2]: ASTERISK-28422


was (Author: bford):
I've looked through the logs you've provided, and noticed that {{chan_sip.c}}, {{res_rtp_asterisk.c}}, and {{smoother.c}} seem to be the main sources of memory consumption. Here's some things that can help track the problem down:
# Try PJSIP. If this is a chan_sip issue, PJSIP is the correct solution for it, as chan_sip is now under extended support [1].
# If possible, try using a different system or virtual environment and seeing if the problem persists. We want to eliminate the possibility that it's not Asterisk causing the problem.
# Provide output of {{memory show allocations}} the same way you did with {{memory show summary}}, with a large enough amount of time between them so that we can compare allocations.
# If you're using conferencing, are you using dialplan to set them up dynamically? For example:
{code}
...
same => n,SET(CONFBRIDGE(menu,0)=hello-world)
...
{code}
There's a known memory leak with this [2].
# Can you provide any other information that may be impacting the system? Other programs running in conjunction with Asterisk, any custom patches you might have applied to your build, or anything along those lines that we should be aware of?

[1]: https://wiki.asterisk.org/wiki/display/AST/Asterisk+Module+Support+States
[2]: https://issues.asterisk.org/jira/browse/ASTERISK-28422

> 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
>         Attachments: 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)