SSSD / sssd

#2455 Log shows "Internal Error" when sssd comes back online and has wrong bind password
Closed: wontfix by pbrezina. Opened by mkosek.

Closed: wontfix
Reopen Issue

Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 6): Bug 1150025

Description of problem:
Bug 902436 fixed the segfault, but we see "Internal Error" in the domain log.
Version-Release number of selected component (if applicable):
sssd-1.11.6-30.el6
How reproducible:
Always
Steps to Reproduce:
Same as in bug 902436
1. sssd.conf domain section has:
ldap_default_bind_dn = cn=Manager,dc=example,dc=com
ldap_default_authtok = wrongpassword
2. Wait for sssd to come back online.
3. Check the domain log.
Actual results:
Domain log shows "Internal Error" when sssd tries to come back online.
Domain log shows:
(Tue Oct  7 05:20:47 2014) [sssd[be[LDAP]]] [simple_bind_send] (0x0100):
Executing simple bind as: cn=Manager,dc=example,dc=com
(Tue Oct  7 05:20:47 2014) [sssd[be[LDAP]]] [simple_bind_send] (0x2000): ldap
simple bind sent, msgid = 2
(Tue Oct  7 05:20:47 2014) [sssd[be[LDAP]]] [sdap_process_result] (0x2000):
Trace: ldap_result found nothing!
(Tue Oct  7 05:20:47 2014) [sssd[be[LDAP]]] [sdap_process_message] (0x4000):
Message type: [LDAP_RES_BIND]
(Tue Oct  7 05:20:47 2014) [sssd[be[LDAP]]] [simple_bind_done] (0x1000): Server
returned no controls.
(Tue Oct  7 05:20:47 2014) [sssd[be[LDAP]]] [simple_bind_done] (0x0400): Bind
result: Invalid credentials(49), no errmsg set
(Tue Oct  7 05:20:47 2014) [sssd[be[LDAP]]] [fo_set_port_status] (0x0100):
Marking port 636 of server 'ldapserver.example.com' as 'not working'
(Tue Oct  7 05:20:47 2014) [sssd[be[LDAP]]] [fo_set_port_status] (0x0400):
Marking port 636 of duplicate server 'ldapserver.example.com' as 'not working'
(Tue Oct  7 05:20:47 2014) [sssd[be[LDAP]]] [remove_connection_callback]
(0x4000): Successfully removed connection callback.
(Tue Oct  7 05:20:47 2014) [sssd[be[LDAP]]] [check_online_callback] (0x0100):
Backend returned: (3, 0, <NULL>) [Internal Error (Success)]
Expected results:
Any meaningful error instead of Internal Error
Additional info:

Moving to 1.13 as agreed on last week's meeting.

blockedby: =>
blocking: =>
changelog: =>
coverity: =>
design: =>
design_review: => 0
feature_milestone: =>
fedora_test_page: =>
mark: no => 0
milestone: NEEDS_TRIAGE => SSSD 1.13 beta
review: True => 0
selected: =>
testsupdated: => 0

Fields changed

milestone: SSSD 1.13 beta => SSSD 1.13 backlog
priority: major => trivial

Mass-moving tickets not planned for any immediate release and re-setting priority.

milestone: SSSD 1.13 backlog => SSSD Deferred
priority: trivial => major

Metadata Update from @mkosek:
- Issue set to the milestone: SSSD Patches welcome

Thank you for taking time to submit this request for SSSD. Unfortunately this issue was not given priority and the team lacks the capacity to work on it at this time.

Given that we are unable to fulfill this request I am closing the issue as wontfix.

If the issue still persist on recent SSSD you can request re-consideration of this decision by reopening this issue. Please provide additional technical details about its importance to you.

Thank you for understanding.

Metadata Update from @pbrezina:
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)

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

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
None
0
0
https://bugzilla.redhat.com/show_bug.cgi?id=1150025
0
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.