zone_journal_compact: could not get zone size: not found

[Kees Bakker]

On 08-07-2024 13:42, Greg Choules wrote:
> Hi Kees. 

Hi Greg, thanks for the quick reply.

> A few questions:
> - What version of BIND are you running?
9.16.23 (in centos that is 32:9.16.23-15.el9)

> - How large (number of RRs) are your zones?
My main zone (renamed to example.com) is about 800 RRs (if I interpret 
RR correctly).
The in-addr.arpa zones have 150-200 entrie.
What you need to know is that this is a FreeIPA environment. The zones 
are stored in LDAP.
The DHCP sends its updates to one of the bind servers. These updates are 
then replicated in LDAP.

> - What is the peak rate of dynamic updates?
Don't know. Is there is simple command to show this.

> - Do you have "max-journal-size" configured to anything?
That should be the default. I haven't specifically changed it.

> - Are you perhaps getting short on disc storage in the place where 
> BIND keeps its files?
No. Many GBs free disk space. The jnl files that I see are just a few 
kbs in size.

> - How much RAM does the server have and how much of that is BIND using?
One has 8GB. Two others have 128GB (because they run in an LXC/Incus 
container).

>
> I would recommend reading the ARM section on the journal. The log 
> message itself comes from "zone.c"
OK. I have a global understanding what the journal is doing. I went 
through the zone.c code before posting this here.
But so far I could not figure out how this message can be triggered. And 
also, the systems didn't show this message before upgrading CentOS.
One system is still at CentOS 8-Stream. The message isn't shown on that one.

>
> Cheers, Greg
-- Kees

>
> On Mon, 8 Jul 2024 at 12:18, Kees Bakker via bind-users 
> <bind-users at 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 <http://iparep5.example.com>
>     named[541]: zone example.com/IN <http://example.com/IN>:
>     zone_journal_compact: could not get zone size: not found
>     Jul 03 07:50:51 iparep5.example.com <http://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 <http://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 <http://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 <http://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 <http://iparep5.example.com>
>     named[541]: zone example.com/IN <http://example.com/IN>:
>     zone_journal_compact: could not get zone size: not found
>     Jul 03 08:04:52 iparep5.example.com <http://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 <http://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 <http://iparep5.example.com>
>     named[541]: zone example.com/IN <http://example.com/IN>:
>     zone_journal_compact: could not get zone size: not found
>     Jul 03 08:20:19 iparep5.example.com <http://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 <http://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 <http://iparep5.example.com>
>     named[541]: zone example.com/IN <http://example.com/IN>:
>     zone_journal_compact: could not get zone size: not found
>     Jul 03 08:34:50 iparep5.example.com <http://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 at lists.isc.org
>     https://lists.isc.org/mailman/listinfo/bind-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20240708/3c42edc8/attachment.htm>