Discussion:
[SR-Users] SIGUSR1 for memory status not working as documented - only one process reports back
Alex Villací­s Lasso
2014-07-30 20:15:18 UTC
Permalink
I am trying to track down a memory leak that was triggered by a patch I wrote for my local copy of kamailio 4.1.4 . For this, I am following the documentation at http://www.kamailio.org/dokuwiki/doku.php/troubleshooting:memory . This page claims that once
memlog is set in the configuration file, a kamailio process will dump a report of the allocation map when shutting down, or when receiving a SIGUSR1. I have configured my kamailio.cfg with memlog=1 and no other change, and I see the memory report on
shutdown for all processes. However, when I send a SIGUSR1 to a kamailio process, the process does absolutely nothing, with the exception of the first kamailio process (the one reported as Type=attendant by "kamctl ps"). All of the other processes just
ignore SIGUSR1. What is going on? It is inconvenient to force a shutdown of all the kamailio processes just to get the memory report.
Daniel-Constantin Mierla
2014-08-01 06:16:50 UTC
Permalink
Hello,

it the same page is a mention for 3.x versions which is the new way
respectively:

kamcmd cfg.set_now_int core mem_dump_pkg <pid>

The signal method was considered unsafe and replaced by the rpc comamnd
by Andrei Pelinescu (iirc).

Cheers,
Daniel
Post by Alex Villací­s Lasso
I am trying to track down a memory leak that was triggered by a patch
I wrote for my local copy of kamailio 4.1.4 . For this, I am following
the documentation at
http://www.kamailio.org/dokuwiki/doku.php/troubleshooting:memory .
This page claims that once memlog is set in the configuration file, a
kamailio process will dump a report of the allocation map when
shutting down, or when receiving a SIGUSR1. I have configured my
kamailio.cfg with memlog=1 and no other change, and I see the memory
report on shutdown for all processes. However, when I send a SIGUSR1
to a kamailio process, the process does absolutely nothing, with the
exception of the first kamailio process (the one reported as
Type=attendant by "kamctl ps"). All of the other processes just ignore
SIGUSR1. What is going on? It is inconvenient to force a shutdown of
all the kamailio processes just to get the memory report.
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
--
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Loading...