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.
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?
(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
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?