Bug 2184566 - SSSD consume to much memory.
Summary: SSSD consume to much memory.
Keywords:
Status: NEW
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: sssd
Version: 8.5
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: Sumit Bose
QA Contact: sssd-qe
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-04-05 04:56 UTC by Paulo Serra
Modified: 2023-07-27 05:49 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-154043 0 None None None 2023-04-05 04:58:52 UTC

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.


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