Improve logging when locust master port is busy. #1471
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.
Avoid issues like https://stackoverflow.com/questions/62769727/facing-error-address-already-in-use-while-running-locust
Instead of printing:
It will print something like:
[2020-07-07 10:19:28,906] lafp-mac-JG5J.int.svenskaspel.se/ERROR/locust.runners: The Locust master port (5557) was busy. Close any applications using that port - perhaps an old instance of Locust is still running? (Socket bind failure: Address already in use)