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.

(In reply to Daniel Filho from comment #0)
> Description of problem:
> 
> SSSD Logs increased a lot after the customer upgrade his system to rhel 8.5
> 
> Common messages on /var/log/sssd/sssd_$domain
> [simple_check_get_groups_next] (0x0040): [RID#9070] Could not resolve name of group with GID XXXXX

This ^^ looks like an issue in the env that customer must fix.


> (2021-11-22  8:31:45): [nss] [cache_req_search_cache] (0x0020): CR #717453:
> Multiple objects were found when only one was expected!

This ^^ is interesting, this might indicate a bug in SSSD code. I saw this before in the logs, but didn't investigate yet.


As an immediate work around you can set `debug_backtrace_enabled = false` in respective sections of sssd.conf (or set `debug_level` to 0)
There is also an update planned in 8.5.1 - bz 2021499 - that will somewhat remediate this case.

But in general, the idea is that only real issues (i.e. requiring user action) should be reported with default settings.

*** This bug has been marked as a duplicate of bug 2021499 ***