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

anyip-routes and route-tables services should be resilient to failures #6

Open
brakthehack opened this issue Dec 8, 2020 · 0 comments

Comments

@brakthehack
Copy link
Collaborator

If anyip-routes and route-tables crash for any reason, they currently stay dead because we do not have the unit files currently configured with any restart policy. We should configure these services with simple restart policies to ensure they can recover from any failures if a valid configuration becomes available at a later date.

Here's one such example:

[Unit]
StartLimitInterval=300
StartLimitBurst=3
[Service]
Restart=always
RestartSec=30

The files that need to be changed are:
anyip-routes.service
route-tables.service

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant