If lmdb is upgraded to 1.0 (from the ports) all knot3 operations get following error : error: failed to load configuration file '/usr/local/etc/knot/knot.conf' (MDB_BAD_TXN: Transaction must abort, has a child, or is invalid) I had to revert to a snapshot of my jail with lmdb 0.9 to restore the service
From the symptoms, it might be broken in a similar way to mail/postfix, see https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=296531 and discuss thjis with the knot3 upstream please.
The Arch Linux guys figured that the bug is the same as mail/postfix's https://gitlab.archlinux.org/archlinux/packaging/packages/lmdb/-/work_items/5#note_508323
I have reported the bug in knot dns mailing list: https://lists.nic.cz/hyperkitty/list/knot-dns-users@lists.nic.cz/message/LXG4357GIZNETCN6WRXPIXFUHSZP7S2R/
(In reply to Michael Grimm from comment #3) And fixed: https://lists.nic.cz/hyperkitty/list/knot-dns-users@lists.nic.cz/message/WG6LHGNWDNB4HEE736D5YYKBHHU6HJ62/