Hi, > On 28 Dec 2024, at 13:09, Csillag Tamás <cstamas+...@cstamas.hu> wrote: > > hi, > > On 2024-12-27 22:32, Fredrik Pettai via nsd-users wrote: >> Hello, >> It seems our NSD secondary has triggered some sort of intermittent bug >> After several weeks/months of running nsd stops forking with the new zone >> data. >> A manual nsd-control transfer or even nsd-control force_transfer won’t work, >> only restart of nsd solves the problem. >> The only “hint” I’ve found is that the nsd xfrd messages stops appearing in >> the logs (while the notify messages keeps coming). >> I’ve put the details in this issue >> https://github.com/NLnetLabs/nsd/issues/417 > > It seems somewhat similar to the issue I have experienced: > https://github.com/NLnetLabs/nsd/issues/338
The symptoms are similar, but we don’t have verification configured on this host, so I don’t think it’s the same issue. > in my case it recovered on its own. Only a restart makes it recover in our case. Re, /P > > Regards, > Tamás
signature.asc
Description: Message signed with OpenPGP
_______________________________________________ nsd-users mailing list nsd-users@lists.nlnetlabs.nl https://lists.nlnetlabs.nl/mailman/listinfo/nsd-users
