Tomasu wrote: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...

I don't recall what all the rules are, but personally, I'm a Power User on that site and I definitely don't have limits like that, though there might be such limits if you don't actually have an account. I have around 30 torrents going for Boxtorrents on my computer with Ktorrent 2.2.8 and I rarely - if ever - get this sort of problem. However, it pops up fairly frequently on my computer with Ktorrent 3.2, and Boxtorrents is not the only site with the problem. It seems to happen to most trackers at least from time to time, if not semi-frequently. Usually restarting Ktorrent fixes the problem at least temporarily.

Kalessin wrote:

Tomasu wrote: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...

I don't recall what all the rules are, but personally, I'm a Power User on that site and I definitely don't have limits like that, though there might be such limits if you don't actually have an account. I have around 30 torrents going for Boxtorrents on my computer with Ktorrent 2.2.8 and I rarely - if ever - get this sort of problem. However, it pops up fairly frequently on my computer with Ktorrent 3.2, and Boxtorrents is not the only site with the problem. It seems to happen to most trackers at least from time to time, if not semi-frequently. Usually restarting Ktorrent fixes the problem at least temporarily.

Indeed, it actually seems that the limit is 4 times per torrent per hour, and if you let the torrent do the updating itself (you don't hurry it along by manually updating a few times) you can't possibly hit that issue.

I have noticed a similar issue with 3.2 on my Ubuntu box. Everything runs fine for a few days maybe a week, but then for some reason all torrents say Announcing. A manual announce has the same problem. Torrents are still seeded and uploaded but the tracker never gets updated with the upload stats. Also my connectable status on the tracker site goes to Waiting. The only solution I have found is to restart KTorrent.

Is there some log file or command I can execute to give you more information?

pacha2 wrote:I have noticed a similar issue with 3.2 on my Ubuntu box. Everything runs fine for a few days maybe a week, but then for some reason all torrents say Announcing. A manual announce has the same problem. Torrents are still seeded and uploaded but the tracker never gets updated with the upload stats. Also my connectable status on the tracker site goes to Waiting. The only solution I have found is to restart KTorrent.

Is there some log file or command I can execute to give you more information?

~/.kde/share/apps/ktorrent/log

Should give us some idea what goes wrong.

I'm not sure if this is the same problem or just similar. But demonoid has all my torrents in ktorrent reporting "Invalid data from tracker" Restarting doesn't seem to help and neither does readding the torrent or new ones (though it did help ones and it worked until I closed ktorrent) He is the relevant part of the log.


Sat Apr 25 12:41:23 2009: Starting download T
Sat Apr 25 12:41:23 2009: Loading list of peers from /home//.kde/share/apps/ktorrent/tor35/peer_list
Sat Apr 25 12:41:23 2009: Loading 0 active chunk downloads
Sat Apr 25 12:41:23 2009: Doing tracker request to url : http://inferno.demonoid.com:3413/announ ... =����8�9�3�0���tT
Sat Apr 25 12:41:23 2009: Using proxy :
Sat Apr 25 12:41:23 2009: Timeout occurred
Sat Apr 25 12:41:23 2009: Authentication to 121.218.165.58 : failure
Sat Apr 25 12:41:23 2009: Timeout occurred
Sat Apr 25 12:41:23 2009: Authentication to 66.97.105.145 : failure
Sat Apr 25 12:41:23 2009: Timeout occurred
Sat Apr 25 12:41:23 2009: Authentication to 121.218.165.58 : failure
Sat Apr 25 12:41:23 2009: Timeout occurred
Sat Apr 25 12:41:23 2009: Authentication to 125.238.148.115 : failure
Sat Apr 25 12:41:23 2009: Timeout occurred
Sat Apr 25 12:41:23 2009: Authentication to 66.97.105.145 : failure
Sat Apr 25 12:41:24 2009: Timeout occurred
Sat Apr 25 12:41:24 2009: Authentication to 121.218.165.58 : failure
Sat Apr 25 12:41:24 2009: Timeout occurred
Sat Apr 25 12:41:24 2009: Authentication to 66.97.105.145 : failure
Sat Apr 25 12:41:24 2009: Selected tracker http://inferno.demonoid.com:3413/announce (tier = 1)
Sat Apr 25 12:41:24 2009: Timeout occurred
Sat Apr 25 12:41:24 2009: Authentication to 121.218.165.58 : failure
Sat Apr 25 12:41:24 2009: Timeout occurred
Sat Apr 25 12:41:24 2009: Authentication to 66.97.105.145 : failure

Thanks in advance for any light you can shed on this problem

Had the same stalling issue with private and public trackers till I disabled Peer Exchange (DHT was always off).

EDIT: Scratch that. Happened again. Just took more time.

I'm seeing a lot of this. I moved about ten half-finished downloads from KDE3 to KDE4, and now most of them are stalled. They were running fine before, the tracker websites say they have plenty of seeders and leechers, but all I'm getting is "invalid data" and "connection broken".

It looks like I'm not the only user with this problem -- is anything being done about it?

Niels wrote:I'm seeing a lot of this. I moved about ten half-finished downloads from KDE3 to KDE4, and now most of them are stalled. They were running fine before, the tracker websites say they have plenty of seeders and leechers, but all I'm getting is "invalid data" and "connection broken".

It looks like I'm not the only user with this problem -- is anything being done about it?

The connection broken problems are being looked into, but they are not that easy to reproduce, and they are probably KDE problems.

George wrote:

Niels wrote:I'm seeing a lot of this. I moved about ten half-finished downloads from KDE3 to KDE4, and now most of them are stalled. They were running fine before, the tracker websites say they have plenty of seeders and leechers, but all I'm getting is "invalid data" and "connection broken".

It looks like I'm not the only user with this problem -- is anything being done about it?

The connection broken problems are being looked into, but they are not that easy to reproduce, and they are probably KDE problems.

If any of the trackers are HTTPS, thats one potential problem. Qt's ssl is somewhat broken these days.

Tomasu wrote:

George wrote:

Niels wrote:I'm seeing a lot of this. I moved about ten half-finished downloads from KDE3 to KDE4, and now most of them are stalled. They were running fine before, the tracker websites say they have plenty of seeders and leechers, but all I'm getting is "invalid data" and "connection broken".

It looks like I'm not the only user with this problem -- is anything being done about it?

The connection broken problems are being looked into, but they are not that easy to reproduce, and they are probably KDE problems.

If any of the trackers are HTTPS, thats one potential problem. Qt's ssl is somewhat broken these days.

It is probably not SSL, the problem was analyzed before in the thread:

The tracker returns invalid HTTP (no content-length field in the header), KIO sometimes accepts this, sometimes it doesn't (don't know why).

