SSSD / sssd

#821 LDAP connection is not terminated when offline is triggered by other provider
Closed: Fixed Opened by sbose.

Closed: Fixed
Reopen Issue

In a setup with id_provider = LDAP and auth_provider = krb5 the LDAP connection is not properly terminated if the krb5 provider sets the backend offline. After some time the load might jump to 100% and a neverending sequence of log messages like

[sdap_process_result] (8): Trace: sh[0x154c4e0], connected[0], ops[(nil)], ldap[0x154d530]
[sdap_process_result] (2): ERROR: LDAP connection is not connected!
[sdap_process_result] (8): Trace: sh[0x154c4e0], connected[0], ops[(nil)], ldap[0x154d530]
[sdap_process_result] (2): ERROR: LDAP connection is not connected!

can be seen.

Related bugzilla entry: https://bugzilla.redhat.com/show_bug.cgi?id=683431

Fixed by:
- d0d3497c10a02e8489198dc3e1edc621bfac0c6d (master)
- d2e36fc224f57204dee65e232ff8e16f66e2ecd9 (sssd-1-5)

component: SSSD => LDAP Provider
milestone: NEEDS_TRIAGE => SSSD 1.5.2
resolution: => fixed
status: new => closed

Fields changed

rhbz: => 0

Metadata Update from @sbose:
- Issue set to the milestone: SSSD 1.5.2

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

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
LDAP Provider
1.5.1
None
0
None
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.