On Tue, Jun 23, 2015 at 06:42:02AM -0700, Janelle wrote:
My first post here. I have an issue with having occasional failures of LDAP
servers being used by SSSD. What happens is that when a new server is stood
up to replace the failed servers, users can't seem to login until SSSD is
restarted. Some users can, and it is hard to tell which can and can't. I
understand this is a caching setting or has something to do with caching,
but I don't fully understand why sssd can't just keep running. Prior to this
we used nslcd and never had these issues. Is this a known issue or am I
missing something in the setup?
Do the new servers have a different address? One possible reason is that
SSSD would keep the old connection (or remain offline) until you cycle
Would signaling sssd to switch to offline and online instead of
restarting it work equally?
pkill -USR1 sssd # Go offline
pkill -USR2 sssd # Go back online