Slow rsync commands to prevent IP blocking #335
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced Dec 7, 2020
Member
|
Replacement PR with some improvements (based against openvas-20.08, sleep only for the GCF, sleep in various additional places, ...) is available here: #629 Let's hope that this is getting merged soon. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Two rsync commands run in fairly quick succession to check if the feed is current and sync down new changes if it is not. I've found these run too quickly most of the time and the second rsync is blocked by the server which causes the update to fail. Adding a delay before the second rsync resolves the issue.
This is related to the open pull request in the greenbone/gvmd repository:
Fix rsync errors due to IP blocking