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

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.


Fixed by:
- d0d3497 (master)
- d2e36fc (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

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

Login to comment on this ticket.

Metadata