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.
How is it a duplicate, I can't see it. Result is the same, sssd crashes but according to github the issue marked as duplicate was fix in January although in July similar crashes appear. I marked this issue as urgen for a reason! I did update few systems to the latest patch lavel at the beginning of the June but still there is no fix for this crash despite that I'm not the only one facing this issue.
Please check bz 1792184 which is public (btw, there are offered a couple of temporary workarounds)
Issue is fixed upstream in `master` branch, in Fedora and in RHEL8.
Is is not yet fixed in RHEL7 and this is tracked in bz 1854317 (I will check if description can be made public or will add a public comment). Please, do not reopen this ticket as this won't help in anyway.
*** This bug has been marked as a duplicate of bug 1854317 ***
Created attachment 1701553 [details] Sample configuration with multiple ldap back-ends Description of problem: Version-Release number of selected component (if applicable): sssd packages version 1.16.4-37.el7_8.3 How reproducible: every time Steps to Reproduce: 1. update sssd from version 1.16.4-21.el7_7.3 to1.16.4-37.el7_8.3 2. restart sssd daemon 3. daemon fails Actual results: hard failure, entire sssd based identity managemnt dies Expected results: sssd starts and provides it's intended services to the system Additional info: Exactly the same configuration with multiple ldap back-end domains works correctly with version 1.16.4-21.el7_7.3 but fails with segfault when updated to 1.16.4-37 dmesg: [Thu Jul 16 16:13:54 2020] sssd_be[172815]: segfault at 0 ip 00007fea26d302e2 sp 00007ffd755e19e8 error 4 in libsss_util.so[7fea26d13000+8c000] [Thu Jul 16 16:13:54 2020] Code: d0 75 07 48 83 c4 18 5b 5d c3 e8 c9 9d ff ff 66 0f 1f 84 00 00 00 00 00 48 8b 86 c0 00 00 00 48 8b 4e 08 48 8d 15 86 ad 04 00 <48> 8b 30 31 c0 e9 64 a0 ff ff 0f 1f 40 00 55 48 89 fd 31 ff 53 48