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.
DescriptionThorsten Scherf
2017-08-23 11:55:24 UTC
Description of problem:
The ask here is to add a configuration option to tell the SSSD NSS responder to not create the memory cache when the option is set.
We have seen issues with disk space in environments where sssd is restarted in short intervals. It's clear that disabling the memory cache will have a negative impact on NSS performance, but in some situations it might be helpful to have such an option available.
Setting the "SSS_NSS_USE_MEMCACHE" env variable to "no" does not always help because some services clear their environment before starting the actual process. In this case the env variable is unset and the service is still using the memory cache even though it has been told to not use it.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
Verified the bug on SSSD Version : sssd-1.16.0-9.el7.x86_64
Steps followed during verification:
1. Ensure sssd service is running. Check the contents of /var/lib/sss/mc directory.
# ls /var/lib/sss/mc/
group initgroups passwd
2. Delete all the files from /var/lib/sss/mc/ and restart sssd service.
3. Upon service restart, you will see that all the files are re-created.
# ls /var/lib/sss/mc/
group initgroups passwd
4. Now, add memcache_timeout=0 in NSS section as given below:
[sssd]
config_file_version = 2
services = nss, pam
domains = LDAP
[nss]
filter_groups = root
filter_users = root
memcache_timeout=0
[pam]
[domain/LDAP]
debug_level = 0xFFF0
id_provider = ldap
ldap_uri = ldap://hubcap.lab.eng.pnq.redhat.com
ldap_search_base = dc=example,dc=com
5. Delete all the files from /var/lib/sss/mc/ and restart sssd service.
6. List the contents of /var/lib/sss/mc/, you will notice that dir /var/lib/sss/mc/ is empty, The files are not created since memory cache gets disabled.
# ls /var/lib/sss/mc/
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHEA-2018:0929