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 725472 - [abrt] Process /usr/libexec/sssd/sssd_nss was killed by signal 11 (SIGSEGV)
Summary: [abrt] Process /usr/libexec/sssd/sssd_nss was killed by signal 11 (SIGSEGV)
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: sssd
Version: 7.0
Hardware: x86_64
OS: Linux
high
high
Target Milestone: pre-dev-freeze
: ---
Assignee: Jakub Hrozek
QA Contact: Kaushik Banerjee
URL:
Whiteboard:
Depends On:
Blocks: 727267 747123 756082
TreeView+ depends on / blocked
 
Reported: 2011-07-25 15:12 UTC by Andrea Cavallari
Modified: 2020-05-02 16:22 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-03-14 14:20:22 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
sssd coredump (1.59 MB, application/octet-stream)
2011-07-25 15:12 UTC, Andrea Cavallari
no flags Details


Links
System ID Private Priority Status Summary Last Updated
FedoraHosted SSSD 860 0 None None None Never
Github SSSD sssd issues 1974 0 None None None 2020-05-02 16:22:19 UTC

Comment 10 Stephen Gallagher 2011-07-26 15:06:59 UTC
It looks like there's a bug somewhere while chasing referrals with an authenticated bind. I'm not certain yet whether it is SSSD's bug or OpenLDAP's bug, but it will become irrelevant when we resolve
https://fedorahosted.org/sssd/ticket/860
(which is a complete rewrite of the referral code)

In the meantime, you can mitigate this issue by setting
ldap_referrals = false

in the [domain/default] section of your sssd.conf.

This will disable referral-following, so if you rely on referrals (e.g. you are using partial replication), it may not help. However, from the logs I can see you're talking to AD, which uses referrals automatically in many places, despite having no need to do so. I'd say there's a fair chance this will work for you as a workaround until we fix the above ticket.


Note You need to log in before you can comment on or make changes to this bug.