Code: Select all

**** failed : Unexpected end of data, some information may be lost.
Timeout occurred
Authentication to 65.212.204.98 : failure
Timeout occurred
Authentication to 74.118.93.99 : failure
Timeout occurred
Authentication to 65.75.95.100 : failure
Timeout occurred
Authentication to 81.8.231.10 : failure
Timeout occurred
Authentication to 69.146.33.97 : failure
Timeout occurred
Authentication to 201.78.189.166 : failure
Timeout occurred
Authentication to 201.235.153.245 : failure
Timeout occurred
Authentication to 202.71.165.22 : failure
Timeout occurred
Authentication to 80.251.207.13 : failure
Timeout occurred
Authentication to 83.29.64.205 : failure
Timeout occurred
Authentication to 89.120.192.224 : failure
Connection closed
Stalled for too long, time to get some fresh blood
DHT: Doing announce
Doing tracker request to url : http://tracker.torrentbox.com:2710/announce?peer_id=-KT21DV-433912057938&port=9008&uploaded=0&downloaded=0&left=219874360&compact=1&numwant=100&key=1847864144&info_hash=g%fd%26%dd%fa%a6%a7%b8%13%d6q!e%bc%9a%f8%95%c4%97L
Doing tracker request to url : http://tracker.torrentbox.com:2710/announce?peer_id=-KT21DV-433912057938&port=9008&uploaded=0&downloaded=0&left=219874360&compact=1&numwant=0&key=1847864144&event=stopped&info_hash=g%fd%26%dd%fa%a6%a7%b8%13%d6q!e%bc%9a%f8%95%c4%97L
Saving 4 chunk downloads
Stopping socketmonitor thread
Starting download
Loading 4 active chunk downloads
Loading chunk 0
Loading chunk 4
Loading chunk 2606
Loading chunk 2798
DHT: Doing announce
Doing tracker request to url : http://tracker.torrentbox.com:2710/announce?peer_id=-KT21DV-433912057938&port=9008&uploaded=0&downloaded=0&left=219874360&compact=1&numwant=100&key=1847864144&event=started&info_hash=g%fd%26%dd%fa%a6%a7%b8%13%d6q!e%bc%9a%f8%95%c4%97L
Error : Timeout on server
Connection was to tracker.torrentbox.com at port 2710
Selected tracker http://tracker.torrentbox.com:2710/announce. (tier = 1)
Switching to tracker http://tracker.torrentbox.com:2710/announce.
Doing tracker request to url : http://tracker.torrentbox.com:2710/announce.?peer_id=-KT21DV-433912057938&port=9008&uploaded=0&downloaded=0&left=219874360&compact=1&numwant=100&key=1847864144&event=started&info_hash=g%fd%26%dd%fa%a6%a7%b8%13%d6q!e%bc%9a%f8%95%c4%97L
Doing scrape request to url : http://tracker.torrentbox.com:2710/scrape.?infohash=g%fd%26%dd%fa%a6%a7%b8%13%d6q!e%bc%9a%f8%95%c4%97L
Initiating connection to 213.202.171.159
Initiating connection to 67.68.255.202
Initiating connection to 69.232.205.210
Initiating connection to 212.1.151.16
Initiating connection to 87.203.141.255
Initiating connection to 68.126.129.241
Initiating connection to 70.36.251.61
Initiating connection to 65.23.224.87
Initiating connection to 62.128.241.53
Initiating connection to 202.156.54.17
Initiating connection to 74.106.28.245
Initiating connection to 84.9.171.80
Initiating connection to 70.176.167.179
Initiating connection to 212.14.14.20
Initiating connection to 86.61.18.228
Initiating connection to 69.235.149.180
Initiating connection to 87.197.143.95
Initiating connection to 66.137.227.139
Initiating connection to 85.138.23.14
Initiating connection to 69.15.133.89
Initiating connection to 68.236.148.148
Authentication to 69.232.205.210 : failure
Authentication to 68.126.129.241 : failure
Initiating connection to 86.88.97.122
Initiating connection to 71.193.252.173
Authentication to 69.15.133.89 : failure
Authentication to 212.14.14.20 : failure
Initiating connection to 89.4.45.139
Initiating connection to 90.227.213.205
Authentication to 66.137.227.139 : failure
Initiating connection to 67.48.76.37
Authentication to 67.68.255.202 : failure
Authentication to 67.48.76.37 : failure
Initiating connection to 134.153.103.208
Initiating connection to 70.88.23.38
Authentication to 85.138.23.14 : ok
Starting socketmonitor thread
Authentication to 86.61.18.228 : ok
Authentication to 71.193.252.173 : failure
Initiating connection to 204.116.209.144
Initiating connection to 217.155.41.59
Initiating connection to 71.132.227.6
Authentication to 217.155.41.59 : failure
Initiating connection to 24.78.114.92
Authentication to 71.132.227.6 : failure
Authentication to 90.227.213.205 : ok
Initiating connection to 85.167.169.201
Initiating connection to 68.146.104.129
Authentication to 85.167.169.201 : failure
Initiating connection to 89.161.8.33
DHT: AnnounceTask done
Authentication to 89.4.45.139 : ok
Initiating connection to 82.182.100.109
Authentication to 68.146.104.129 : ok
Initiating connection to 83.19.205.50
Authentication to 83.19.205.50 : failure
Initiating connection to 70.16.249.221
Authentication to 70.16.249.221 : ok
Initiating connection to 81.168.248.42
Scrape failed : Unexpected end of data, some information may be lost.
Authentication to 82.182.100.109 : ok
Initiating connection to 68.94.57.51
Authentication to 68.94.57.51 : failure
Initiating connection to 72.136.212.87
Timeout occurred
Authentication to 213.202.171.159 : failure
Timeout occurred
Authentication to 212.1.151.16 : failure
Timeout occurred
Authentication to 87.203.141.255 : failure
Timeout occurred
Authentication to 70.36.251.61 : failure
Timeout occurred
Authentication to 65.23.224.87 : failure
Timeout occurred
Authentication to 62.128.241.53 : failure
Timeout occurred
Authentication to 202.156.54.17 : failure
Timeout occurred
Authentication to 74.106.28.245 : failure
Timeout occurred
Authentication to 84.9.171.80 : failure
Timeout occurred
Authentication to 70.176.167.179 : failure
Timeout occurred
Authentication to 69.235.149.180 : failure
Timeout occurred
Authentication to 87.197.143.95 : failure
Timeout occurred
Authentication to 68.236.148.148 : failure
Initiating connection to 81.155.37.67
Initiating connection to 24.226.60.99
Initiating connection to 211.28.122.134
Initiating connection to 71.164.129.227
Initiating connection to 80.202.21.152
Initiating connection to 66.98.90.98
Initiating connection to 81.8.231.10
Initiating connection to 71.35.237.223
Initiating connection to 71.116.136.254
Timeout occurred
Authentication to 86.88.97.122 : failure
Authentication to 71.164.129.227 : failure
Authentication to 80.202.21.152 : failure
Authentication to 81.155.37.67 : failure
Timeout occurred
Authentication to 134.153.103.208 : failure
Timeout occurred
Authentication to 70.88.23.38 : failure
Timeout occurred
Authentication to 204.116.209.144 : failure
Authentication to 72.136.212.87 : failure
Timeout occurred
Authentication to 24.78.114.92 : failure
Timeout occurred
Authentication to 89.161.8.33 : failure
Authentication to 66.98.90.98 : ok
Timeout occurred
Authentication to 81.168.248.42 : failure
Timeout occurred
Authentication to 24.226.60.99 : failure
Timeout occurred
Authentication to 211.28.122.134 : failure
Timeout occurred
Authentication to 81.8.231.10 : failure
Timeout occurred
Authentication to 71.35.237.223 : failure
Timeout occurred
Authentication to 71.116.136.254 : failure
Authentication(S) to 68.151.48.212 : ok
Connection closed
                                                                           

