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.
Description of problem:
After ipa server installed , got three ipa-dnskeysync-replica and ipa-dnskeysncd related crash emails
Version-Release number of selected component (if applicable):
ipa-server-4.2.0-15
How reproducible:
Steps to Reproduce:
1.ipa server installed
Actual results:
Crash of ipa-dnskeysync-replica and ipa-dnskeysncd
Expected results:
No crash for these components
Additional info:
Attached full abrt emails
ipa-dnskeysync-replica cannot connect to DS
NetworkError: cannot connect to 'ldapi://%2fvar%2frun%2fslapd-TESTRELM-TEST.socket
Is DS operational?
also ipa-dnskeysyncd cannot get kerberos ticket
:LOCAL_ERROR: {'info': 'SASL(-1): generic failure: GSSAPI Error: Unspecified GSS failure. Minor code may provide more information (KDC returned error string: PROCESS_TGS)', 'desc': 'Local error'}
This might be also caused by non operational DS
Are there any issues with DS?
Those errors are not caused by DNSSEC daemons.
We do not have any information how to reproduce the problem with directory server so there is no way how to proceed without additional data. Feel free to reopen the bug whenever you reproduce the bug.
Comment 10Abhijeet Kasurde
2016-03-14 05:53:48 UTC
Per triage on 2016-04-28, we are closing this bug as INSUFFICIENT_DATA given that it happens rarely and there is no reliable reproducer.
with note:
pspacek: I do not like hidding the traceback because it would hide the problem with DS and do not solve the issue. Now we at least know that something does not work.