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.

Description of problem:
If you have many users in /etc/passwd, sssd_be process eats 100 % CPU. 

Version-Release number of selected component (if applicable):
2.3.0-9.el8

How reproducible:


Steps to Reproduce:
1. put many users into /etc/passwd
2. start ssssd service
3. wait unitl it starts
4. touch /etc/passwd

Actual results:
sssd_be stops to work and eats 100 % CPU being restarted periodically.

Expected results:
continue to work.

Additional info:
if I delete ldb caches and start sssd again, it works until I touch passwd file again.

This is sssd.conf:

[sssd]
    services = pam
    domains = YYYY

[domain/YYYY]
    id_provider = files
    auth_provider = krb5
    krb5_realm = YYYY
    krb5_validate = true
    krb5_ccachedir = /tmp
    krb5_keytab = /etc/krb5.keytab
    krb5_server = XXXXX
    enumerate = False

Hi,

thanks for the report. It is a duplicate of bz 1693379.

As a work around you can disable implicit files provider (see `man sssd.conf`: enable_files_domain option) and change order of databases in /etc/nsswitch.conf to `files sss ...` (instead of `sss files ...`)

*** This bug has been marked as a duplicate of bug 1693379 ***

Can I disable files provider if I actually need kerberos authentication for users?

(In reply to Lukas Hejtmanek from comment #2)
> Can I disable files provider if I actually need kerberos authentication for
> users?

You can try to use
```
    id_provider = proxy
    proxy_lib_name = files
```
instead of 'id_provider = files' (and keeping krb5 for auth)