On Tue, 16 Apr 2013, steve wrote:
Hi again OK, I found it. sss_cache
Unfortunately it gives an error even if a correct switch and domain are given:
sudo sss_cache -d default Usage: sss_cache [-?UGNSA] [-?|--help] [--usage] [-u|--user=STRING] [-U|--users] [-g|--group=STRING] [-G|--groups] [-n|--netgroup=STRING] [-N|--netgroups] [-s|--service=STRING] [-S|--services] [-a|--autofs-map=STRING] [-A|--autofs-maps] [-d|--domain=STRING] Please select at least one object to invalidate (Tue Apr 16 09:37:15:820975 2013) [sssd] [main] (0x0020): Error initializing context for the application
The other switches, e.g. sss_cache -u steve2 works OK.
sssd 1.9.4
Surely that should be:
sss_cache -d default -UG
or just
sss_cache -UG
But to be honest, I'd favour the more brutal technique while debugging. sss_cache invalidates the cache, but if sssd can't contact the LDAP servers it'll still serve from cache I thought. I may be wrong on that point though.
I've always gone for the completely unambiguous:
service sssd stop rm -f /var/lib/sss/{db,mc}/* /var/log/sssd/* service sssd start
That way, I'm clear that it knew nothing, and that the logs I'm looking at are 100% from the current config.
jh