On Thu, 2016-08-18 at 09:09 -0700, Jeff White wrote:
I was able to get the group working again by doing:
systemctl stop sssd ; rm -f /var/lib/sss/db/* ; systemctl start sssd
Across all of my systems. I believe sssd may have actually seen a duplicate GID at some point but it no longer exists. However, this issue has been going on for days, possibly weeks, and wasn't fixed by flushing cache. So why is sssd getting stuck like this?
I have seen similar issues, sss_cache -E does not clear everything and doing rm -f /var/lib/sss/db/* fixes whatever the problem is
Jocke