Bug 2131184
| Summary: | named-pkcs11: exiting (due to assertion failure) dumping core: REQUIRE(rdataset->methods != ((void *)0)) | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Aleksandr Sharov <asharov> | ||||
| Component: | bind | Assignee: | Petr Menšík <pemensik> | ||||
| Status: | ASSIGNED --- | QA Contact: | rhel-cs-infra-services-qe <rhel-cs-infra-services-qe> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 7.9 | CC: | pemensik, rcritten, sam, tscherf | ||||
| Target Milestone: | rc | Keywords: | Triaged | ||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | Type: | Bug | |||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | 1854473, 1891410 | ||||||
| Bug Blocks: | 2216096 | ||||||
| Attachments: |
|
||||||
|
Description
Aleksandr Sharov
2022-09-30 08:26:44 UTC
I don't see any real concurrency in attached core dump. It terminates with REQUIRE(rdataset->methods != ((void *)0)) failed, on line lib/dns-pkcs11/rdataset.c:263, which suggests rdataset in iteration were disassociated. But I don't see any real concurrency. Thread 1 is doing fctx_try and Thread 5 processing ldap change. Other threads seems to be idling. It seems the crash logged at beginning of named.run happens during managed-keys priming, the failing query was ./DNSKEY. 28-Sep-2022 03:07:02.458 managed-keys-zone: journal file is out of date: removing journal file 28-Sep-2022 03:07:02.458 managed-keys-zone: loaded serial 54749 28-Sep-2022 03:07:02.458 zone 0.in-addr.arpa/IN: loaded serial 0 28-Sep-2022 03:07:02.459 zone localhost/IN: loaded serial 0 28-Sep-2022 03:07:02.459 zone 1.0.0.127.in-addr.arpa/IN: loaded serial 0 28-Sep-2022 03:07:02.459 zone 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa/IN: loaded serial 0 28-Sep-2022 03:07:02.459 zone localhost.localdomain/IN: loaded serial 0 28-Sep-2022 03:07:02.459 all zones loaded 28-Sep-2022 03:07:02.460 running 28-Sep-2022 03:07:02.480 LDAP configuration for instance 'ipa' synchronized 28-Sep-2022 03:07:02.498 LDAP data for instance 'ipa' are being synchronized, please ignore message 'all zones loaded' 28-Sep-2022 03:07:03.261 network unreachable resolving './NS/IN': 2001:7fd::1#53 28-Sep-2022 03:07:03.261 network unreachable resolving './NS/IN': 2001:500:2f::f#53 28-Sep-2022 03:07:03.261 network unreachable resolving './NS/IN': 2001:500:1::53#53 28-Sep-2022 03:07:03.261 network unreachable resolving './NS/IN': 2001:500:200::b#53 28-Sep-2022 03:07:03.261 network unreachable resolving './NS/IN': 2001:503:c27::2:30#53 28-Sep-2022 03:07:03.261 network unreachable resolving './NS/IN': 2001:dc3::35#53 28-Sep-2022 03:07:03.261 network unreachable resolving './NS/IN': 2001:503:ba3e::2:30#53 28-Sep-2022 03:07:03.261 network unreachable resolving './NS/IN': 2001:7fe::53#53 28-Sep-2022 03:07:03.261 network unreachable resolving './NS/IN': 2001:500:9f::42#53 28-Sep-2022 03:07:03.261 network unreachable resolving './NS/IN': 2001:500:2d::d#53 28-Sep-2022 03:07:03.261 network unreachable resolving './NS/IN': 2001:500:a8::e#53 28-Sep-2022 03:07:03.261 network unreachable resolving './NS/IN': 2001:500:2::c#53 28-Sep-2022 03:07:03.261 network unreachable resolving './NS/IN': 2001:500:12::d0d#53 28-Sep-2022 03:07:04.862 ../../../lib/dns-pkcs11/rdataset.c:263: REQUIRE(rdataset->methods != ((void *)0)) failed, back trace This issue might be related to bind-dyndb-ldap, but seems primary in bind component, named-pkcs11 service. I would recommend the customer using OPTIONS="-4" in /etc/sysconfig/named. When IPv6 is not available on the host, it would save named trying from accessing it. It would make all outgoing queries IPv4 only, because it seems all IPv6 queries are failing anyway on this host. Probably would not avoid hitting this issue, but would save some CPU cycles for important stuff. And log less warnings. I would suggest workaround recommended in https://bugzilla.redhat.com/show_bug.cgi?id=1935152#c36 It would not prevent those crashes, but would make them less noticeable. There has been bug #1891410 filled for this issue, which has been closed as a duplicate of bug #1891410, which is still open. Bug #1854473 is the correct one still open for bind-dyndb-ldap. |