You need to ask your supplier. BIND 9.16 is end-of-life and for all practical
purposes,
everything that ISC provides doesn't have the problem. Unfortunately, RedHat
decided
to provide FreeIP dyndb plugin under incompatible license with BIND 9, so we
can't
really do anything about that.
Ondrej
--
Ondřej Surý (He/Him)
ond...@isc.org
My working hours and your working hours may be different. Please do not feel
obligated to reply outside your normal working hours.
> On 9. 7. 2024, at 9:34, Kees Bakker <ke...@ghs.com> wrote:
>
> Indeed the LDAP plugin does not provide the getsize method. Until now it
> never has.
> I'll notify the maintainer.
>
> I have a question that you may be able to answer. Is the getsize method a
> required method or an optional one?
> If the latter then the zone_journal_compact function needs to become a bit
> more friendly with its logging, because journalctl colors the message in red
> (meaning: something is wrong here).
> -- Kees
>
> On 08-07-2024 17:17, Ondřej Surý wrote:
>> You need to ask FreeIPA people and your vendor (but my guess is that the
>> dyndb plugin provided by RH doesn’t provide this method).
>> --
>> Ondřej Surý — ISC (He/Him)
>>
>> My working hours and your working hours may be different. Please do not feel
>> obligated to reply outside your normal working hours.
>>
>>> On 8. 7. 2024, at 16:48, Kees Bakker via bind-users
>>> <bind-users@lists.isc.org> wrote:
>>>
>>> Running gdb showed that the "not found" comes from this piece of code
>>>
>>> isc_result_t
>>> dns_db_getsize(dns_db_t *db, dns_dbversion_t *version, uint64_t *records,
>>> uint64_t *bytes) {
>>> REQUIRE(DNS_DB_VALID(db));
>>> REQUIRE(dns_db_iszone(db));
>>> if (db->methods->getsize != NULL) {
>>> return ((db->methods->getsize)(db, version, records, bytes));
>>> }
>>> return (ISC_R_NOTFOUND);
>>> } That db->methods-getsize is NULL. Here is a piece of the gdb session
>>> 08-Jul-2024 16:39:29.587 dump_done: zone 29.16.172.in-addr.arpa/IN: enter
>>> Thread 2 "isc-net-0000" hit Breakpoint 2, zone_journal_compact
>>> (zone=0x7ffff062ffd0, db=0x7ffff6151268, serial=1720448567) at
>>> ../../../lib/dns/zone.c:11654 11654 dns_db_currentversion(db, &ver); (gdb)
>>> n 11655 result = dns_db_getsize(db, ver, NULL, &dbsize); (gdb) s
>>> dns_db_getsize (db=0x7ffff6151268, version=0x7fffdba86640, records=0x0,
>>> bytes=0x7ffff5fcc4b8) at ../../../lib/dns/db.c:955 955 uint64_t *bytes) {
>>> (gdb) n 956 REQUIRE(DNS_DB_VALID(db)); (gdb) 957
>>> REQUIRE(dns_db_iszone(db)); (gdb) 959 if (db->methods->getsize != NULL) {
>>> (gdb) p db->methods->getsize $3 = (isc_result_t (*)(dns_db_t *,
>>> dns_dbversion_t *, uint64_t *, uint64_t *)) 0x0 The question now is: why is
>>> that getsize method NULL? Or, should it never have gotten here?
>>> -- Kees
>>>
>>> On 08-07-2024 13:42, Greg Choules wrote:
>>>> *** EXTERNAL E-MAIL ***
>>>>
>>>> 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
>
--
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
