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.
This bug is created as a clone of upstream ticket:
https://pagure.io/SSSD/sssd/issue/3465
I was working with lslebodn on IRC (freenode #sssd) and even after installing the latest LTM release 1.13.4 on EL6, sssd_be is leaking memory on systems with enumeration disabled and regular lookups going on. lslebodn mentioned: quick check of the valgrind log and it seems that 33MiB are leaked in cyrus sasl code
I have this issue on both EL6 (6.9) and EL7 (7.3). Attached is 2 hours of valgrind output of SSSD version 1.13.4 running on EL6. sssd on this server was last restarted on the evening of August 4th (less than 4 days ago) and sssd_be is currently using 125MiB of memory.
[](/SSSD/sssd/issue/raw/f77e8e5ac499a447a5a1a83e66305c477d5517ad8e92d7bd0ca151983b3c521e-valgrind_64systems.com_5394.log)
In all the testing we've done the increase seemed to have stabilized after some time which might be due to e.g sssd connecting to other domains or discovering more servers. We could never prove an ongoing leak, therefore I'm closing this bugzilla.