Differences

This shows you the differences between two versions of the page.

--- tutorials:troubleshooting:memory [2015/11/06 11:48] – smititelu
+++ tutorials:troubleshooting:memory [2021/06/01 18:44] (current) – [Insufficient Memory] giavac
@@ Line 36: / Line 36: @@
   * too small PKG or SHM - insufficient size to accommodate all data needed to be stored in memory
-  * memory leak - some part of code allocates memory at runtine and does not free it
+  * memory leak - some part of code allocates memory at runtime and does not free it
 ===== Monitoring Memory =====
@@ Line 58: / Line 58: @@
 Notice that for SHM only one group of statistics is printed, being one zone of memory, while for PKG you get a list with many groups of statistics, each specific for a Kamailio process (child).
-In order to merge the free memory fragments one should enable memory join. This is enable by default in latest kamailio:
+In order to merge the free memory fragments one should enable memory join. Default is disabled (mem_join=0).
 <code>
 mem_join=1
@@ Line 167: / Line 167: @@
 (4082) NOTICE: fm_status:  count=     1 size=       704 bytes from <core>: cfg/cfg_struct.c: cfg_shmize(217)
 (4082) NOTICE: fm_status:  count=     3 size=        64 bytes from usrloc: udomain.c: build_stat_name(51)
+</code>
+If you dumped the status with qm_malloc, you can extract the logs from syslog and count the unique allocations with next commands:
+<code>
+grep qm_status /var/log/syslog >qm_status.txt
+# or:
+# grep qm_status /var/log/messages >qm_status.txt
+grep alloc qm_status.txt | awk '{ print substr( $0, 16, length($0) ) }' | sort | uniq -c | sort -k1n
 </code>
 ===== Using GDB =====
@@ Line 258: / Line 268: @@
 Here is the article that presents better the situation:
-   * http://blog.logicmonitor.com/2014/10/09/more-linux-memory-free-memory-that-is-not-free-nor-cache/
+   * https://www.logicmonitor.com/blog/more-linux-memory-free-memory-that-is-not-free-nor-cache/
 An relevant excerpt from the blog article: