[nsd-users] Problems loading zone with nsd4
wouter at nlnetlabs.nl
Mon Jun 16 07:12:30 UTC 2014
-----BEGIN PGP SIGNED MESSAGE-----
On 06/11/2014 10:28 AM, Klaus Darilion wrote:
> I just tried to switch from nsd3 to nsd4 but nsd4 fails to load
> the zone. The zone is approx 170MB (Bind text format).
> NSD4 is configured is slave. The zone is transferred but failed
> during loading with memory allocation error:
> 10:17:16 nsd: zonefile at.zone does not exist 10:17:16
> nsd: nsd started (NSD 4.0.3), pid 3847 10:17:26 nsd:
> xfrd: zone at committed "received update to serial 1402473601 at
> 2014-06-11T10:17:26 from 18.104.22.168 TSIG verified with key
> rcode0-distribution" 10:17:26 nsd: rehash of zone at. with
> parameters 1 0 5 b81fd4d081abe7a4 10:17:59 nsd:
> mremap(/var/lib/nsd/nsd.db, size 1743910912) error Cannot allocate
> memory 10:17:59 nsd: could not add RR to nsd.db, disk-space?
> 10:17:59 nsd: bad ixfr packet part 2007 in diff file for at.
> 10:17:59 nsd: handle_reload_cmd: reload closed cmd channel
> 10:17:59 nsd: Reload process 4059 failed with status 256,
> continuing with old database 10:17:59 nsd: xfrd: zone at: soa
> serial 1402473601 update failed, restarting transfer (notified
> The server has 8GB RAM, 512KB swap and 9GB of free disk space, and
> there is plenty of disk and ram left when nsd logs the memory
> Thus, I suspect something else is going wrong. Any hints?
I think it is the memory somehow, perhaps the memory overcommit kernel
settings in Linux are disallowing the allocation, even though there
seems to be enough memory (at current usage). The most recent code
from the repository (not yet released, but passed regression tests)
has the option to use database: "" in nsd.conf and then the nsd.db is
not made, not mmapped, and thus a lot of disk and memory space is
freed. That would likely make your system work.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
-----END PGP SIGNATURE-----
More information about the nsd-users