[nsd-users] Problems loading zone with nsd4

[Klaus Darilion]

Seems like the "working" server has even less resources:

Debian Wheezy 32bit, 8GB Ram, 8GB Swap, not working:
core file size          (blocks, -c) 0
data seg size           (kbytes, -d) unlimited
scheduling priority             (-e) 0
file size               (blocks, -f) unlimited
pending signals                 (-i) 64637
max locked memory       (kbytes, -l) 64
max memory size         (kbytes, -m) unlimited
open files                      (-n) 1024
pipe size            (512 bytes, -p) 8
POSIX message queues     (bytes, -q) 819200
real-time priority              (-r) 0
stack size              (kbytes, -s) 8192
cpu time               (seconds, -t) unlimited
max user processes              (-u) 64637
virtual memory          (kbytes, -v) unlimited
file locks                      (-x) unlimited


Ubuntu 12.04 64bit, 1GB Ram, 2GB Swap, working:
core file size          (blocks, -c) 0
data seg size           (kbytes, -d) unlimited
scheduling priority             (-e) 0
file size               (blocks, -f) unlimited
pending signals                 (-i) 7758
max locked memory       (kbytes, -l) 64
max memory size         (kbytes, -m) unlimited
open files                      (-n) 1024
pipe size            (512 bytes, -p) 8
POSIX message queues     (bytes, -q) 819200
real-time priority              (-r) 0
stack size              (kbytes, -s) 8192
cpu time               (seconds, -t) unlimited
max user processes              (-u) 7758
virtual memory          (kbytes, -v) unlimited
file locks                      (-x) unlimited


regards
Klaus



On 24.06.2014 16:35, W.C.A. Wijngaards wrote:
> Hi Klaus,
> 
> Do you have a ulimit (heap size) set that constrains memory usage
> per-process?
> 
> Best regards, Wouter
> 
> On 06/24/2014 04:28 PM, Klaus Darilion wrote:
>> Strange, on another server (64bit linux) I can load the zone
>> although the server only has 1GB Ram and 2GB swap.
> 
>> regards Klaus
> 
>> On 18.06.2014 12:57, Klaus Darilion wrote:
>>> On 16.06.2014 09:12, W.C.A. Wijngaards wrote:
>>>> Hi Klaus,
>>>>
>>>> On 06/11/2014 10:28 AM, Klaus Darilion wrote:
>>>>> Hi!
>>>>
>>>>> 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[3849]: zonefile at.zone does not exist 10:17:16 
>>>>> nsd[3849]: nsd started (NSD 4.0.3), pid 3847 10:17:26
>>>>> nsd[3847]: xfrd: zone at committed "received update to serial
>>>>> 1402473601 at 2014-06-11T10:17:26 from 83.136.34.4 TSIG
>>>>> verified with key rcode0-distribution" 10:17:26 nsd[4059]:
>>>>> rehash of zone at. with parameters 1 0 5 b81fd4d081abe7a4
>>>>> 10:17:59 nsd[4059]: mremap(/var/lib/nsd/nsd.db, size
>>>>> 1743910912) error Cannot allocate memory 10:17:59 nsd[4059]:
>>>>> could not add RR to nsd.db, disk-space? 10:17:59 nsd[4059]:
>>>>> bad ixfr packet part 2007 in diff file for at. 10:17:59
>>>>> nsd[3849]: handle_reload_cmd: reload closed cmd channel 
>>>>> 10:17:59 nsd[3849]: Reload process 4059 failed with status
>>>>> 256, continuing with old database 10:17:59 nsd[3847]: xfrd:
>>>>> zone at: soa serial 1402473601 update failed, restarting
>>>>> transfer (notified zone)
>>>>
>>>>
>>>>> 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 error.
>>>>
>>>>> 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.
>>>
>>> May the problem be related that my test server uses a 32bit
>>> kernel?
>>>
>>> regards Klaus _______________________________________________ 
>>> nsd-users mailing list nsd-users at NLnetLabs.nl 
>>> http://open.nlnetlabs.nl/mailman/listinfo/nsd-users
>>>
> 
>