Hi Kees. A few questions: - What version of BIND are you running? - How large (number of RRs) are your zones? - What is the peak rate of dynamic updates? - Do you have "max-journal-size" configured to anything? - Are you perhaps getting short on disc storage in the place where BIND keeps its files? - How much RAM does the server have and how much of that is BIND using?
I would recommend reading the ARM section on the journal. The log message itself comes from "zone.c" Cheers, Greg On Mon, 8 Jul 2024 at 12:18, Kees Bakker via bind-users < bind-users@lists.isc.org> wrote: > Hi, > > At the moment I have three FreeIPA systems (replicas), recently > installed with CentOS 9-Stream. > All three of these show this message at irregular intervals. > > Jul 03 07:50:44 iparep5.example.com named[541]: zone example.com/IN: > zone_journal_compact: could not get zone size: not found > Jul 03 07:50:51 iparep5.example.com named[541]: zone > 16.16.172.in-addr.arpa/IN: zone_journal_compact: could not get zone > size: not found > Jul 03 07:51:03 iparep5.example.com named[541]: zone > 17.16.172.in-addr.arpa/IN: zone_journal_compact: could not get zone > size: not found > Jul 03 07:51:34 iparep5.example.com named[541]: zone > 29.16.172.in-addr.arpa/IN: zone_journal_compact: could not get zone > size: not found > Jul 03 07:52:12 iparep5.example.com named[541]: zone > 30.16.172.in-addr.arpa/IN: zone_journal_compact: could not get zone > size: not found > Jul 03 08:03:51 iparep5.example.com named[541]: zone example.com/IN: > zone_journal_compact: could not get zone size: not found > Jul 03 08:04:52 iparep5.example.com named[541]: zone > 29.16.172.in-addr.arpa/IN: zone_journal_compact: could not get zone > size: not found > Jul 03 08:06:30 iparep5.example.com named[541]: zone > 30.16.172.in-addr.arpa/IN: zone_journal_compact: could not get zone > size: not found > Jul 03 08:18:42 iparep5.example.com named[541]: zone example.com/IN: > zone_journal_compact: could not get zone size: not found > Jul 03 08:20:19 iparep5.example.com named[541]: zone > 29.16.172.in-addr.arpa/IN: zone_journal_compact: could not get zone > size: not found > Jul 03 08:26:23 iparep5.example.com named[541]: zone > 30.16.172.in-addr.arpa/IN: zone_journal_compact: could not get zone > size: not found > Jul 03 08:34:12 iparep5.example.com named[541]: zone example.com/IN: > zone_journal_compact: could not get zone size: not found > Jul 03 08:34:50 iparep5.example.com named[541]: zone > 29.16.172.in-addr.arpa/IN: zone_journal_compact: could not get zone > size: not found > > I have been running FreeIPA (including the bind nameserver) for several > years now and I have never seen this message before. > I still have one FreeIPA system running CentOS 8-Stream. > > Does anyone have a clue what it can be? Or how to find out? There are > close to zero hits when I searched for this on the internet. > How to debug this? (How to debug this in a production environment, ha ha) > -- > Kees > -- > Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe > from this list > > ISC funds the development of this software with paid support > subscriptions. Contact us at https://www.isc.org/contact/ for more > information. > > > bind-users mailing list > bind-users@lists.isc.org > https://lists.isc.org/mailman/listinfo/bind-users >
-- Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
