Kees Bakker via FreeIPA-users wrote:
> On 04-11-2024 12:56, Florence Blanc-Renaud wrote:
>> Hi,
>>
>> On Fri, Nov 1, 2024 at 3:51 PM Kees Bakker via FreeIPA-users
>> <[email protected]> wrote:
>>
>>     Hi,
>>
>>     After a scheduled power down on and power up on one of our IPA
>>     servers
>>     named crashed.
>>     I remember I saw this before and that it was "solved" by
>>     restarting named.
>>     This time however it took about 12 retries before named finally
>>     continued.
>>
>>     This is the error it produces
>>     ../../../lib/dns/name.c:667: REQUIRE((name1->attributes &
>>     0x00000001) ==
>>     (name2->attributes & 0x00000001)) failed, back trace
>>
>>     bind9 is quite drastic when it hits a failing REQUIRE. It immediately
>>     stops with a coredump.
>>     But it doesn't tell which names are failing the comparison.
>>
>>     Of course I can (or should) report this to the bind developers.
>>     However,
>>     I'm sure they
>>     are going to say that this is an old version and that I should ask
>>     CentOS/RH devs.
>>
>> The issue has already been reported here:
>> https://issues.redhat.com/browse/RHEL-30407
>>
>>
>>     If anybody here on the list has an idea, then please let me know.
>>
>>     Some more details
>>     Version info:
>>     * os: CentOS 9-Stream
>>     * ipa packages 4.12.0-4.el9
>>     * bind9 packages 32:9.16.23-15.el9
>>     * bind-libdyndb-ldap 11.9.8-el9
>>
>> Some updates are available for those packages, it may be worth trying.
> 
> Nope. With the latest CentOS 9-Stream packages it is also crashing at
> startup.
> 
> Version info:
> * ipa packages: 4.12.2-1.el9
> * bind packages: 32:9.16.23-24.el9
> * bind-libdyndb-ldap: 11.9-10.el9
> 
> The only thing for me to do is to keep retrying to start named until it
> finally stays up and running.
> 
> It would help if I knew a little bit more what is in that RHEL-30407 issue.

It probably wouldn't. There are some stack traces there with a similar
assertion failure but no solutions yet. If you want to provide a stack
trace we could confirm it is identical but in the end it would just be
"yup, same thing" and still wouldn't be that helpful.

The bind developer has been looking into it but the root cause has been
elusive.

rob

-- 
_______________________________________________
FreeIPA-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedorahosted.org/archives/list/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to