BitTorrent issues

[alexoren]

I am downloading a torrent and noticed some issues:

1) The tracker summary from isohunt says:
Trackers: (aggregated from BitTorrent sites everywhere for reliability and speed)
Tracker up, last checked 0.7 hours ago 11 seeds, 42 leechers, 10 downloads http://vip.tracker.prq.to:80/announce
Tracker up, last checked 0.3 hours ago 10 seeds, 46 leechers, 10 downloads http://tracker.publicbt.org:80/announce
Tracker up, last checked 3.8 hours ago 9 seeds, 36 leechers, 3 downloads Original, primary tracker http://tracker.openbittorrent.com:80/announce
Tracker up, last checked 3.6 hours ago 3 seeds, 17 leechers, 1 downloads http://91.209.127.28:80/announce
Tracker down, last changed 6.1 hours ago 3 seeds, 14 leechers, 33 downloads http://tracker.bitreactor.to:2710/announce
Tracker down, last changed 5.8 hours ago 3 seeds, 5 leechers, 2 downloads http://tracker.torrentbay.to:6969/announce
Tracker up, last checked 0.1 hours ago 2 seeds, 13 leechers, 0 downloads http://bt1.the9.com:6969/announce
Tracker down, last changed 4.2 hours ago 1 seeds, 5 leechers, 0 downloads http://pirates-united.org:6969/announce
Tracker up, last checked 3.7 hours ago 0 seeds, 2 leechers, 0 downloads http://bt.rghost.net:80/announce

But Shareaza shows a very different state:


How can I tell Shareaza to check the other trackers?


Also, there are a lot of errors in the log.
The most common one is: Handshake with a.b.c.d failed due to invalid data on the wire.
It appears about every 5 seconds. In the last 7 hours, it happened for over 100 unique IP addresses.

What's the deal?


Other errors (less common):
BitTorrent connection to a.b.c.d was dropped.
BitTorrent coupling with a.b.c.d not accepted, a connection to this client already exists.
BitTorrent coupling with a.b.c.d was dropped.
BitTorrent handshake with a.b.c.d was dropped.
Closing BitTorrent coupling with a.b.c.d due to lack of traffic.
Closing connection to neighbour a.b.c.d due to lack of traffic.
Closing upload connection a.b.c.d due to lack of traffic.
Handshake with a.b.c.d failed due to invalid data on the wire.
Neighbour a.b.c.d dropped the connection unexpectedly.
Received a malformatted query hit packet from a.b.c.d, ignoring.
Refusing upload of "xxx" to a.b.c.d (LimeWire/5.5.8), too many concurrent from host.
Rejecting BitTorrent connection from a.b.c.d, network core overloaded.
Timed out connecting to a.b.c.d.
Timed out connecting to BitTorrent client a.b.c.d.
Timed out handshaking with a.b.c.d.
Timed out handshaking with BitTorrent client a.b.c.d.
Timed out waiting for request from upload host a.b.c.d.

Thanks.

[alexoren]

Guys, an explanation on what is going on will be much appreciated!

[old_death]

[ailurophobe]

Well, you can switch "tracker mode" to "multi-tracker" then IF the tracker you connected to supports it, Shareaza should query other trackers (or not).

Not sure about "Invalid data on the wire", but the others seem normal. Are you certain it happens at 5 second intervals? Do other protocols have problems every 5 seconds?

[brov]

Invalid data on the wire is simply because others are trying to establish an encrypted connection. So consider it "normal".

[alexoren]

[alexoren]

Clarification of the above post:
Nothing that I posted was meant as criticism of the program or the programmers, just a sincere wish for some BT features to be added, so I will be able to finally ditch uTorrent.

Thank you.

[raspopov]

[siavoshkc]

[alexoren]

It would be nice to know the common cases for these errors/warnings/notifications.

Broadly:
- Normal (possibly uncommon) protocol result
- Protocol extensions not implemented by Shareaza
- Should not happen (bug in Shareaza or in peer)
etc.