So I am trying to add a few hundred .torrents to my watch folder to seed them, when my upload is done I go to rutorrent to see hows it going and every time I see the same exact thing. First 80-100 torrents are completed and seeding perfect, but the rest are just basically stuck at "Downloading" usually at like 80% and they throwing back and forth the same exact error: "unable to connect to UDP tracker".
I am trying to fix it for like a few days now and I think I read every remotely related issue here on github about this problem. I was playing around with "file limit" in system/rtorrent.service, because someone said it helped with hostname resolving error. I was also trying to use nscd and changing max_open's inside my .rtorrent.rc, but nothing worked for me, I think installing nscd helped me raise the limit from like first 50 to 100, but might be just random timing.
So how do I recreate this problem over and over:
1) Upload a few hundred .torrents to /watch/start
2) First ~100 are instantly "completed" (files for all of my torrents are already on my server) and seeding is perfect as I see from my other computers (instant connection to my server, good speed etc.)
3) All the other ones beside those first ~100 are going to "Downloading".
4) After like 30 seconds they start to go to "Error" (like 30 torrents each 5-10 seconds), so I end up with all torrents beside first 100 in "Error".
5) After some more time they try to go back to "Downloading", but come back to "Error" again.
6) All errors are the same - "Unable to connect to UDP tracker".
I think it is somewhat related to my server trying to send too much connection requests to trackers at the same time for those torrents to announce them and that's why it works only for first ~100 torrents, I don't have any other explanation in mind.
So I am trying to add a few hundred .torrents to my watch folder to seed them, when my upload is done I go to rutorrent to see hows it going and every time I see the same exact thing. First 80-100 torrents are completed and seeding perfect, but the rest are just basically stuck at "Downloading" usually at like 80% and they throwing back and forth the same exact error: "unable to connect to UDP tracker".
I am trying to fix it for like a few days now and I think I read every remotely related issue here on github about this problem. I was playing around with "file limit" in system/rtorrent.service, because someone said it helped with hostname resolving error. I was also trying to use nscd and changing max_open's inside my .rtorrent.rc, but nothing worked for me, I think installing nscd helped me raise the limit from like first 50 to 100, but might be just random timing.
So how do I recreate this problem over and over: 1) Upload a few hundred .torrents to /watch/start 2) First ~100 are instantly "completed" (files for all of my torrents are already on my server) and seeding is perfect as I see from my other computers (instant connection to my server, good speed etc.) 3) All the other ones beside those first ~100 are going to "Downloading". 4) After like 30 seconds they start to go to "Error" (like 30 torrents each 5-10 seconds), so I end up with all torrents beside first 100 in "Error". 5) After some more time they try to go back to "Downloading", but come back to "Error" again. 6) All errors are the same - "Unable to connect to UDP tracker".
I think it is somewhat related to my server trying to send too much connection requests to trackers at the same time for those torrents to announce them and that's why it works only for first ~100 torrents, I don't have any other explanation in mind.