You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 4, 2021. It is now read-only.
I've having some connectivity issue with your container under my synology.
No connectivity to the outside world which is odd.
Could you look also if your container use IPV6 is available and if yes to add something your code to disable that (I remember that diameter had to do the same thing for his rtorrent.
The text was updated successfully, but these errors were encountered:
Would you think it's a ressource issue or something else? It s clearly not networking.
What would you need to diagnostic this kind of thing? A docker logs?
Okey it seems to be a perf issue. With only 221 torrents ( not necessarily all actives, so like previous screen) there have again full connectivity or nearly at least.
Maybe I'm missing something here. Shouldn't the stopped torrents not using any ressources? So is it a rtorrent problem or an interface problem or something else?
I m going to pull some logs from the container and See if there are some clues but I would really like your input on this.
And by the way not all the cpu nor the ram was being used. I have made sure of that
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I've having some connectivity issue with your container under my synology.
No connectivity to the outside world which is odd.
Could you look also if your container use IPV6 is available and if yes to add something your code to disable that (I remember that diameter had to do the same thing for his rtorrent.
The text was updated successfully, but these errors were encountered: