[nsd-users] NSD 4 / OS limitation problem?

Fredrik Pettai pettai at nordu.net
Thu Jul 2 06:10:45 UTC 2015


I recently tried to switch from nsd-3.2.19 -> nsd-4.1.3 on our largest DNS slave

$ grep -c zone: nsd.conf

But I stumbled upon a problem with NSD4. The log complains about memory allocation:

[2015-07-01 19:40:26.285] nsd[29189]: info: zone itsnat.se read with success
[2015-07-01 19:40:26.302] nsd[29189]: info: rehash of zone itsnat.se. with parameters 1 0 5 c393596e0fd9f7de
[2015-07-01 19:40:26.789] nsd[29189]: error: mmap(/var/nsd/nsd.db, size 1376910080) error Cannot allocate memory
[2015-07-01 19:40:26.846] nsd[29395]: error: did not get start signal from main

While I know that the database is much bigger in NSD4, this shouldn’t be a problem for a modern OS.

$ ls -l /var/nsd/nsd*.db

-rw-r--r--  1 nsd   nsd   162257814 Jul  1 19:37 /var/nsd/nsd3.db  <—  old NSD3 db
-rw-------  1 nsd   nsd  1376910080 Jul  1 19:41 /var/nsd/nsd4.db  <—  NSD4 db

There is still plenty of room on /var too…
It doesn’t look like an obvious limitation in the OS either?

$ ulimit -a
socket buffer size       (bytes, -b) unlimited
core file size          (blocks, -c) unlimited
data seg size           (kbytes, -d) 262144
file size               (blocks, -f) unlimited
max locked memory       (kbytes, -l) 1023162
max memory size         (kbytes, -m) 3069488
open files                      (-n) 128
pipe size            (512 bytes, -p) 1
stack size              (kbytes, -s) 2048
cpu time               (seconds, -t) unlimited
max user processes              (-u) 160
virtual memory          (kbytes, -v) unlimited


Any ideas?


More information about the nsd-users mailing list