is it normal to have alot of authenticaiton failure?
currently i've set to encryption mode with NO unencrypted connection allowed

after 5 minutes of starting single torrent download with 3449 leech and 1637 seeders
i only manage to connect to 8 peers.

other torrent client like azureus and utorrent can connect o 200 peers under 5 minutes

from time to time since ktorrent 2.0.1 till the latest svn i've tested ktorrent to see the performance of it and the max peers i got from ktorrent from all the test is less than 100 peers (which eventually decreased to less than 10 after 1 hours or so downloads)

and that situation only happens once with ktorrent 2.0.2.

now it decreased to 6 peers as i type...

First try to update your version to 2.0.3

Most people don't run encryption, and if you do not allow unencrypted connections, you cannot to those peers.

The upgrade-instruction doesn't answer the original question, and I'm also interested in the answer

What exactaly are the possible causes for this "authentication failure" message?

I made some tests with a friend who used ktorrent 2.0.x as well as azureus, I was using the latest SVN verison of ktorrent. We enforced encrypted connections. With both clients (KT/AZ) the connection could be established sometimes, sometimes not (authentication failures). It also happend that the download was stalled for hours, and suddenly the download started with none of us doing anything.

What could be the reason behind this?

Regards, Christian

chrschn wrote:The upgrade-instruction doesn't answer the original question, and I'm also interested in the answer

What exactaly are the possible causes for this "authentication failure" message?

There are many reasons :
- The peer is not online
- The peer has no more room to add a new connection
- We try to connect for a torrent the peer is no longer sharing
- We try to connect encrypted, the peer does not support this
- The peer sends something back which is not a valid handshake
...

I made some tests with a friend who used ktorrent 2.0.x as well as azureus, I was using the latest SVN verison of ktorrent. We enforced encrypted connections. With both clients (KT/AZ) the connection could be established sometimes, sometimes not (authentication failures).

That's normal, even when you accept non encrypted connections there are allways going to be authentication failures. If you limit yourself to encrypted only, you will get even more failures.

It also happend that the download was stalled for hours, and suddenly the download started with none of us doing anything.

What could be the reason behind this?

Regards, Christian

If everybody chokes you and suddenly one guy decides to unchoke you an hour later. To how many peers where you connected ?

George wrote:If everybody chokes you and suddenly one guy decides to unchoke you an hour later. To how many peers where you connected ?

Only me and my friend, on a private tracker, with no other torrents than our test-torrent in the queue and no other peers on this tracker.

Would it be possible to log some more sophisticated messages than "authentication failure"? To me "authentication" seems to be an indication to a security-related problem, no general connection problem (host down).

When encryption is completely disabled, do I also get these messages?