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.

Sign up for GitHub

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

Jump to bottom

Client should restart if it's not able to sync to the server #62

Closed
glothriel opened this issue May 28, 2024 · 0 comments
Closed

Client should restart if it's not able to sync to the server #62

glothriel opened this issue May 28, 2024 · 0 comments
Assignees
@glothriel
Milestone
1.1.0

Comments

@glothriel
Copy link
Owner

glothriel commented May 28, 2024 •
edited
Loading

After a period (2m?) Clients should restart themselves (use liveness probes for that). There may be a case that server reconfigured wireguard and something's not right with the network.

Also add aggressive timeout to sync command (currently it's like 60s or so)
@glothriel glothriel added this to the 1.1.0 milestone Jun 5, 2024
@glothriel glothriel self-assigned this Jun 5, 2024
glothriel added a commit that referenced this issue Jun 5, 2024
@glothriel
#62 Client now restarts after sync failures
f797a49
glothriel added a commit that referenced this issue Jun 6, 2024
@glothriel
#62: Linter fixes
7cbbd77
glothriel added a commit that referenced this issue Jun 8, 2024
@glothriel
Merge pull request #74 from glothriel/62-client-restarts-after-sync-f…
9981e13 
…ailures

#62 Client now restarts after sync failures
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@glothriel glothriel

Labels
None yet
Projects
None yet
Milestone
1.1.0
Development

No branches or pull requests
1 participant
@glothriel