Learn more about these different git repos.
Other Git URLs
If for some reason the trust relationship to AD is broken (which might be a different bug...), there are two events logged to syslog every 1 minute:
Jul 13 21:12:19 sssd01 [sssd[ldap_child[10975]]]: Failed to initialize credentials using keytab [MEMORY:/etc/krb5.keytab]: Preauthentication failed. Unable to create GSSAPI-encrypted LDAP connection. Jul 13 21:12:19 sssd01 [sssd[ldap_child[10975]]]: Preauthentication failed
The second line that duplicates the error that is already contained in the first line: "Preauthentication failed", causes syslog to be not able to use the "last message repeated n times" feature.
I suggest to remove the second log event so that syslogd's "last message repeated n times" feature can work.
The first message is from this line https://pagure.io/SSSD/sssd/blob/master/f/src/providers/ldap/ldap_child.c#_453 and second one in done section https://pagure.io/SSSD/sssd/blob/master/f/src/providers/ldap/ldap_child.c#_530
Given that both are in the same function and the second one is called on any failure, I think we could just remove the first one and perhaps add the extended logging the first one has but the second one does not.
All in all, sounds like an easy fix for me..
Metadata Update from @jhrozek: - Issue set to the milestone: SSSD 1.15.4 - Issue tagged with: easyfix
Metadata Update from @jhrozek: - Issue priority set to: minor
PR:https://github.com/SSSD/sssd/pull/352
Metadata Update from @jhrozek: - Issue tagged with: PR
master:
Metadata Update from @lslebodn: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Metadata Update from @jhrozek: - Issue set to the milestone: SSSD 1.16.0 (was: SSSD 1.15.4)
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/4477
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Login to comment on this ticket.