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.
Comment 2RHEL Program Management
2011-04-06 15:24:06 UTC
Since RHEL 6.1 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.
Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.
Comment 5Stephen Gallagher
2011-04-14 15:23:20 UTC
Comment 9Stephen Gallagher
2011-04-14 15:42:04 UTC
These steps are a bit contrived, but they should adequately demonstrate the problem and the solution. Copy the three LDIF files attached to this bug to the test system. DO NOT PERFORM THIS TEST ON BARE IRON. Use a VM. If you don't kill the test before the memory grows too large, the OOM killer will start causing problems and you may have to forcibly kill the VM.
Steps to reproduce (all performed as root):
1) Set up SSSD with a single LOCAL domain (domain name must be LOCAL to use the attached LDIf files):
[sssd]
config_file_version = 2
services = nss, pam
domains = LOCAL
[nss]
[pam]
[domain/LOCAL]
description = LOCAL Users domain
id_provider = local
min_id = 1000
2) Stop SSSD, rm -f /var/lib/db/sssd.ldb; restart SSSD
3) Bulk load 10,000 users into the local domain using the usersadd.ldif
ldbadd -H /var/lib/db/sssd.ldb usersadd.ldif
4) Add the following two groups with the sss_groupadd command:
sss_groupadd largegroup1
sss_groupadd largegroup2
(They must be named largegroup1 and largegroup2 for the attached LDIFs to work properly)
5) Add the 10,000 users to each of those groups using groupadd.ldif
ldbmodify -H /var/lib/db/sssd.ldb groupadd.ldif
6) Open a separate window and run 'top'. Keep this window visible.
7) Remove group members from the two large groups using groupdel.ldif
ldbmodify -H /var/lib/db/sssd.ldb groupdel.ldif
While watching the 'top' window, you will see the memory percentage increase rapidly. Be prepared to kill the ldbmodify command before memory grows too high.
Comment 11Gowrishankar Rajaiyan
2011-04-15 15:19:40 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.
http://rhn.redhat.com/errata/RHSA-2011-0560.html
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.
http://rhn.redhat.com/errata/RHSA-2011-0560.html