I have done some experiments with using Qt's QNetworkAccessManager, this doesn't accept it, and you get an error similar to connection to host is broken.

Not sure what I'm going to do. I could use the webseeding HTTP code, but that is less mature then KIO, and it needs SSL support.

A solution is being prepared, still need some testing, but this will be included in 3.2.2 as an experimental option which you can enable.

George wrote:A solution is being prepared, still need some testing, but this will be included in 3.2.2 as an experimental option which you can enable.

Thats good to hear. Have you had any luck talking to kde-devel about making kio_http work around this issue?

George wrote:A solution is being prepared, still need some testing, but this will be included in 3.2.2 as an experimental option which you can enable.

Is it in svn or not yet?

rangerGR wrote:

George wrote:A solution is being prepared, still need some testing, but this will be included in 3.2.2 as an experimental option which you can enable.

Is it in svn or not yet?

Not yet

It has been committed in revision 973256 (trunk only at the moment, still needs to be backported to stable)

Disabling KIO is done in Advanced Settings -> Miscellaneous

Proxy settings should keep on working.

The tracker announce message in the log has been slightly changed and now shows what is being used :

Doing tracker request to url (via QHttp) : http://tracker.com/announce?... (new way)
Doing tracker request to url (via KIO) : http://tracker.com/announce?... (old way)