Bug 2025682

Summary:	SSSD logs size increased so much after upgrading to 8.5
Product:	Red Hat Enterprise Linux 8	Reporter:	Daniel Filho <dcamilof>
Component:	sssd	Assignee:	Alexey Tikhonov <atikhono>
Status:	CLOSED DUPLICATE	QA Contact:	sssd-qe <sssd-qe>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	8.5	CC:	atikhono, grajaiya, jhrozek, lslebodn, mzidek, pbrezina, tscherf
Target Milestone:	rc	Keywords:	Triaged
Target Release:	---	Flags:	pm-rhel: mirror+
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-12-01 12:20:13 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Comment 1 Alexey Tikhonov 2021-11-24 13:24:22 UTC

(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.

Comment 8 Alexey Tikhonov 2021-12-01 12:20:13 UTC


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