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.

Bug 2184566

Summary: SSSD consume to much memory.
Product: Red Hat Enterprise Linux 8 Reporter: Paulo Serra <paulo.serra>
Component: sssdAssignee: Sumit Bose <sbose>
Status: CLOSED MIGRATED QA Contact: sssd-qe
Severity: high Docs Contact:
Priority: unspecified    
Version: 8.5CC: aboscatt, atikhono, dchen, pbrezina
Target Milestone: rcKeywords: MigratedToJIRA
Target Release: ---Flags: pm-rhel: mirror+
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-09-14 08:19:53 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:

Description Paulo Serra 2023-04-05 04:56:26 UTC
Description of problem:
SSSD is consuming to much memory. This is increasing every day.
it will only drop if we restart the entire server.

Version-Release number of selected component (if applicable):
version 2.5.2

How reproducible:


Steps to Reproduce:
1. free -g every week
2.
3.

Actual results:
Wed Apr  5, 2023:
              total        used        free
Swap:          31Gi        23Gi       8.9Gi

14th march, 2023:
total used free shared
Swap: 31Gi 18Gi 13Gi

1st March,2023:

total used free shared 
Mem: 92Gi 75Gi 813Mi 5.0Mi 16Gi 16Gi
Swap: 31Gi 16Gi 15Gi

Expected results:
Not much usage in here since there is 14GB/16G available

Additional info:
for file in /proc/*/status ; do awk '/VmSwap|Name/{printf $2 " " $3}END{ print ""}' $file; done | sort -k 2 -n -r | less

sssd_nss 9663264 kB
sssd_be 4485876 kB
java 1100296 kB
postgres 266576 kB
firewalld 23736 kB
systemd-journal 22564 kB
tuned 20116 kB
polkitd 5788 kB
(sd-pam) 5272 kB
systemd-udevd 5104 kB

Comment 1 Ding-Yi Chen 2023-07-27 05:49:21 UTC
We would need to have the SSSD log and sosreport to have a better look

I suggest you open a support case so you can upload your sosreport and/or SSSD logs.

Comment 2 Sumit Bose 2023-09-07 09:18:26 UTC
Hi,

can you try to get a report on the used memory as described in https://sssd.io/contrib/talloc.html#identifying-memory-leaks ? If possible shortly after a restart and for a second time after SSSD was running for a while. Feel free to attach the created file here.

bye,
Sumit

Comment 3 RHEL Program Management 2023-09-14 08:14:52 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 4 RHEL Program Management 2023-09-14 08:19:53 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.

Comment 5 Red Hat Bugzilla 2024-01-13 04:25:23 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days