On Tue, Jan 07, 2020 at 09:11:56AM +0300, Anand Buddhdev via nsd-users <[email protected]> wrote a message of 36 lines which said:
> This suggests that an incoming XFR is triggering a bug. Have you saved > the contents of the nsd-xfr-1974 directory? If not, perhaps you can save > it the next time it happens. This may help the developers in figuring > out what causes the crash. Apparently, it was a lack of memory: [8374219.385014] Out of memory: Kill process 10677 (nsd) score 66 or sacrifice child [8374219.385758] Killed process 10678 (nsd) total-vm:37552kB, anon-rss:676kB, file-rss:0kB, shmem-rss:27344kB [8374219.386779] oom_reaper: reaped process 10678 (nsd), now anon-rss:0kB, file-rss:0kB, shmem-rss:27344kB > Finally, the database mode is no longer recommended. Could you try > running your instance of NSD with: > > database: "" Currently under test and no problem yet (anyway, I'll add RAM). _______________________________________________ nsd-users mailing list [email protected] https://lists.nlnetlabs.nl/mailman/listinfo/nsd-users
