On 10/10/2016 10:09 AM, Fabiano Fidêncio wrote:
Victor,
On Mon, Oct 10, 2016 at 10:04 AM, Victor Tapia victor.tapia@canonical.com wrote:
Hi list,
I've faced a race condition when SSSD boots in a machine with a big clock drift. This is what I see:
- SSSD starts before the network is up, queries the LDAP server without
success and sets a retry timer (~60 secs) 2. NTP starts and corrects the clock, 1 hour back for example. 3. SSSD takes ~60 secs + the drift correction (1 hour) to retry the connection.
In this particular scenario the credentials cache is disabled, so the wait time to login is noticeable. How feasible would it be to use a monotonic clock for this kind of timed events?
Are you running git master? This issue is supposed to be already solved by https://github.com/SSSD/sssd/commit/b8ceaeb80cffb00c26390913ea959b77f7e848b9
This patch fix the issue only in watchdog which would result in terminating sssd otherwise. Fixing it across whole sssd would be difficult. The fix should go to tevent.