Thanks Fredrik,And yes Tamás, this is indeed quite similar to your issue. I was hoping that the notifies directly to the transfer daemon in 4.11 would resolve this, but there may be another cause.
The issue is my first priority with NSD now. I'm planning to add some additional monitoring and watchdogs for the several stages of the reload process, that can also trigger log events when they take longer (logging which stage of the reload process took how much time so far). I will merge the two issues, because they are indeed quite similar, and report on this work there.
Regards, -- Willem Op 28-12-2024 om 13:09 schreef Csillag Tamás via nsd-users:
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 bugAfter 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/417It seems somewhat similar to the issue I have experienced: https://github.com/NLnetLabs/nsd/issues/338 in my case it recovered on its own. Regards, Tamás _______________________________________________ nsd-users mailing list nsd-users@lists.nlnetlabs.nl https://lists.nlnetlabs.nl/mailman/listinfo/nsd-users
OpenPGP_0xE5F8F8212F77A498_and_old_rev.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
_______________________________________________ nsd-users mailing list nsd-users@lists.nlnetlabs.nl https://lists.nlnetlabs.nl/mailman/listinfo/nsd-users
