Tracker connection issues
Page 1 of 1 (7 posts)
Tags:
None
Registered Member 
|
Ktorrent: 4.1.1
My problem started when I was stress-testing a new router right after setting up a torrent proxy in ktorrent then disabling the proxy(too slow). I loaded about 200 torrents with 200 connections on a 35/35 fios link to stress-test a new ddwrt router for about a day before I could not connect to most trackers anymore. I thought that I might be banned due to over-scrapping, but qBittorrent doesn't have any tracker issues. At first it was "Cannot connect to tracker localhost" for a few days. Then it changed to "Timeout on tracker" for another few days. Then I checked "Do not use KIO for tracker announces", which was unchecked before. Now I get "invalid response from tracker". This happens to most trackers but not all. The tracker openbittorrent.org consistantly scraps just fine. Again, qBittorrent scraps all trackers just fine on the same torrents. My router is filled with 0.0.0.0<->0.0.0.0 ESTABLISHED in its NAT table when I leave Ktorrent running for a while. I moved my ~/.kde/share/config/ktorrent and ~/.kde/share/apps/ktorrent folders to a backup location to allow ktorrent to create new configs to see if my configurations were messing it up. But even with a clean config, the tracker errors didn't change. All of my ports are forwarded properly. Also, PeerExchange and DHT work fine. Based on the above information, is there any ideas as to what would cause the trackers not to scrap? |
|
Moderator
|
"Cannot connect to tracker localhost"
That sounds like you have a tracker in your torrent with localhost or 127.0.0.1 as address, which is pointless, because you aren't running a tracker. Anyway 200 connections on 200 torrents, means you are probably running out of file descriptors, which means you can't open new network connections. Linux is limited to 1024 open file descriptors per process by default. You can increase this, but I would not do that, it can lead to crashes due to a bug in Qt. |
|
Registered Member
|
Hi George, thanks for the reply.
The trackers listed in the UI are as they should be. IE: udp://tracker.openbittorrent.com/80/announce I thought it might be the IP Filter plugin, but the same behavior happens when it is disabled and I remove the ip_filter and level1.dat files from the ~/.kde/share/apps/ktorrent/ directory. My max file descriptors is MUCH higher than 1024:
I think that is stock for 64-bit with ext4 on Kubuntu. But that would be a non-issue in my case because I am only running 3 torrents right now with 20 max global connections. Also, qBittorrent runs parallel just fine on the same torrents. The 200/200 was only for about 24 hours. What things could I look for that would help us understand the problem? |
|
Registered Member
|
I have some new information.
Ifconfig shows that I am dropping MANY connections. I would venture to say that those dropped packets are my tracker connections:
Also my dmesg is filled up with the following:
Again, only Ktorrent is having the issue. QBittorrent runs as it should. |
|
Moderator
|
/proc/sys/fs/file-max is not the per process limit, you can find that with: ulimit -n |
|
Moderator
|
What is on port 11710 ? |
|
Registered Member
|
Sorry about that. You are right, my ulimit does show 1024. The port 11710 was my main ktorrent port. My tacker port at the time was 9473, which never showed up in dmesg.
I have since changed my ports to make more sense. Main: 10200, Tracker: 10201, DHT: 10202. qBittorrent- Main:10210. I also changed my max open files to 4096. (Probably unnecessary) |
Page 1 of 1 (7 posts)
Bookmarks
Who is online
Registered users: Bing [Bot], daret, Google [Bot], sandyvee, Sogou [Bot]
