Registered Member
|
I am still getting the stalled error with 3.2 release that was in RC1. I have seen different error messages from connection to tracker is broken and one error about bad data. A restart of the client is necessary to get the file transferring.
Thank you. KDE 4.20/Kubuntu 8.10 |
Moderator
|
The stalled bug has been fixed, I'm pretty certain of that. Do you get connected to peers ? If so are they all leechers who have nothing of the torrent ? |
Registered Member
|
|
Registered Member
|
I've been seeing problems like this with 3.1.6 and now 3.2. That is, I frequently end up with torrents declaring invalid data from tracker or connection broken. Restarting ktorrent does appear to fix it (at least it did the last time that I tried it), but the problem always seems to pop up again eventually. It happens primarily with one tracker which I have quite a few torrents from, but my other computer (which is using ktorrent 2.2.8 on a separate connection) never has this problem, so I'm not convinced that it's the tracker itself that's the problem. Unfortunately, I have found no pattern as to how it pops up. I was hoping that the issue would go away with 3.2, but no such luck.
I have no idea if this has any relation to the stalled bug from before. The torrents download and upload just fine as long as they have peers, but once they start start reporting in the announce box that they have invalid data from tracker or that the connection is broken, all the torrents with that tracker - whether they're new once the problem starts or have been running for a while - cease to be able to communicate properly with the tracker. So, I don't really have a problem with torrents stalling so much as being unable to talk with the tracker properly. I don't know if this happens with other trackers or not since most of my torrents are from the same tracker and I haven't paid adequate attention to determine if it's tracker specific. I'll have to take a look at that the next time that the problem crops up. |
Registered Member
|
Well, the problem just popped up again. At the moment, most of the time that a torrent announces, it either complains about the connection to the host being broken or there being invalid data from the tracker. Interestingly enough, the torrents from private trackers are almost always having the problem (once in a while one will announce properly but mostly not) but the public trackers aren't having any trouble. Also, restarting ktorrent didn't do anything this time. The problem is still there. However, most of the torrents managed to announce correctly when ktorrent first started up again. It was only upon further announces that it started failing again.
|
Registered Member
|
I'm getting the same problem with version 3.2 as well.
Currently I have 4 downloads, all from Demonoid. 1 of them is downloading fine, one keeps alternating between "stalled" and downloading 2 B/s, the other 2 are "stalled" and say the connection to the host is broken. I have the same behavior with torrents I've uploaded and am seeding as well. I've seen it happen with torrents from isohunt, piratebay, demonoid, etc. and there doesn't seem to be any common factor. |
Moderator
|
|
Registered Member
|
I don't even know what that means, sorry. I am getting a lot of "connection to host tracker.xxx.com is broken." I never had that error before. It has to be the client, because I have 40 torrents to the same tracker, pretty much all announcing at the same time, and it only shows up on one or two of the torrent. I have been using ktorrent for over two years, never got this error before. |
Moderator
|
Wireshark is a program to capture packets on network interfaces.
Connection to host is broken, just means that the connection got closed before the announce could be completed, it is unlikely that this is a KT problem, it is probably the tracker closing the connection. Which is why I need a wireshark trace, so I can see what exactly is happening. |
Moderator
|
OK, I had a look at your wireshark trace. Here is an example trace :
This is the request which KT sends :
This is the reply :
The problem here is that this is invalid HTTP, if the response contains content, then the Content-Length field must be present in the header (see http://www.faqs.org/rfcs/rfc1945.html section 7.2). This is not the case here, only the HTTP status line in the header is returned. So this tracker is returning invalid HTTP, and the KIO library (which handles the HTTP request), does not accept this. |
Moderator
|
|
Registered Member
|
Well, that makes it sound like Boxtorrents isn't doing quite what it's supposed to and that KIO can't consistently decide what to do about it. The reason that I'm not seeing this issue on my box with Ktorrent 2.2.8 may be because KIO in KDE 3.5 doesn't act the same way as KIO in KDE 4. |
Registered Member
|
|
Registered Member
|
I've been getting the "connection to tracker broken" on boxtorrents as well, mostly though only after making several announces. I _think_ they might ban people for a time if they announce more than 4 times an hour (they have a rule, max two torrents at any one time, and each torrent is set to auto announce 30min later).
But I can't be certain they are actually doing that... |
Registered Member
|
Yes! That is definitely the problem I have. Still, could someone help me how do I set ktorrent to prefer ipv4 without disabling ipv6 entirely? |
Registered users: Bing [Bot], Evergrowing, Google [Bot]