I get the error:
"connection to host X is broken." in tracker status.

It's a private tracker, so I can't post the log here, but I can mail if you leave me an address.

I do see this in the log:

Code: Select all

Authentication(S) to <IP> : ok
Error : Connection to host <host> is broken.


One thing that stands out is:

Code: Select all

doing tracker request to url : http://host:port/77ad0fb1968b96987511f353be6e8b7b/announce?peer_id=-KT32B1-SvtWuOspswmc&port=57882&uploaded=0&downloaded=0&left=6903824384&compact=1&numwant=100&key=9173874&event=started&info_hash=y_F��������m                                         
��7���                                                                         


neuron wrote:I get the error:
"connection to host X is broken." in tracker status.

It's a private tracker, so I can't post the log here, but I can mail if you leave me an address.

I do see this in the log:

Code: Select all

Authentication(S) to <IP> : ok
Error : Connection to host <host> is broken.


One thing that stands out is:

Code: Select all

doing tracker request to url : http://host:port/77ad0fb1968b96987511f353be6e8b7b/announce?peer_id=-KT32B1-SvtWuOspswmc&port=57882&uploaded=0&downloaded=0&left=6903824384&compact=1&numwant=100&key=9173874&event=started&info_hash=y_F��������m                                         
��7���                                                                         


That's probably a tracker problem

I did go on their irc and ask about it, and nobody else was having issues, I'll let you know if I can repeat it.

this is definitely ktorrent, I just tried starting a torrent from the same tracker in deluge, and it connected and got seeds and peers instantly. While ktorrent only "finds" the seeds connecting to me (I'm guessing here, but it has 4 atm).

Note that on the torrent that I left on from earlier there are now loads of peers and seeds, and the connection error has disapeared. No clue why, does something diffferently when it starts seeding? (not sure it happened when it started seeding either).

//edit, if needed I can try to get you an invite to fix this.
and the downloading torrent is saying tracker status : ok now, but it took it a good while. And deluge instantly got peers and seeders while ktorrent didn't.

neuron wrote:this is definitely ktorrent, I just tried starting a torrent from the same tracker in deluge, and it connected and got seeds and peers instantly. While ktorrent only "finds" the seeds connecting to me (I'm guessing here, but it has 4 atm).

Note that on the torrent that I left on from earlier there are now loads of peers and seeds, and the connection error has disapeared. No clue why, does something diffferently when it starts seeding? (not sure it happened when it started seeding either).

//edit, if needed I can try to get you an invite to fix this.
and the downloading torrent is saying tracker status : ok now, but it took it a good while. And deluge instantly got peers and seeders while ktorrent didn't.

Probably just the HTTP server dropping connections for some reason.

it has to be khttp or ktorrent, deluge picks up all seeds and peers within a second, and ktorrent needs ages to get the seed/peer list from the tracker.

I'm having the same issue with a private tracker right now after update to kde 4.2. The tracker actually seems to be working and I can download and upload, find seeders, leechers and get credit for my uploading. First I figured it had something to do with a recent switch in locales on my behalf (from iso-8859 to utf-8), as I too got all those funny chars in my info_hash string.

I have the same problem on Arch Linux with Ktorrent 3.2.0 and KDE 4.2.1.
It occurs with 15+ torrents on 3 different private trackers.

Deluge handles my 2 test torrents fine (which break in KT)
Also, sometimes a torrent will work early but break on a later update.
Here's an example of a dysfunctional update

Code: Select all

Doing tracker request to url : http://www.example.com:2710/mypasskey/announce?peer_id=-KT3200-ClbAjm6OBWbn&port=54754&uploaded=1590497&downloaded=0&left=0&compact=1&numwant=100&key=1155701356&info_hash=D�C]���o3[m^����
Error : Connection to host www.example.com is broken.
Selected tracker http://www.example.com:2710/mypasskey/announce (tier = 1)

I just recently moved from 2.8 (on Ubuntu8.04) which handled everything fine.

Thanks

I'm not sure this is the same problem, but I was seeing the same kinds of tracker status errors, but it seems I had the number of connections set so high even kio couldn't open new connections. I messed with ulimit a little and fiddled with ktorrent's max connections and things started working again.

it isn't, I had this problem on one specific tracker, never on the others I use, and it'd screw up even if it was the first torrent I started.

Yup, it's not a connections threshold issue for me either. It ONLY appears on private trackers.

Hmm, my problem seems to be back. I was hoping it was just a connection issue. And it does seem to only happen on private trackers.

Tomasu, which KDE version are you using ?

I did a google search on KIO + connection to host broken and found this bug :

http://bugs.kde.org/179934

George wrote:Tomasu, which KDE version are you using ?

I did a google search on KIO + connection to host broken and found this bug :

http://bugs.kde.org/179934

Nothing two months old. Been using KDE SVN for a while now. I try to keep it somewhat up to date.

Any ideas of what part of the request/response trips it up?