-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Locust throwing connection error failures #638
Comments
Same issues.I've found the way to solve this problem. According to #92. add these to ur code to solve it
It's caused by the open file limit.The real reason is that your locustfile wasn't respecting the limit settings.
|
This is what i get when i print the resource limit (1048576, 1048576), so i'm not sure that's the reason the tests are failing @BlinkMo |
i Still get these errors: it seems to timeout for some reason |
Solved it. it was a docker issue. |
hey @broulaye how you solve it? i have the same error too when i try test HTTPS site. Thanks/ |
@broulaye I know its been over two years, but any chance you remember what the resolution was for the Docker issue? |
You can pass the setting through docker run apparently.
Found it here https://mtyurt.net/post/docker-how-to-increase-number-of-open-files-limit.html |
i have this simple node server i'm running locally and running a locust file from a container pointing at node. whenever i run from the container i get this error:
'''ConnectionError(MaxRetryError("HTTPConnectionPool(host='123.123.123.123', port=8000): Max retries exceeded with url: /icecream.txt (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x....>: Failed to establish a new connection: [Errno 110] Operation timed out',))",),)'''
And it's not caused by the open file limit i checked and that seems ok. also when i run the same test locally instead of a container i dont encounter the same issue
The text was updated successfully, but these errors were encountered: