Learn more about these different git repos.
Other Git URLs
Start sssd with -d 4 (or higher). Watch until the ping interval occurs. You should see all of the configured components pinged at the same time.
Now, kill one of them with a SIGTERM (I killed the Data Provider). It will automatically restart.
Watch the output in the console. It will be pinged once with all of the other services, and again at a different time. Kill it again and you will see three pings, etc.
We need to ensure that we remove the original ping request when restarting the service, else in a very long-running situation we could end up wasting a lot of time processing pings.
Fields changed
component: component1 => Service Monitor
Fixed by commit [403c91f]
resolution: => fixed status: new => closed
rhbz: => 0
Metadata Update from @sgallagh: - Issue assigned to sgallagh
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/1043
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.