#1702 sssd_nss crashes during enumeration
Closed: Duplicate None Opened 8 years ago by jhrozek.

https://bugzilla.redhat.com/show_bug.cgi?id=885078 (Red Hat Enterprise Linux 6)

Description of problem:
sssd_nss crashes during enumeration and with ldap_default_bind_dn in sssd.conf

Version-Release number of selected component (if applicable):

How reproducible:
Almost always. The crash is in middle of enumerating 30k users on the ldap

Steps to Reproduce:
1. Setup sssd with the following in domain section:
enumerate = True
debug_level = 0xFFF0
cache_credentials = True
ldap_search_base = dc=example,dc=org
id_provider = ldap
auth_provider = ldap
chpass_provider = ldap
ldap_uri = ldap://ldapserver.example.org
ldap_default_bind_dn = cn=Manager,dc=example,dc=org
ldap_default_authtok = password

2. Observe the domain log. Wait for enumeration to complete.

Actual results:
Enumeration goes on forever. And sssd_nss crashes after sometime. See
attachment for backtrace.

sssd_be cpu usage is about 98%
21727 root      20   0  383m 167m 3572 R 98.1 16.9   1:09.61 sssd_be

Expected results:
Enumeration should complete and sssd_nss should not crash.

Additional info:

Fields changed

blockedby: =>
blocking: =>
coverity: =>
design: =>
design_review: => 0
feature_milestone: =>
fedora_test_page: =>
owner: somebody => jhrozek
status: new => assigned
testsupdated: => 0

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.9.4

Because of the extremely long time the enumeration took, Kaushik actually ended up hitting #1717. He verified that he's no longer seeing the crashes with Simo's patch for #1717 and neither did I. Marking as a duplicate.

resolution: => duplicate
status: assigned => closed

Metadata Update from @jhrozek:
- Issue assigned to jhrozek
- Issue set to the milestone: SSSD 1.9.4

4 years ago

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/2744

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Login to comment on this ticket.