ehlo,
There are some false positive debug messages when you try
to invalidate automount entries.
sh# sss_cache -A --debug=0x00f0
[sss_cache] [sysdb_set_cache_entry_attr] (0x0080): ldb_modify failed: [No such
object](32)[ldb_wait: No such object (32)]
[sss_cache] [sysdb_set_entry_attr] (0x0080): Cannot set ts attrs for
name=auto.share1,cn=autofsmaps,cn=custom,cn=LDAP,cn=sysdb
[sss_cache] [sysdb_set_cache_entry_attr] (0x0080): ldb_modify failed: [No such
object](32)[ldb_wait: No such object (32)]
[sss_cache] [sysdb_set_entry_attr] (0x0080): Cannot set ts attrs for
name=auto.share2,cn=autofsmaps,cn=custom,cn=LDAP,cn=sysdb
[sss_cache] [sysdb_set_cache_entry_attr] (0x0080): ldb_modify failed: [No such
object](32)[ldb_wait: No such object (32)]
[sss_cache] [sysdb_set_entry_attr] (0x0080): Cannot set ts attrs for
name=auto.home,cn=autofsmaps,cn=custom,cn=LDAP,cn=sysdb
Only users and groups have timestamp data in separate cache.
It caused false positive warnings for autofs, netgroup ...
And I bet such messages are also in domain log file.
LS
Show replies by date