Learn more about these different git repos.
Other Git URLs
Monitor allows exactly 10 seconds for any service to start:
> /* 10 seconds should be plenty */ > tv = tevent_timeval_current_ofs(10, 0); > mini->timeout = tevent_add_timer(ctx->ev, mini, tv, init_timeout, mini);
But starts responders in 5 seconds:
[sssd] [services_startup_timeout] (0x0020): Providers did not start in time, forcing services startup!
Those two timeouts should be consistent (equal or second should be slightly greater)
Metadata Update from @atikhonov: - Issue assigned to atikhonov
Metadata Update from @jhrozek: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1645461
Issue linked to Bugzilla: Bug 1645461
Since Alexey said this issue seems to be so far impacting only the sssd-1-16 branch (more investigation is needed for the master branch), I'm so far moving the ticket to the 1.16 milestone. We can move the ticket around later if we change our minds.
Metadata Update from @jhrozek: - Issue set to the milestone: SSSD 1.16.4
PR for sssd-1-16 branch: https://github.com/SSSD/sssd/pull/771
As Pavel wrote about relevant timeout in master (2.x) branch: "There does not seem to be one. Not sure if it is by design or I just forgot to implement it. It is done in provider though." I will open separate ticket for this.
https://pagure.io/SSSD/sssd/issue/3981
Metadata Update from @atikhonov: - Issue tagged with: PR
Metadata Update from @jhrozek: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
SSSD is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in SSSD's github repository.
This issue has been cloned to Github and is available here: - https://github.com/SSSD/sssd/issues/4942
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Login to comment on this ticket.