We're not certain of the underlying cause yet, but the LDAP cleanup task on at least one user is failing because it is a member of a group for which its username is not listed as a memberuid.
The fact that the cache is in such a state is its own problem, but we should also address the symptom. If the memberUid is not present, we should just ignore it and move on (since the net effect we're looking for here is to have it removed anyway).
(Tue Feb 21 15:33:19 2012) [sssd[be[LDAP]]] [sysdb_search_users] (0x0400): Search users with filter: (&(objectclass=user)(&(!(dataExpireTimestamp=0))(dataExpireTimestamp<=1329856399)(!(lastLogin=*)))) (Tue Feb 21 15:33:19 2012) [sssd[be[LDAP]]] [cleanup_users] (0x0100): Found 18 expired user entries! (Tue Feb 21 15:33:19 2012) [sssd[be[LDAP]]] [sysdb_delete_entry] (0x0020): LDB Error: No such attribute(16) Error Message: [No matching attribute value when deleting attribute: memberuid on name=Development,cn=groups,cn=LDAP,cn=sysdb] (Tue Feb 21 15:33:19 2012) [sssd[be[LDAP]]] [sysdb_delete_user] (0x0400): Error: 14 (Bad address) (Tue Feb 21 15:33:19 2012) [sssd[be[LDAP]]] [ldap_id_cleanup_send] (0x0020): Failed to cleanup caches (14 [Bad address]), retrying later!
Fields changed
component: SSSD => memberOf Plugin version: 1.8.0 beta 2 => 1.8.0 beta 3
cc: => crazed
owner: somebody => jzeleny
milestone: NEEDS_TRIAGE => SSSD Deferred
rhbz: => 0
changelog: => design: => design_review: => 0 fedora_test_page: => mark: => 0 review: => 1 selected: => sensitive: => 0
There is not enough information to reproduce this bug anymore. I suggest we close this instance and reopen if the bug reappears.
resolution: => worksforme status: new => closed
Metadata Update from @sgallagh: - Issue assigned to jzeleny - Issue set to the milestone: SSSD Patches welcome
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/2246
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.