dnsperf and BIND memory consumption
JINMEI Tatuya / 神明達哉
Jinmei_Tatuya at isc.org
Thu Aug 7 18:18:37 UTC 2008
At Thu, 7 Aug 2008 10:33:25 -0400,
Vinny Abello <vinny at tellurian.com> wrote:
> > =======================================================================
> > - create a symbolic link from "/etc/malloc.conf" to "X":
> > # ln -s X /etc/malloc.conf
>
> What exactly is this trying to accomplish here? JFYI, I don't have a file /etc/malloc.conf on my server. Did you mean /etc/make.conf? Where is X being referenced?
/etc/malloc.conf normally doesn't exist. You should create a new
symbolic link. For other details, see malloc(3).
> > - start named with a moderate limitation of virtual memory size, e.g.
> > # /usr/bin/limits -v 384m $path_to_named/named <command line options>
> >
> > Then the named process will eventually abort itself with a core dump
> > due to malloc failure. Please show us the stack trace at that point.
> > Hopefully it will reveal the malloc call that keeps consuming memory.
>
> How would I show the trace that you require once this happens?
named will die with a core file. Then perform the following:
# gdb <path_to_named> <path_to_core>
(gdb) thread apply all bt full
---
JINMEI, Tatuya
Internet Systems Consortium, Inc.
More information about the bind-users
mailing list