Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1693092

Summary:	[abrt] [faf] adcli: raise(): /usr/sbin/adcli killed by 6
Product:	Red Hat Enterprise Linux 7	Reporter:	Lukas Slebodnik <lslebodn>
Component:	adcli	Assignee:	Sumit Bose <sbose>
Status:	CLOSED DUPLICATE	QA Contact:	ipa-qe <ipa-qe>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.7	CC:	ashankar, codonell, dj, fweimer, mkosek, mnewsome, pcech, pfrankli, sbose
Target Milestone:	rc	Keywords:	Regression
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
URL:	http://faf.lab.eng.brq.redhat.com/faf/reports/bthash/b16b5db011da669ac06173eb89c9d4c5c85b4893/
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-04-15 08:38:37 UTC	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:

Description Lukas Slebodnik 2019-03-27 07:22:30 UTC

This bug has been created based on an anonymous crash report requested by the package maintainer.

Report URL: http://faf.lab.eng.brq.redhat.com/faf/reports/bthash/b16b5db011da669ac06173eb89c9d4c5c85b4893/

Comment 4 Sumit Bose 2019-03-27 07:53:33 UTC

Hi Lukas,

thanks for the report, this is most probably a double-free in adcli. Do you, by chance, have the verbose output of adcli, so that I can see how it got into this state?

bye,
Sumit

Comment 5 Lukas Slebodnik 2019-03-27 08:13:54 UTC

Here is output from journald:

Mar 26 17:34:31 kvm-04-guest20.host.example realmd[16655]:  * Set computer password
Mar 26 17:34:31 kvm-04-guest20.host.example realmd[16655]:  * Set computer password
Mar 26 17:34:31 kvm-04-guest20.host.example realmd[16655]:  * Retrieved kvno '3' for computer account in directory: CN=KVM-04-GUEST20,CN=Computers,DC=sssdad,DC=com
Mar 26 17:34:31 kvm-04-guest20.host.example realmd[16655]:  * Retrieved kvno '3' for computer account in directory: CN=KVM-04-GUEST20,CN=Computers,DC=sssdad,DC=com
Mar 26 17:34:31 kvm-04-guest20.host.example realmd[16655]:  * Checking HOST/kvm-04-guest20.sssdad.com
Mar 26 17:34:31 kvm-04-guest20.host.example realmd[16655]:  * Checking HOST/kvm-04-guest20.sssdad.com
Mar 26 17:34:31 kvm-04-guest20.host.example realmd[16655]:  *    Added HOST/kvm-04-guest20.sssdad.com
Mar 26 17:34:31 kvm-04-guest20.host.example realmd[16655]:  *    Added HOST/kvm-04-guest20.sssdad.com
Mar 26 17:34:31 kvm-04-guest20.host.example realmd[16655]:  * Checking HOST/KVM-04-GUEST20
Mar 26 17:34:31 kvm-04-guest20.host.example realmd[16655]:  * Checking HOST/KVM-04-GUEST20
Mar 26 17:34:31 kvm-04-guest20.host.example realmd[16655]:  *    Added HOST/KVM-04-GUEST20
Mar 26 17:34:31 kvm-04-guest20.host.example realmd[16655]:  *    Added HOST/KVM-04-GUEST20
Mar 26 17:34:31 kvm-04-guest20.host.example realmd[16655]:  ! Couldn't set service principals on computer account CN=KVM-04-GUEST20,CN=Computers,DC=sssdad,DC=com: 000020B5: Atr
Mar 26 17:34:31 kvm-04-guest20.host.example realmd[16655]:  ! Couldn't set service principals on computer account CN=KVM-04-GUEST20,CN=Computers,DC=sssdad,DC=com: 000020B5: Atr
Mar 26 17:34:31 kvm-04-guest20.host.example realmd[16655]:         0: 000020B5: DSID-0315274C, problem 1005 (CONSTRAINT_ATT_TYPE), data 0, Att 90303 (servicePrincipalName)
Mar 26 17:34:31 kvm-04-guest20.host.example realmd[16655]:         0: 000020B5: DSID-0315274C, problem 1005 (CONSTRAINT_ATT_TYPE), data 0, Att 90303 (servicePrincipalName)
Mar 26 17:34:31 kvm-04-guest20.host.example realmd[16655]: 
Mar 26 17:34:31 kvm-04-guest20.host.example realmd[16655]: 
Mar 26 17:34:31 kvm-04-guest20.host.example realmd[16655]:  * Discovered which keytab salt to use
Mar 26 17:34:31 kvm-04-guest20.host.example realmd[16655]:  * Discovered which keytab salt to use
Mar 26 17:34:31 kvm-04-guest20.host.example realmd[16655]:  * Added the entries to the keytab: KVM-04-GUEST20$@SSSDAD.COM: FILE:/etc/krb5.keytab
Mar 26 17:34:31 kvm-04-guest20.host.example realmd[16655]:  * Added the entries to the keytab: KVM-04-GUEST20$@SSSDAD.COM: FILE:/etc/krb5.keytab
Mar 26 17:34:31 kvm-04-guest20.host.example realmd[16655]:  * Added the entries to the keytab: host/KVM-04-GUEST20: FILE:/etc/krb5.keytab
Mar 26 17:34:31 kvm-04-guest20.host.example realmd[16655]:  * Added the entries to the keytab: host/KVM-04-GUEST20: FILE:/etc/krb5.keytab
Mar 26 17:34:31 kvm-04-guest20.host.example realmd[16655]:  * Added the entries to the keytab: host/kvm-04-guest20.host.example: FILE:/etc/krb5.keytab 
Mar 26 17:34:31 kvm-04-guest20.host.example realmd[16655]:  * Added the entries to the keytab: host/kvm-04-guest20.host.example: FILE:/etc/krb5.keytab 
Mar 26 17:34:31 kvm-04-guest20.host.example realmd[16655]:  * Added the entries to the keytab: RestrictedKrbHost/KVM-04-GUEST20: FILE:/etc/krb5.keytab
Mar 26 17:34:31 kvm-04-guest20.host.example realmd[16655]:  * Added the entries to the keytab: RestrictedKrbHost/KVM-04-GUEST20: FILE:/etc/krb5.keytab
Mar 26 17:34:31 kvm-04-guest20.host.example realmd[16655]:  * Added the entries to the keytab: RestrictedKrbHost/kvm-04-guest20.host.example: FILE:/etc/kr
Mar 26 17:34:31 kvm-04-guest20.host.example realmd[16655]:  * Added the entries to the keytab: RestrictedKrbHost/kvm-04-guest20.host.example: FILE:/etc/kr
Mar 26 17:34:31 kvm-04-guest20.host.example kernel: realmd[16655]: segfault at 0 ip 00007fa20a083e51 sp 00007ffeed781568 error 4 in libc-2.17.so[7fa209f15000+1c3000]
Mar 26 17:34:31 kvm-04-guest20.host.example abrt-hook-ccpp[16669]: Process 16660 (adcli) of user 0 killed by SIGABRT - dumping core
Mar 26 17:34:31 kvm-04-guest20.host.example abrt-hook-ccpp[16670]: Process 16655 (realmd) of user 0 killed by SIGSEGV - dumping core


