Also, with some kernels, it is disabled for non-root users, so might be
better to run as root when trying to reproduce.
Private memory stats are available starting with 3.2, via 'sercmd
pkg.stats'.
For older versions, you would have to walk the private memory with gdb:
http://www.kamailio.org/dokuwiki/doku.php/troubleshooting:memory#walking_th…
and you can see where are the chunks allocated from.
Cheers,
Daniel
On 2/23/12 10:40 AM, Klaus Darilion wrote:
Usually (on Debian) the core file will be activated in
/etc/default/kamailio and the location of the core file is specified
in /etc/init.d/kamailio.
regards
klaus
On 22.02.2012 23:45, Fabian Borot wrote:
How can I make sure that a core file is created after a situation
like this? Where will it be created?
How can I check the status of the private memory? I use the "kamctl
fifo get_statistics all" but I don't know which one relates to
"private memory":
Example:
shmem:total_size = 2147483648
shmem:used_size = 16860928
shmem:real_used_size = 17033968
shmem:max_used_size = 19174528
shmem:free_size = 2130449680
shmem:fragments = 1850
I know that with so little information is hard to diagnose, but if
anybody has an idea as to what else I can do I greatly appreciate it.
Thank you in advance
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
--
Daniel-Constantin Mierla --
http://www.asipto.com
http://linkedin.com/in/miconda --
http://twitter.com/miconda