Re: managed-keys-error since BIND-9.16.15

I suspect we missed a auto detection case. Can you open ticket on https://gitlab.isc.org. We will need to see the journal and whatever else was logged at the same time. That said "named-journalprint -u /var/named/slave/example.com.hosts.jnl" should fix the issue. Only run this when named is s

Re: managed-keys-error since BIND-9.16.15

I see the same error also on a couple of slave zones on a updated authoritative server, not only on the "managed-keys.bind"-file. So this is also not critical and can be ignored? 03-May-2021 00:20:28.532 general: error: /var/named/slave/example.com.hosts.jnw: journal file corrupt: expected se

Re: managed-keys-error since BIND-9.16.15

Named should automatically correct this error. The journal version was not updated when the transaction header was updated. This has been corrected and named detects the unexpected transaction header and writes out a corrected journal. -- Mark Andrews > On 30 Apr 2021, at 21:16, Tom wrote:

managed-keys-error since BIND-9.16.15

Hi After upgrading to BIND-9.16.15, I have the following error in named.log: 30-Apr-2021 12:41:29.194 general: error: managed-keys.bind.jnw: journal file corrupt: expected serial 1823, got 1824 30-Apr-2021 12:41:29.194 general: error: managed-keys-zone: dns_journal_compact failed: unexpected e