Hi Ondřej,
unfortunately, it happened that we introduced a bug in journal loop
detection in 3.2.7. We discovered the bug ourselves and i has been fixed
https://gitlab.nic.cz/knot/knot-dns/-/merge_requests/1540 , but it will
be part of the upcoming 3.2.8 release.
I'd like to ask you to roll back to 3.2.6 in the meantime.
Anyway, could you please share the output of `kjournalprint -d
83.204.91.in-addr.arpa.` , so that we can make sure that is is the same
bug as we think it is?
Thank you!
Libor
Dne 23. 06. 23 v 12:34 Ondřej Caletka napsal(a):
Hey,
after an (unattended) upgrade to 3.2,7, one of my zones (the one that
does rapid KSK rollovers) failed to load. Trying ro reload emits these
errors in the log:
info: [83.204.91.in-addr.arpa.] zone file parsed, serial 1622013488
error: [83.204.91.in-addr.arpa.] failed to apply journal changes,
serial 1622013488 -> 1686209286 (loop detected)
2023-06-23T12:11:57+0200 error: [83.204.91.in-addr.arpa.] failed to
apply journal changes, serial 1622013488 -> 1686209286 (loop detected)
warning: [83.204.91.in-addr.arpa.] failed to load journal (loop detected)
2023-06-23T12:11:57+0200 warning: [83.204.91.in-addr.arpa.] failed to
load journal (loop detected)
info: [83.204.91.in-addr.arpa.] zone not found
error: [83.204.91.in-addr.arpa.] zone event 'load' failed (not exists)
2023-06-23T12:11:57+0200 error: [83.204.91.in-addr.arpa.] zone event
'load' failed (not exists)
Calling `kjournalprint 83.204.91.in-addr.arpa` yields 600 lines of
journal full of both additions and deletions, nothing seems
particularly wrong. Is there anything I should try before purging the
journal and starting from scratch?
There are other zones on the same server with similar config that just
work normally, so I guess this is somehow related to the size of the
journal for this zone, which rotates DNSSEC keys very often.
--
Cheers,
Ondřej Caletka
--
--
