[SR-Users] Problem with debug memory: kill -SIGUSR1 doesn't work fine

[Henning Westerholt]

On Friday 24 September 2010, César Pinto Magán wrote:
> We had been experiencing memory leaks issues with our Kamailio deployment.
> Some of the process started to use all their assigned memory and arises
> allocation memory errors. Using the “kill –SIGUSR1” as explained in the
> Kamailio wiki and found the problem:
> [..]
> We saw there was several core memory leaks resolved in the 3.0.3 version
> (we had the 3.0.2), so we decided to upgrade to that version. Now I was
> trying to check the memory status of the process (in order to see if the
> problem is arising again) with “kill –SIGUSR1” but now only show the
> memory status of the shm and the memory of the attendant process (the one
> who launch the other ones). I had tried to send the signal to each of the
> son process but I see nothing in the log. Is this a new bug or is that
> there is other new way to see the memory status of the processes?

Hi César,

normally it should work here as in the old version. Do you compiled the new 
version also with memory debug enabled and enabled also the appropriate 
logging in the configuration?

build:
make cfg mode=debug MEMDBG=1
make all

cfg:
memlog=1
memdbg=1

Cheers,

Henning