1 Aug
2019
1 Aug
'19
1:24 p.m.
Hello,
if it is pkg, then you have to see which process is increasing the use
of memory, because it is private memory, specific for each process. The
sum is an indicator, but the debugging has to be done for a specific
process/pid.
Once you indentify a process that is leaking pkg, execute the rpc command:
-
https://www.kamailio.org/docs/modules/devel/modules/corex.html#corex.rpc.pk…
When that process is doing some runtime work (e.g., handling of a sip
message), the syslog will get a summary with used pkg chunks. Send those
log messages here for analysis. You have to set memlog core parameter to
a value smaller than debug.
Cheers,
Daniel
On 01.08.19 03:43, Andrew White wrote:
Hi all,
I had a Kamailio crash the other day, and some debugging showed I ran
out of PKG memory.
Since then I’ve run a simple bash script to compile the amount of
memory used by all child processes, effective /usr/local/sbin/kamcmd
pkg.stats | grep real_used summed together. I’ve graphed out the data,
and there’s a clear growth of PKG memory going on, mostly increasing
during our busier daytime hours.
https://i.imgur.com/UTzx2k1.png
Based on this, I suspect either a module loaded or something within my
app_ruby conf is leaking memory.
I’ve been reading
through https://www.kamailio.org/wiki/tutorials/troubleshooting/memory,
but I’m a bit nervous, as I’m not really a C/deep memory type of guy.
I can see a GDB script I can attach to Kamailio, but is that going to
use significant resources to run or impact the running process? Is
there a newer/better/alternative way to do this, and to help me break
this down?
Thanks!
Andrew
_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users(a)lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
--
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda
