Increase healthcheck ping timeout #1627
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix #1582
For some reason, a 5 seconds timeout on ping specified as
-w 5
is sometimes too short for two pings to go through, most likely because of the delay between pings and...? I don't know, but it nevertheless causes some apparent ping loss, as the last ping is deemed unsuccessful. This in turn marks the container as unhealthy even when it is indeed connected to the VPN and able to reach the internet.I just increased the timeout to 10 seconds (for 2 pings). This seems awfully long for 2 small pings, but 🤷