Hello and thanks for all the valuable feedback. Debugging messages might not help you in this case, because they tend to generate a lot of data, especially when Knot is loading 16G worth of zones, so it could take a lot of time until the issue occurs. If you could attach a debugger to knotd process when it gets stuck and let us know what is doing at the moment. Perhaps using Poor Man's Profiler might be the best option. Thanks again for your feedback. Best regards, Jan.

Anand Buddhdev <anandb@ripe.net> wrote:
I thought I'd enable debugging code to try and figure out why the server
goes into a loop. So I added the following to configure:

--enable-debug=server,zones,xfr,packet,dname,rr,ns,hash,compiler,stash

However, Knot doesn't compile now. The compile fails with:

...
...
libknot/packet/packet.c: In function 'knot_packet_parse_question':
libknot/packet/packet.c:311: error: 'bp' undeclared (first use in this
function)
libknot/packet/packet.c:311: error: (Each undeclared identifier is
reported only once
libknot/packet/packet.c:311: error: for each function it appears in.)

If I remove the packet debug option, I can compile Knot again.

Regards,

Anand

knot-dns-users mailing list
knot-dns-users@lists.nic.cz
https://lists.nic.cz/cgi-bin/mailman/listinfo/knot-dns-users

--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.