Bug 1913378

Summary:	[abrt] krb5-server: krb5kdc killed by SIGABRT
Product:	Red Hat Enterprise Linux 7	Reporter:	Vinay Mishra <vmishra>
Component:	ipa	Assignee:	Florence Blanc-Renaud <frenaud>
Status:	CLOSED DUPLICATE	QA Contact:	ipa-qe <ipa-qe>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	7.9	CC:	dpal, fdvorak, rcritten, tscherf
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-01-12 14:14:24 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:

Comment 3 Rob Crittenden 2021-01-06 21:55:00 UTC

ipa-server-4.6.8-5.el7.x86_64
389-ds-base-1.3.10.2-8.el7_9.x86_64

Is there any context on what was happening when this occurred?

Can we get a full sosreport?

Comment 4 Vinay Mishra 2021-01-07 15:42:30 UTC

(In reply to Rob Crittenden from comment #3)
> ipa-server-4.6.8-5.el7.x86_64
> 389-ds-base-1.3.10.2-8.el7_9.x86_64
> 
> Is there any context on what was happening when this occurred?
> 
> Can we get a full sosreport?

Hello Rob,

SOS report is attached to the case now.

Thanks
Vinay

Comment 5 Rob Crittenden 2021-01-07 19:35:40 UTC

The reported crash was:

reason:         krb5kdc killed by SIGABRT
time:           Sun Dec 27 07:10:40 2020
cmdline:        /usr/sbin/krb5kdc -P /var/run/krb5kdc.pid -w 4
package:        krb5-server-1.15.1-50.el7
uid:            0 (root)
count:          5

The logs in the sosreport only cover since the beginning of the year so aren't helpful.

Per the stack trace it is failing in ipadb_parse_user_auth() due to a NULL ld value, which means there was no LDAP connection.

Understanding the context of the failure will help reproduce it and lead to a better fix.

The fact that it failed in early morning Sunday just after Christmas it may be safe to assume there was limited activity which could help narrow down what was happening at the time.

Are there logs available that cover the time period of the crash?

Comment 6 Rob Crittenden 2021-01-12 14:14:24 UTC

The stack trace is identical to the one in BZ 1835741. Marking as a duplicate.

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