Braden McGrath via FreeIPA-users wrote:
> See subject... I have 3 CentOS 7 VMs running as FreeIPA Servers.
> 
> I ran a standard "yum update" as root; these packages were included as part 
> of that update:
> bind.x86_64                           32:9.11.4-26.P2.el7_9.16 
> bind-dyndb-ldap.x86_64        11.1-7.el7_9.1
> bind-export-libs.x86_64       32:9.11.4-26.P2.el7_9.16
> bind-libs.x86_64              32:9.11.4-26.P2.el7_9.16
> bind-libs-lite.x86_64         32:9.11.4-26.P2.el7_9.16
> bind-license.noarch           32:9.11.4-26.P2.el7_9.16
> bind-pkcs11.x86_64                    32:9.11.4-26.P2.el7_9.16
> bind-pkcs11-libs.x86_64       32:9.11.4-26.P2.el7_9.16
> bind-pkcs11-utils.x86_64      32:9.11.4-26.P2.el7_9.16
> bind-utils.x86_64                     32:9.11.4-26.P2.el7_9.16
> 
> Previously, bind-dyndb-ldap had been on 11.1-7.el7 (no "_9.1" suffix)
> And the rest had been on the exact same versions as above, but ending in .15.
> 
> After the upgrade, named-pkcs11 crashes when started by systemctl, with the 
> following journalctl output (server domain has been anonymized but everything 
> else was untouched):
> 
> Jul 02 19:39:19 ipa3.example.net named-pkcs11[10794]: 
> ../../../lib/dns-pkcs11/name.c:1114: REQUIRE((target != ((void *)0) && 
> (__builtin_expect(!!((target) != ((void *)0)), 1) && 
> __builtin_expect(!!(((const isc__magic_t *)(target))->magic == 
> (0x42756621U)), 1))) || (target == ((void *)0) && 
> (__builtin_expect(!!((name->buffer) != ((void *)0)), 1) && 
> __builtin_expect(!!(((const isc__magic_t *)(name->buffer))->magic == 
> (0x42756621U)), 1)))) failed, back trace
> Jul 02 19:39:19 ipa3.example.net named-pkcs11[10794]: #0 0x561df47e5130 in ??
> Jul 02 19:39:19 ipa3.example.net named-pkcs11[10794]: #1 0x7fac0362b48a in ??
> Jul 02 19:39:19 ipa3.example.net named-pkcs11[10794]: #2 0x7fac03930b7b in ??
> Jul 02 19:39:19 ipa3.example.net named-pkcs11[10794]: #3 0x7fabfb6efb78 in ??
> Jul 02 19:39:19 ipa3.example.net named-pkcs11[10794]: #4 0x7fabfb6effee in ??
> Jul 02 19:39:19 ipa3.example.net named-pkcs11[10794]: #5 0x7fabfb6f198b in ??
> Jul 02 19:39:19 ipa3.example.net named-pkcs11[10794]: #6 0x7fabfb6f1b89 in ??
> Jul 02 19:39:19 ipa3.example.net named-pkcs11[10794]: #7 0x7fabfb6fb528 in ??
> Jul 02 19:39:19 ipa3.example.net named-pkcs11[10794]: #8 0x7fac03650713 in ??
> Jul 02 19:39:19 ipa3.example.net named-pkcs11[10794]: #9 0x7fac0365128b in ??
> Jul 02 19:39:19 ipa3.example.net named-pkcs11[10794]: #10 0x7fac01726ea5 in ??
> Jul 02 19:39:19 ipa3.example.net named-pkcs11[10794]: #11 0x7fac00799b0d in ??
> Jul 02 19:39:19 ipa3.example.net named-pkcs11[10794]: exiting (due to 
> assertion failure)
> Jul 02 19:39:19 ipa3.example.net systemd[1]: named-pkcs11.service: main 
> process exited, code=killed, status=6/ABRT
> Jul 02 19:39:19 ipa3.example.net systemd[1]: Unit named-pkcs11.service 
> entered failed state.
> Jul 02 19:39:19 ipa3.example.net systemd[1]: named-pkcs11.service failed.
> 
> I was able to get named to start again by running a "yum downgrade" of the 
> above list of bind-related packages. Obviously, now the server is "behind" on 
> patches though.
> I'm not sure how to report this further to get it investigated/fixed, or if 
> any action will even be taken at this point now that CentOS7 is EOL.
> 
> I'm happy to provide additional details if requested.
> 
> Regards,
> Braden McGrath
> bra...@big-geek.net
> 

It appears that the centos 7 builds were done incorrectly. Given it is
EOL it is not likely to be addressed. We have little influence in centos.

rob

-- 
_______________________________________________
FreeIPA-users mailing list -- freeipa-users@lists.fedorahosted.org
To unsubscribe send an email to freeipa-users-le...@lists.fedorahosted.org
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/freeipa-users@lists.fedorahosted.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to