[asterisk-bugs] [JIRA] (ASTERISK-30149) core: minmemfree watermark issue

Asterisk Team (JIRA) noreply at issues.asterisk.org
Thu Jul 21 09:35:09 CDT 2022


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

Asterisk Team commented on ASTERISK-30149:
------------------------------------------

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur.

Please note that by submitting data, code, or documentation to Sangoma through JIRA, you accept the Terms of Use present at [https://www.asterisk.org/terms-of-use/|https://www.asterisk.org/terms-of-use/].

> core: minmemfree watermark issue
> --------------------------------
>
>                 Key: ASTERISK-30149
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-30149
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: PBX/General
>    Affects Versions: 18.5.0
>         Environment: AWS Linux 4.14.198-152.320.amzn2.x86_64
>            Reporter: Cyril Ramière
>            Severity: Major
>
> Hello,
> I have an issue with asterisk stopping accepting new calls.
> When the issue occurs, the console shows those messages:
> ```
> [Jul 21 06:55:49] WARNING[762] pbx.c: Available system memory (~169MB) is below the configured low watermark (200MB)
> [Jul 21 06:55:49] WARNING[762] chan_pjsip.c: Failed to start PBX (call limit reached) 
> ```
> I have set inside asterisk.conf the "minmemfree" value to 200M so this seems right.
> But after checking on the host, I have plenty of ram available:
> ```
> free
>               total        used        free      shared  buff/cache   available
> Mem:        2001944      686428      122692        1560     1192824     1154636
> ```
> Let's do a 'core show sysinfo' :
> ```
>  core show sysinfo 
> System Statistics
> -----------------
>   System Uptime:             197 hours
>   Total RAM:                 2001944 KiB
>   Free RAM:                  121992 KiB
>   Buffer RAM:                107268 KiB
>   Total Swap Space:          0 KiB
>   Free Swap Space:           0 KiB
>   Number of Processes:       390 
> ```
> So it seems that asterisk is only relying on the "free" memory information, and it stops accepting new calls although the host have plenty of available ram.
> This issue seems similar to https://issues.asterisk.org/jira/browse/ASTERISK-28695 which has been fixed on 18.X branch if I'm correct.
> Regards



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



More information about the asterisk-bugs mailing list