Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

keep-alive for internal services #76

Closed
JanKoppe opened this issue Mar 10, 2017 · 2 comments
Closed

keep-alive for internal services #76

JanKoppe opened this issue Mar 10, 2017 · 2 comments
Assignees
Milestone

Comments

@JanKoppe
Copy link
Contributor

The current agent state implementation (#64) cannot clearly detect stuck or crashed services. We should implement a keep-alive function to fix this. I'm working on this right now. My approach is to add a timestamp column to the service state table that will be updated on set_service_status() call, including the main loops for the services. This timestamp can then be used to check if a service is still alive (i.e. not older than xx seconds).

@JanKoppe JanKoppe added this to the 2.1 milestone Mar 10, 2017
@JanKoppe JanKoppe self-assigned this Mar 10, 2017
@lkiesow lkiesow modified the milestones: 2.2, 2.1 Apr 25, 2017
@JanKoppe
Copy link
Contributor Author

This would be made somewhat obsolete by #144. One upside of a internal, python-only solution would be that it would work on a non systemd distribution, but I think we can neglect this because afaik pretty much every relevant system for pyca nowadays uses systemd.

@lkiesow
Copy link
Member

lkiesow commented Jun 27, 2020

Closing this since it's now taken care of by systemd.

@lkiesow lkiesow closed this as completed Jun 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants