#4166 timestamp cache entries are not created if missing
Closed: cloned-to-github 3 years ago by pbrezina. Opened 4 years ago by orion.

If somehow a timestamp cache entry is not created alongside a cache entry, the timestamp cache entry is never created.

(Tue Mar  3 15:52:33 2020) [sssd[be[nwra.com]]] [sysdb_store_group] (0x0400): Group "Boulder Administrators@ad.nwra.com" has been stored
GROUPNAME
(Tue Mar  3 15:52:33 2020) [sssd[be[nwra.com]]] [sysdb_check_ts_cache] (0x2000): Cannot find TS cac
he entry for [name=GROUPNAME,cn=groups,cn=ad.nwra.com,cn=sysdb]: [2]: No s
uch file or directory
(Tue Mar  3 15:52:33 2020) [sssd[be[nwra.com]]] [sysdb_check_and_update_ts_cache] (0x2000): No timestamps entry
(Tue Mar  3 15:52:33 2020) [sssd[be[nwra.com]]] [merge_msg_ts_attrs] (0x2000): No such DN in the timestamp cache: name=GROUPNAME,cn=groups,cn=ad.nwra.com,cn=sysdb
(Tue Mar  3 15:52:33 2020) [sssd[be[nwra.com]]] [sysdb_merge_res_ts_attrs] (0x2000): TS cache doesn't contain this DN, skipping
(Tue Mar  3 15:52:33 2020) [sssd[be[nwra.com]]] [merge_msg_ts_attrs] (0x2000): No such DN in the timestamp cache: name=GROUPNAME,cn=groups,cn=ad.nwra.com,cn=sysdb
(Tue Mar  3 15:52:33 2020) [sssd[be[nwra.com]]] [sysdb_merge_res_ts_attrs] (0x2000): TS cache doesn't contain this DN, skipping
(Tue Mar  3 15:52:33 2020) [sssd[be[nwra.com]]] [sysdb_set_cache_entry_attr] (0x0080): ldb_modify failed: [No such object](32)[ldb_wait from ldb_modify with LDB_WAIT_ALL: No such object (32)]
(Tue Mar  3 15:52:33 2020) [sssd[be[nwra.com]]] [sysdb_set_cache_entry_attr] (0x0400): No such entry
(Tue Mar  3 15:52:33 2020) [sssd[be[nwra.com]]] [sysdb_set_entry_attr] (0x0080): Cannot set ts attrs for name=GROUPNAME,cn=groups,cn=ad.nwra.com,cn=sysdb
(Tue Mar  3 15:52:33 2020) [sssd[be[nwra.com]]] [sysdb_store_group] (0x0400): Group "GROUPNAME" has been stored

This may have arisen from promoting an ipa client to a server.

sssd-2.2.0-19.el8.x86_64


Hi,

as an easy reproducer you can remove a single entry from the timestamp cache with ldbedit or remove just the timestamp cache in a SSSD restart cycle.

bye,
Sumit

Metadata Update from @thalman:
- Issue tagged with: Future milestone

4 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/5121

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 Update from @pbrezina:
- Issue close_status updated to: cloned-to-github
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.

Metadata