Inactive will not time out

[markpc]

Over the past 2 days i have noticed that inactive seeds/peers will not timeout. The advanced option list is is untouched apart from the half open (which does not make any difference) the peer disconnect inactive is true, peer disconnect interval set to 300. I currently have a peer at 1hour 20 mins and counting. what is going on? Please help.

[DreadWingKnight]

Is the swarm for that torrent large or small?

[markpc]

seeds 5 peers 21

[markpc]

The peer finally stopped at an 1 1/2 hours but instantly restarted counting inactive and did nothing.

[dAbReAkA]

it wont timeout if the swarm is smaller than the maximum allowed connections per torrent..

[markpc]

Thanx

[Switeck]

Yet another inactive peer mystery!

I'm seeding the torrent in question...

This peer 87.103.x.x (which is also running µTorrent 1.7.5) is at 36.1%, has pieces of the torrent spread across-the-board (meaning it's not downloading JUST a couple files in the torrent), has a debug code of "9| -1", reports no download speed, has Flags of XE, and at some point I supposedly uploaded 215 MB to it.

...YET, it is idle for over an hour at a time now and accepting/doing nothing.

It shouldn't disconnect simply because I have not exceeded connection max per torrent.

µTorrent's logs give only this as a clue as to what's wrong:

[05:53:29] 87.103.x.x : [µTorrent 1.7.5 ]: Got Request while choked: 786:540672->16384

[05:56:35] 87.103.x.x : [µTorrent 1.7.5 ]: Got Request while choked: 786:622592->16384

[05:58:41] 87.103.x.x : [µTorrent 1.7.5 ]: Got Request while choked: 786:671744->16384

[05:59:49] 87.103.x.x : [µTorrent 1.7.5 ]: Got Request while choked: 786:835584->16384

[06:05:39] 87.103.x.x : [µTorrent 1.7.5 ]: Got Request while choked: 786:966656->16384

[06:05:39] 87.103.x.x : [µTorrent 1.7.5 ]: Got Request while choked: 786:966656->16384

[06:15:41] 87.103.x.x : [µTorrent 1.7.5 ]: Got Request while choked: 786:1392640->16384

[07:33:06] 87.103.x.x : [µTorrent 1.7.5 ]: Got Request while choked: 786:2031616->16384

[07:33:07] 87.103.x.x : [µTorrent 1.7.5 ]: Got Request while choked: 786:2048000->16384

[07:33:07] 87.103.x.x : [µTorrent 1.7.5 ]: Got Request while choked: 786:2064384->16384

[07:34:28] 87.103.x.x : [µTorrent 1.7.5 ]: Got Request while choked: 786:2113536->16384

[07:41:48] 87.103.x.x : [µTorrent 1.7.5 ]: Got Request while choked: 786:2392064->16384

[08:49:41] 87.103.x.x : [µTorrent 1.7.5 ]: Disconnect: Peer error: Error 10054

[08:50:48] 87.103.x.x : Connecting: port 56010 source: TIX

[08:50:52] 87.103.x.x : [µTorrent/1.7.5.0]: Encrypted handshake completed

Note: The disconnect was manually done by me using TCP View. I was attempting to see if the connection would correct itself on reconnect.

Also note the extremely long time between request intervals.

Why is it never unchoking?

Even when I set my upload slots higher than the total peers on the torrent, peer 87.103.x.x never gets an upload slot OR optimistic upload slot -- this despite the debug level for that torrent being 0|0|12, meaning up to 12 upload slots are allowed on that torrent!

I suspect that this slow ADSL line in Russia (did a WHOIS on it) is throttled in some way/s by their ISP.

However µTorrent does not seem to be handling it very well.

[Switeck]

My follow-up to my previous post is the 87.103.x.x peer MAY have been using Scheduler...but even then the situation seems a little weird.

Anyone have some insight to this situation or seen similar behavior?