or 


Mar 26 17:37:15 kvm-04-guest20.host.example realmd[21038]:  * Set computer password
Mar 26 17:37:15 kvm-04-guest20.host.example realmd[21038]:  * Set computer password
Mar 26 17:37:15 kvm-04-guest20.host.example realmd[21038]:  * Retrieved kvno '5' for computer account in directory: CN=KVM-04-GUEST20,CN=Computers,DC=sssdad,DC=com
Mar 26 17:37:15 kvm-04-guest20.host.example realmd[21038]:  * Retrieved kvno '5' for computer account in directory: CN=KVM-04-GUEST20,CN=Computers,DC=sssdad,DC=com
Mar 26 17:37:15 kvm-04-guest20.host.example realmd[21038]:  * Checking HOST/kvm-04-guest20.sssdad.com
Mar 26 17:37:15 kvm-04-guest20.host.example realmd[21038]:  * Checking HOST/kvm-04-guest20.sssdad.com
Mar 26 17:37:15 kvm-04-guest20.host.example realmd[21038]:  *    Added HOST/kvm-04-guest20.sssdad.com
Mar 26 17:37:15 kvm-04-guest20.host.example realmd[21038]:  *    Added HOST/kvm-04-guest20.sssdad.com
Mar 26 17:37:15 kvm-04-guest20.host.example realmd[21038]:  * Checking HOST/KVM-04-GUEST20
Mar 26 17:37:15 kvm-04-guest20.host.example realmd[21038]:  * Checking HOST/KVM-04-GUEST20
Mar 26 17:37:15 kvm-04-guest20.host.example realmd[21038]:  *    Added HOST/KVM-04-GUEST20
Mar 26 17:37:15 kvm-04-guest20.host.example realmd[21038]:  *    Added HOST/KVM-04-GUEST20
Mar 26 17:37:15 kvm-04-guest20.host.example realmd[21038]:  ! Couldn't set service principals on computer account CN=KVM-04-GUEST20,CN=Computers,DC=sssdad,DC=com: 00000057: Lda
Mar 26 17:37:15 kvm-04-guest20.host.example realmd[21038]:  ! Couldn't set service principals on computer account CN=KVM-04-GUEST20,CN=Computers,DC=sssdad,DC=com: 00000057: Lda
Mar 26 17:37:15 kvm-04-guest20.host.example realmd[21038]:  * Discovered which keytab salt to use
Mar 26 17:37:15 kvm-04-guest20.host.example realmd[21038]:  * Discovered which keytab salt to use
Mar 26 17:37:15 kvm-04-guest20.host.example realmd[21038]:  * Added the entries to the keytab: KVM-04-GUEST20$@SSSDAD.COM: FILE:/etc/krb5.keytab
Mar 26 17:37:15 kvm-04-guest20.host.example realmd[21038]:  * Added the entries to the keytab: KVM-04-GUEST20$@SSSDAD.COM: FILE:/etc/krb5.keytab
Mar 26 17:37:16 kvm-04-guest20.host.example realmd[21038]:  * Added the entries to the keytab: host/KVM-04-GUEST20: FILE:/etc/krb5.keytab
Mar 26 17:37:16 kvm-04-guest20.host.example realmd[21038]:  * Added the entries to the keytab: host/KVM-04-GUEST20: FILE:/etc/krb5.keytab
Mar 26 17:37:16 kvm-04-guest20.host.example realmd[21038]:  * Added the entries to the keytab: host/kvm-04-guest20.host.example: FILE:/etc/krb5.keytab 
Mar 26 17:37:16 kvm-04-guest20.host.example realmd[21038]:  * Added the entries to the keytab: host/kvm-04-guest20.host.example: FILE:/etc/krb5.keytab 
Mar 26 17:37:16 kvm-04-guest20.host.example realmd[21038]:  * Added the entries to the keytab: RestrictedKrbHost/KVM-04-GUEST20: FILE:/etc/krb5.keytab
Mar 26 17:37:16 kvm-04-guest20.host.example realmd[21038]:  * Added the entries to the keytab: RestrictedKrbHost/KVM-04-GUEST20: FILE:/etc/krb5.keytab
Mar 26 17:37:16 kvm-04-guest20.host.example realmd[21038]:  * Added the entries to the keytab: RestrictedKrbHost/kvm-04-guest20.host.example: FILE:/etc/kr
Mar 26 17:37:16 kvm-04-guest20.host.example realmd[21038]:  * Added the entries to the keytab: RestrictedKrbHost/kvm-04-guest20.host.example: FILE:/etc/kr
Mar 26 17:37:16 kvm-04-guest20.host.example kernel: traps: adcli[26437] trap stack segment ip:7fb9957be80c sp:7ffda81c3180 error:0
Mar 26 17:37:16 kvm-04-guest20.host.example kernel: realmd[21038]: segfault at 0 ip 00007f8cd1573e51 sp 00007fffd6dcc1f8 error 4
Mar 26 17:37:16 kvm-04-guest20.host.example kernel:  in libc-2.17.so[7f8cd1405000+1c3000]
Mar 26 17:37:16 kvm-04-guest20.host.example kernel: 
Mar 26 17:37:16 kvm-04-guest20.host.example kernel:  in libc-2.17.so[7fb99573e000+1c3000]
Mar 26 17:37:16 kvm-04-guest20.host.example kernel: 
Mar 26 17:37:16 kvm-04-guest20.host.example abrt-hook-ccpp[26457]: Process 26437 (adcli) of user 0 killed by SIGBUS - dumping core
Mar 26 17:37:16 kvm-04-guest20.host.example abrt-hook-ccpp[26456]: Process 21038 (realmd) of user 0 killed by SIGSEGV - dumping core

I tried to run adcli with valgrind; but I could not see any error or failure.

Comment 10 Martin Kosek 2019-04-09 11:12:18 UTC

We were not able to reproduce this crash so far. Any help with identifying the scenario is welcome!

Comment 11 Sumit Bose 2019-04-12 15:41:00 UTC

Hi,

jfyi, I came across the issue by chance and think I know how to fix it. It was introduced by the patch for https://bugzilla.redhat.com/show_bug.cgi?id=1630187. If you agree I will close this ticket as duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1630187 and switch https://bugzilla.redhat.com/show_bug.cgi?id=1630187 from ON_QA to POST?

bye,
Sumit

Comment 12 Sumit Bose 2019-04-15 08:38:37 UTC


*** This bug has been marked as a duplicate of bug 1630187 ***