#7054 named-pkcs11 crashes immediately
Closed: invalid Opened by dcmcand.

named-pkcs crashes immediately on service startup. Centos 7.2 fulliy updated running freeipa. named log shows:
11-Jul-2017 14:24:04.342 client @0x7f15bd193bb0: udprecv
11-Jul-2017 14:24:04.350 fctx 0x7f15c8cb9010(./DNSKEY): timeout
11-Jul-2017 14:24:04.350 fctx 0x7f15c8cb9010(./DNSKEY): cancelquery
11-Jul-2017 14:24:04.350 fctx 0x7f15c8cb9010(./DNSKEY): try
11-Jul-2017 14:24:04.350 fctx 0x7f15c8cb9010(./DNSKEY): cancelqueries
11-Jul-2017 14:24:04.350 fctx 0x7f15c8cb9010(./DNSKEY): getaddresses
11-Jul-2017 14:24:04.350 rdataset.c:266: REQUIRE(rdataset->methods != ((void *)0)) failed, back trace
11-Jul-2017 14:24:04.350 #0 0x7f15d9737f30 in ??
11-Jul-2017 14:24:04.350 #1 0x7f15d8ca10ea in ??
11-Jul-2017 14:24:04.350 #2 0x7f15d8fe2268 in ??
11-Jul-2017 14:24:04.350 #3 0x7f15d8ff3f9c in ??
11-Jul-2017 14:24:04.350 #4 0x7f15d8ff4b3d in ??
11-Jul-2017 14:24:04.350 #5 0x7f15d8ff9a73 in ??
11-Jul-2017 14:24:04.350 #6 0x7f15d8cc1186 in ??
11-Jul-2017 14:24:04.350 #7 0x7f15d6ea6dc5 in ??
11-Jul-2017 14:24:04.350 #8 0x7f15d5f1f76d in ??
11-Jul-2017 14:24:04.350 exiting (due to assertion failure)


Hello, we need details from coredump with debuginfo, could you provide backtrace with debuginfo installed?

Here is the full debug log from /var/run/data/named.run
named.run

@dcmcand Hi, I'm afraid the debug log doesn't provide the information we need. Could you please examine and provide the backtrace from coredump? See https://docs.pagure.org/bind-dyndb-ldap/BIND9/Debugging/Coredump.html for instructions.

Hi @tkrizek,
The backtrace from the coredump shows:

0 0x00007f3e2dc4b1d7 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56

1 0x00007f3e2dc4c8c8 in __GI_abort () at abort.c:90

2 0x00007f3e315260fe in assertion_failed ()

3 0x00007f3e30a8f0ea in isc_assertion_failed () from /lib64/libisc-pkcs11.so.95

4 0x00007f3e30dd0268 in dns_rdataset_first () from /lib64/libdns-pkcs11.so.100

5 0x00007f3e30de1f9c in fctx_getaddresses () from /lib64/libdns-pkcs11.so.100

6 0x00007f3e30de2b3d in fctx_try () from /lib64/libdns-pkcs11.so.100

7 0x00007f3e30de7a73 in fctx_timeout () from /lib64/libdns-pkcs11.so.100

8 0x00007f3e30aaf186 in run () from /lib64/libisc-pkcs11.so.95

9 0x00007f3e2ec94dc5 in start_thread (arg=0x7f3e2b72b700) at pthread_create.c:308

10 0x00007f3e2dd0d76d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Is that what you need? or should I attach the whole core?

@dcmcand thanks for providing the traceback.

This looks like an issue with bind-pkcs11 component, not freeipa or bind-dyndb-ldap, so we can't do anything to fix it on our side.

Metadata Update from @tkrizek:
- Issue close_status updated to: invalid
- Issue status updated to: Closed (was: Open)

Metadata