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

[Richard Mudgett (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-30149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Richard Mudgett updated ASTERISK-30149:
---------------------------------------

    Description: 
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 ASTERISK-28695 which has been fixed on 18.X branch if I'm correct.

Regards



  was:
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




> 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
>            Assignee: Unassigned
>
> 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 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)