SSSD / sssd

#627 async bind race problem
Closed: Invalid Opened by jhrozek.

Closed: Invalid
Reopen Issue

Jan and I today independently found out that the sssd master has problems connecting to LDAP server. As we have been only able to reproduce the issue with servers running on localhost, we assume this may be a race condition. The backend process seemingly hangs on:

(Tue Sep 14 13:54:15 2010) [sssd[be[localdap]]] [sdap_id_op_connect_step] (9): waiting for connection to complete

I have bisected the problem to the async bind patch (56d8d19ac9d857580a233d8264e851883b883c67)

Bail out the async patch.

milestone: NEEDS_TRIAGE => SSSD 1.4.0

Fields changed

milestone: SSSD 1.4.0 => SSSD 1.5.0

This is related to ticket #88 and should be fixed together.

milestone: SSSD 1.5.0 => SSSD 1.6.0

Patch that cause this was reverted.

coverity: =>
resolution: => invalid
status: new => closed
upgrade: => 0

Fields changed

rhbz: => 0

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

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/1669

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.
Metadata
None
None
None
None
Normal
defect
SSSD
1.3.1
0
0
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.