Learn more about these different git repos.
Other Git URLs
Hello!
When we list the members of certain unix groups, we see on some nodes not the complete list. If I add or remove members has no effect To purge the cache with "sss_cache -E" has no effect. The only workaround is to remove the cache files and restart sssd. Afterwards everythings works and I can add add and remove members again.
When I log into a node with a broken cache I see lines like this in the log: [sssd[be[LDAP]]] [sysdb_set_cache_entry_attr] (0x0080): ldb_modify failed: No such object[ldb_wait from ldb_modify with LDB_WAIT_ALL: No such object (32)] [sssd[be[LDAP]]] [sysdb_set_entry_attr] (0x0080): Cannot set ts attrs for name=twhite@ldap,cn=users,cn=LDAP,cn=sysdb
If I remove manually one of the missing user record with ldbdel -H /var/lib/sss/db/cache_LDAP.ldb "name=foo@ldap,cn=users,cn=LDAP,cn=sysdb" and then run "sss_cache -E". I get "foo" in the list afterwards
Facts: Centos 7.5 sssd-1.16.0-19.el7.x86_64
<img alt="sssd.conf" src="/SSSD/sssd/issue/raw/files/551eb6e5a770820ab0565aa97a2e696f9a9b0a1de2c30f8f95b993bd6105dd3b-sssd.conf" />
The message is unrelated, it's just an optimalization technique (note the _ts_cache in the debug message).
Can you add the complete debug logs?
Ok I had the impression that the ldb_modfied failed only appears on the nodes with the broken cache.
<img alt="sssd_anon.log" src="/SSSD/sssd/issue/raw/files/67bcb86b3d2d06e7fda9f4a52ca7ded2dfb4dcd1fd1b3590b26b225050f733c7-sssd_anon.log" />
Hi there,
Has there been any progress on this issue? It appears that we're seeing the same thing - only affecting groups - on a significant number of our machines.
Scientific Linux 7.5 1.16.2-13.el7
Thanks Toby
Metadata Update from @pbrezina: - Issue tagged with: Future milestone
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/4859
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.
Metadata Update from @pbrezina: - Issue close_status updated to: cloned-to-github - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.