On Tue, Dec 04, 2012 at 08:50:23PM +0100, Jakub Hrozek wrote: > On Tue, Dec 04, 2012 at 02:38:34PM -0500, Simo Sorce wrote: > > On Tue, 2012-12-04 at 14:31 -0500, Qing Chang wrote: > > > On 04/12/2012 2:19 PM, Simo Sorce wrote: > > > > On Tue, 2012-12-04 at 13:11 -0500, Dmitri Pal wrote: > > > >>> A "service sssd restart" "fix" the problem... > > > >>> > > > >>> I am thinking of running a cron job of above every 10 minutes to > > > >> work > > > >>> around > > > >>> the problem while it is being troubleshoot. Is it a bad idea? > > > > Well every 10 min. seem a bit too much, but I guess it depends how long > > > > your user is willing to wait when it breaks :-/ > > > >> This thread reminded me of the following thread > > > >> https://lists.fedorahosted.org/pipermail/sssd-devel/2011-September/007058.html > > > > > > > > Yes Dmitri, this is very similar. > > > > > > > > Qing, > > > > do you happen to have the provider logs as well ? > > > > > > > > It seemed confined to the nss responder, but it may be an actual > > > > provider issue after all, seem like the provider is deleting the user > > > > from the cache from time to time, and it shouldn't. > > > > > > The provider has no means of deleting a user from cache, in the current > model, the responders are pure "readers" and only the back ends are > "writers".
I'm sorry, I swapped the terms responder and provider myself.. Simo was completely right, because the provider is the writer (at least I got that part right) and for some reason the provider removed the cached entry, then the nss responder could not read it from cache while offline and return it. Bottom line is, the domain logs Simo asked for would be welcome. Sorry for the confusion. _______________________________________________ sssd-devel mailing list [email protected] https://lists.fedorahosted.org/mailman/listinfo/sssd-devel
