Nsd-4.1.20 server failed updating zone

NSD
1

Hello,

I have operated slave name server with nsd on Linux(CentOS7.4).
When I upgrade version from 4.1.16 to 4.1.20,
An error what the zone can not be updated occurred.

These are logs and straces of "nsd-control force_transfer example.net",
using same server, same config and same zone data.
Could you have any advice?

Thanks

---[4.1.16 log]---
[2018-05-17 10:07:12.877] nsd[3157]: info: xfrd: zone example.net written received XFR packet from xxx.xxx.xxx.xxx with serial 2018051602 to disk
[2018-05-17 10:07:12.878] nsd[3157]: info: xfrd: zone example.net committed "received update to serial 2018051602 at 2018-05-17T10:07:12 from xxx.xxx.xxx.xxx"
[2018-05-17 10:07:12.896] nsd[3158]: info: rehash of zone example.net. with parameters 1 0 3 3ff46b
[2018-05-17 10:07:12.921] nsd[3158]: info: zone example.net. received update to serial 2018051602 at 2018-05-17T10:07:12 from xxx.xxx.xxx.xxx of 118323 bytes in 0.102588 seconds
[2018-05-17 10:07:12.925] nsd[3157]: info: zone example.net serial 2018051602 is updated to 2018051602.

2

Hi HarikiTsuyoshi,

Can I have the information, so that I can reproduce the problem with
4.1.20? I would like to reproduce it, so that I can debug (get a stack
trace and perhaps more debugging) the reload process. (process 2939 in
your logs). Perhaps the zone file (old & new?) is sufficient to reproduce?

In 4.1.20 there is 'make xfr-inspect' in the source that builds a tool
to inspect the contents of the xfr file from /tmp, and that file could
be interesting (it contains the downloaded zone update, and perhaps it
can be used to reproduce the problem).

Best regards, Wouter