1.8.1 Release Candidate 1 (build 12549)

[2008-08-30 12:51:15] NOTE: Settings file found in directory of executable; using that.

[2008-08-30 12:51:15] IPv6 is installed

[2008-08-30 12:51:26] ERROR! Detected halfopen count exceeds internal count 7 > 5

[2008-08-30 12:51:27] ERROR! Detected halfopen count exceeds internal count 6 > 2

[2008-08-30 12:51:28] ERROR! Detected halfopen count exceeds internal count 6 > 1

[2008-08-30 12:51:29] ERROR! Detected halfopen count exceeds internal count 6 > 0

[2008-08-30 12:51:30] ERROR! Detected halfopen count exceeds internal count 5 > 0

[2008-08-30 12:51:31] ERROR! Detected halfopen count exceeds internal count 5 > 0

[2008-08-30 12:51:32] ERROR! Detected halfopen count exceeds internal count 5 > 0

[2008-08-30 12:51:33] ERROR! Detected halfopen count exceeds internal count 5 > 0

[2008-08-30 12:51:34] ERROR! Detected halfopen count exceeds internal count 4 > 0

[2008-08-30 12:51:35] ERROR! Detected halfopen count exceeds internal count 4 > 0

[2008-08-30 12:51:36] ERROR! Detected halfopen count exceeds internal count 4 > 0

[2008-08-30 12:51:37] ERROR! Detected halfopen count exceeds internal count 4 > 0

[2008-08-30 12:51:38] ERROR! Detected halfopen count exceeds internal count 4 > 0

[2008-08-30 12:51:39] ERROR! Detected halfopen count exceeds internal count 4 > 0

[2008-08-30 12:51:40] ERROR! Detected halfopen count exceeds internal count 2 > 0

[2008-08-30 12:51:41] ERROR! Detected halfopen count exceeds internal count 1 > 0

[2008-08-30 12:51:42] ERROR! Detected halfopen count exceeds internal count 1 > 0

[2008-08-30 12:52:41] ERROR! Detected halfopen count exceeds internal count 3 > 2

[2008-08-30 12:52:42] ERROR! Detected halfopen count exceeds internal count 3 > 2

[2008-08-30 12:52:43] ERROR! Detected halfopen count exceeds internal count 3 > 2

[2008-08-30 12:52:44] ERROR! Detected halfopen count exceeds internal count 4 > 2

[2008-08-30 12:52:45] ERROR! Detected halfopen count exceeds internal count 4 > 2

[2008-08-30 12:52:46] ERROR! Detected halfopen count exceeds internal count 4 > 1

[2008-08-30 12:52:47] ERROR! Detected halfopen count exceeds internal count 4 > 1

[2008-08-30 12:52:48] ERROR! Detected halfopen count exceeds internal count 4 > 1

[2008-08-30 12:52:49] ERROR! Detected halfopen count exceeds internal count 4 > 1

[2008-08-30 12:52:50] ERROR! Detected halfopen count exceeds internal count 4 > 1

.....

[many more like this]

In About->Show Stats dialog is always written: (<-- UPD: this isn't true)

#half-open: 0 (0 connecting)

It's came with 12024 build. Default settings too (8 half-open connections).

Vista x64 SP1, UPnP settings in uTorrent are disabled, router have static port forwarding.

It is very difficult to connect the users of bitcomet .

Is that a problem? How are you basing this? I routinely get stuck on a BitComet-created or BitComet-centric torrent (damn you padding files)...

I have the same problem like 13xforever

i have Vista x86 SP1 and the latest beta buil 12024

Can't connect to open.tracker.thepiratebay.org -- many users are confirming issues so it is not an ISP issue. Can dev and/or mods look at connection tracking issue with open.tracker.thepiratebay.org? thanks.

Not related to any bittorrent client at all. This tracker is just down -> http://forum.utorrent.com/viewtopic.php?id=44936#p352948

I also get the "Detected halfopen count exceeds internal count" messages with build 12024.

Running Vista x86 SP1 with increased half-open limit to 100.

By the way: The default half-open connections in vista is 10 (But utorrent thinks it is 8?)

Here is the patch that I used

http://half-open.com/

tjobo

uTorrent does not try to reverse engineer tcpip.sys to find out the system default.

8 is just 80% of the minimum known limit.

Any explanation for all those halfopen count errors? Is it an implementation error?

can't you read ? :

- Fix: improved halfopen counting

so they probably touch it and broke it ...

There are now two counters (both shown in Help > Show Statistics). This comparison error message seems was intentionally left for debugging purposes.

Over 2500 handshakes, 2 half-open counts.....

half-open counts on that screen are not historic, they are that instant.

Hell, just looked again and realized, sorry....

Just a little update. After a couple of hours I've got this in About->Show Statistics:

#half-open: 2 (1 connecting)

So, it isn't true that it never open 'em.

That's nice, how do you turn it off? It's being going on for hours, and I bet it didn't stop for even a second.

can't you read ? :

- Fix: improved halfopen counting

so they probably touch it and broke it ...

Of course I read that, just curious

> Not related to any bittorrent client at all. This tracker is just down

How would you know if the tracker is working or not? Web browser check has nothing to do with tracker availability.

I still think its a client issue but no one wants to look at it!

Just because the developers aren't posting here often doesn't mean they aren't checking uTorrent as you requested. But possibly they didn't find an easy fix or couldn't localize the problem.

Can you do a wireshark log of just tracker traffic to the problematic trackers?

Switeck

There is nothing to wireshark - that server just stopped accepting connections on August 15..16

http://forum.utorrent.com/viewtopic.php?pid=355656#p355656

Ah, that might explain this:

Name Status Update In Seeds Peers Downloaded

http://open.tracker.thepiratebay.org/announce offline (timed out)

http://open.tracker.thepiratebay.org/announce.php Error 10061

http://tracker.thepiratebay.org/announce Error 10061

As apparently this affects one of my torrents too.

Fortunately it had other trackers.

The update tracker restriction has been relaxed when the announce fails. If the announce fails, you'll only have to wait 60 seconds to do manual update tracker again, instead of whatever the min interval actually was.

Thx for this improvement, that's better I think.

In fact, on many (semi)-private trackers, when a torrent is not seeded anymore, it disappears from the list of 'visible' tors !!

And this problem appears when a recent uploaded torrent is not seeding because the tracker announce fails (when the tracker is temporarily out of order e.g.) and doesn't see the initial seed.

A solution is to stop/replay the torrent many times but an update tracker can solve too.

Ah, that might explain this:

Name Status Update In Seeds Peers Downloaded

http://open.tracker.thepiratebay.org/announce offline (timed out)

http://open.tracker.thepiratebay.org/announce.php Error 10061

http://tracker.thepiratebay.org/announce Error 10061

And what is this supposed to explain?

first time that this error apears

Way to read the posts before yours.

lol i know

i read this forum almost all days but just to say one user more that have this problem