zone_journal_compact: could not get zone size: not found

2024-07-08 Thread Kees Bakker via bind-users
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

Re: zone_journal_compact: could not get zone size: not found

2024-07-08 Thread Kees Bakker via bind-users
ssage 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 wrote: Hi, At the moment I have three FreeIPA systems (replicas), recently installed with

Re: zone_journal_compact: could not get zone size: not found

2024-07-08 Thread Kees Bakker via bind-users
he 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 wrote: Hi, At the moment I have three FreeIPA systems (replicas), recently installed with CentOS 9-Stream. All three of t

Re: zone_journal_compact: could not get zone size: not found

2024-07-09 Thread Kees Bakker via bind-users
ethod). -- 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 wrote:  Running gdb showed that the "not found" comes from thi

How to print details of dns_name_t* when hitting a gdb breakpoint in dns_name_equal

2024-12-03 Thread Kees Bakker via bind-users
Hi, Background I have a CentOS FreeIPA setup with with multiple named (bind9 9.16.23) servers. On two of my five servers, when I start named it fails a REQUIRE in dns_name_equal     /* * Either name1 is absolute and name2 is absolute, or neither is. */     REQUIRE((name1->attributes

Re: How to print details of dns_name_t* when hitting a gdb breakpoint in dns_name_equal

2024-12-05 Thread Kees Bakker via bind-users
On 04-12-2024 21:41, Petr Špaček wrote: [...] It sounds like you are able to reproduce it fairly easily, right? Yes, fairly easy. If that's the case I would recommend running `named` under RR debugger. In case you are not familiar with it have a look at https://rr-project.org/ - it is an _awe

Re: How to print details of dns_name_t* when hitting a gdb breakpoint in dns_name_equal

2024-12-04 Thread Kees Bakker via bind-users
On 03-12-2024 15:56, Petr Špaček wrote: On 03. 12. 24 11:36, Kees Bakker via bind-users wrote: I have a CentOS FreeIPA setup with with multiple named (bind9 9.16.23) servers. On two of my five servers, when I start named it fails a REQUIRE in dns_name_equal /*   * Either name1 is

Re: How to print details of dns_name_t* when hitting a gdb breakpoint in dns_name_equal

2024-12-06 Thread Kees Bakker via bind-users
r via bind-users wrote: On 03-12-2024 15:56, Petr Špaček wrote: On 03. 12. 24 11:36, Kees Bakker via bind-users wrote: I have a CentOS FreeIPA setup with with multiple named (bind9 9.16.23) servers. On two of my five servers, when I start named it fails a REQUIRE in dns_name_