Greetings,

Recently one of my Kamailio's started started answering with a lot of 500 replies to requests because of insufficient private memory. 

The service Kamailio had been running for 6 months now. In order to solve this i increased the private memory settings and restarted the Kamailio.

Before that, when searching a bit about the issue i found an old thread where Daniel suggested using " kamcmd corex.pkg_summary idx 1" to check for pkg leaks in the sip worker process. I ran this before doing the restart in order to identify leaks and found the summary in the logs.

However, i am having a hard time interpreting this summary and being able to know if i have or not a mem leak. What should i be looking for?

This is the beggining of the summary : 

qm_status: (0x7ff3c8cef010):

 qm_status: heap size= 8388608

 qm_status: used= 928576, used+overhead=1464080, free=6924528

 qm_status: max used (+overhead)= 1488472

 qm_status: dumping all alloc'ed. fragments:

 qm_status:      0. N  address=0x7ff3c8d286d8 frag=0x7ff3c8d286a0 size=1024 used=1

 qm_status:           alloc'd from core: core/str_hash.h: str_hash_alloc(59)

 qm_status:          start check=f0f0f0f0, end check= c0c0c0c0, abcdefed

 qm_status:      1. N  address=0x7ff3c8d28b40 frag=0x7ff3c8d28b08 size=256 used=1

 qm_status:           alloc'd from core: core/str_hash.h: str_hash_alloc(59)

 qm_status:          start check=f0f0f0f0, end check= c0c0c0c0, abcdefed

 qm_status:      2. N  address=0x7ff3c8d28ca8 frag=0x7ff3c8d28c70 size=184 used=1

 qm_status:           alloc'd from core: core/counters.c: cnt_hash_add(332)

 qm_status:          start check=f0f0f0f0, end check= c0c0c0c0, abcdefed

 

 

 Any help? 

 

 Best Regards,

 

 Duarte Rocha