-
-
Notifications
You must be signed in to change notification settings - Fork 114
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
an upstream response is buffered to a temporary file #176
Comments
I also see client prematurely closed connection in the logs
|
This is still happening but I was able to reduce the amount of messages/timeouts I've since seen that I had forgotten to include
from the docker compose file. I had originally just set this up in the Synology GUI. I recreated this container with the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Support guidelines
I've found a bug and checked that ...
Description
Once I got to more than 2,000 torrents added to rtorrent, I started seeing a ton of these messages
Expected behaviour
No errors or warnings should be shown and the image should be able to handle a large amount of torrents
Actual behaviour
Steps to reproduce
Add a large amount of torrents, between 2,000 and 5,000
Observe log messages showing nginx struggling
Docker info
Version
docker-compose version 1.28.5, build 24fb474e
Linux DiskStation 4.4.180+ #42661 SMP Fri Apr 1 15:31:10 CST 2022 x86_64 GNU/Linux synology_v1000_1821+
Docker compose
n/a
Container logs
Additional info
I've had this same issue with another docker image and increasing some nginx variables fixed it but I dont see any nginx configs in this image
The text was updated successfully, but these errors were encountered: