Hello,
Please try to catch this leak at run-time. As soon as a specific process
starts complaining about no more pkg memory, get it's PID from syslog and do
kill -SIGUSR1 PID
and you should get the PKG memory dump just for that specific process.
Regards,
Vlad Paiu
OpenSIPS Developer
http://www.opensips-solutions.com
On 03/20/2012 10:46 AM, Steven Lam, KeenSystems B.V. wrote:
Hi,
Yesterday OpenSIPS crashed after logging things like this:
WARNING:core:fm_malloc: Not enough free memory, will atempt defragmenation
ERROR:core:build_res_buf_from_sip_req: out of pkg memory ; needs 394
ERROR:sl:sl_send_reply_helper: response building failed
Looking at the graphs for the memory usage I can see the memory consumption is
only going up, never going down. Sure it went down after OpenSIPS crashing ;-)
I followed this doc to create a memory manager log of OpenSIPS stopping after
some calls:
http://www.opensips.org/Resources/DocsTsMem
I now have a log but no idea where to look for, is there someone who wants to
take a look for me?
The log can be found here: http://keenserver.nl/files/dump.log
Hope someone can help.
Thanks,
Steven
_______________________________________________
Devel mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
_______________________________________________
Devel mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
