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.
DescriptionKaushik Banerjee
2013-12-04 05:56:47 UTC
Created attachment 832421[details]
sssd_be crash backtrace
Description of problem:
sssd_be crashes occasionally
Version-Release number of selected component (if applicable):
sssd-common-1.11.2-10.el7
How reproducible:
The crash was seen a couple of times during the automation executions.
Steps to Reproduce:
1. Out of the couple of times the crash has happened, it was when sssd was starting up just after the "realm join" process.
Actual results:
sssd_be crashed. Attached the crash backtrace.
Expected results:
Additional info:
I cannot definitely say from backtrace why sssd crashed,
but it crashed on line:
strcasecmp(state->dns_domain, state->backup_domain)
It looks like backup_domain is valid, but dns_domain is NULL.
Could you also attach coredump?
Is there any interesting error message in domain log file?
(In reply to Lukas Slebodnik from comment #2)
> Could you also attach coredump?
> Is there any interesting error message in domain log file?
So far we haven't been able to save the coredump or retrieve any logs. Will attach the coredump when we see the same crash again.
This request was resolved in Red Hat Enterprise Linux 7.0.
Contact your manager or support representative in case you have further questions about the request.
Created attachment 832421 [details] sssd_be crash backtrace Description of problem: sssd_be crashes occasionally Version-Release number of selected component (if applicable): sssd-common-1.11.2-10.el7 How reproducible: The crash was seen a couple of times during the automation executions. Steps to Reproduce: 1. Out of the couple of times the crash has happened, it was when sssd was starting up just after the "realm join" process. Actual results: sssd_be crashed. Attached the crash backtrace. Expected results: Additional info: