Jump to content

µTorrent 1.9 alpha 15380


Firon

Recommended Posts

  • Replies 1.1k
  • Created
  • Last Reply

Top Posters In This Topic

I using D-Link DI-512 wireless router with D-Link DSL-500T router modem.

512kbps download and 256kbps upload, unlimited Streamyx broadband

I had no problem with Bitcomet, Vuze, Deluge, utorrent 1.8.1 and etc using global connection 300 and per torrent 290 settings.

Ever since i start using 1.9, my router keep disconnect once a while, and when it did disconnect, it will auto reconnect a few second later because of the "always on" setting.

But even after got one time disconnect, when I type ip address go into the router configuration page, after I type in username and password, it should go into router web configuration, but it stuck there nothing display. internet connection is also disconnect, didn't auto reconnect back like usual..

Closing firefox and retype the ip address will not even display login page to enter the username and password anymore. Only can be solved by close and open back power for my router.

I not sure whether it is too many connection make, so i try my luck on reduced global connection to 150 and per torrent 140.

After this everything back to normal and my router almost never happen ( only happen 1-2 times after few month time ever since I reduced the connection ) thing I say above.

Link to comment
Share on other sites

@zhong881209

That is probably caused by the router having a too small UDP pinhole table, and the way it handles an overflow is by crashing.

The reason why this is a new problem in uTorrent 1.9 is because it uses uTP (which is a transport on top of UDP), you can disable this by setting the bt.transp_disposition to 13. (13 means, allow incoming TCP and uTP connections, but only make outgoing TCP connections).

Link to comment
Share on other sites

@arvid

too small UDP pinhole table? what that?

and what is disabled by setting the bt.transp_disposition to 13?

what will happen to the to the control of the transfer rate? will it not kill my net connections even i not set limits after i change bt.transp_disposition to 13? on both DL and UL?

plus, i been noticing that now Utorrent seem to be "prefer" TCP ever since setting i set bt.transp_disposition to 13 for almost all Utorrent 1.8.x i connected.

Link to comment
Share on other sites

I've switched to 1.8.2 but I'm still getting this problem: From time to time torrents that are finished downloading but not complete (i.e. not all of the files are selected) will give me an "element not found" error. Seeing as how it (still) isn't on the fix list I assume this problem, among many others it seems, plagues the new alpha as well (correct me if I'm wrong).

Link to comment
Share on other sites

When the error occurs next time, be sure to check the Logger tab and copy the IO error log messages for us to see.

A possible workaround would be to disable the Windows cache override options in the disk cache preferences (that is, uncheck the "Disable Windows caching of disk writes/reads"). It's probably better for you to copy the error for the devs to see though.

Link to comment
Share on other sites

Err, here's the log as it stands now (■■■=censored):

[2009-02-12 14:04:41] NOTE: Settings file found in directory of executable; using that.

[2009-02-12 14:04:41] IPv6 is installed

[2009-02-12 23:41:55] Help file not found in settings directory, attempting to download

[2009-02-12 23:41:57] Could not download help file. Error: HTTP Error 404

[2009-02-12 23:42:05] Help file not found in settings directory, attempting to download

[2009-02-12 23:42:06] Could not download help file. Error: HTTP Error 404

[2009-02-13 00:10:52] ReadFile error: _____padding_file_9_if you see this file, please update to BitComet 0.85 or above____:■■■:■■■:■■■:■■■

[2009-02-13 03:00:05] ■■■: No longer have piece: 0

[2009-02-13 03:00:05] ■■■: No longer have piece: 2

[2009-02-13 03:00:05] ■■■: No longer have piece: 3

[2009-02-13 03:00:05] ■■■: No longer have piece: 8

[2009-02-13 03:00:05] ■■■: No longer have piece: 10

[2009-02-13 03:00:05] ■■■: No longer have piece: 15

[2009-02-13 03:00:05] ■■■: No longer have piece: 16

[2009-02-13 03:00:05] ■■■: No longer have piece: 17

[2009-02-13 03:00:12] ■■■: No longer have piece: 635

[2009-02-13 03:00:13] ■■■: No longer have piece: 661

[2009-02-13 03:01:04] ■■■: No longer have piece: 4948

[2009-02-13 03:01:04] ■■■: No longer have piece: 4949

[2009-02-13 06:09:19] ReadFile error: _____padding_file_10_if you see this file, please update to BitComet 0.85 or above____:■■■:■■■:■■■:■■■

[2009-02-13 12:11:58] ■■■: No longer have piece: 0

[2009-02-13 12:11:58] ■■■: No longer have piece: 2

[2009-02-13 12:11:58] ■■■: No longer have piece: 3

[2009-02-13 12:11:58] ■■■: No longer have piece: 8

[2009-02-13 12:11:58] ■■■: No longer have piece: 10

[2009-02-13 12:11:59] ■■■: No longer have piece: 15

[2009-02-13 12:11:59] ■■■: No longer have piece: 16

[2009-02-13 12:11:59] ■■■: No longer have piece: 17

[2009-02-13 12:12:05] ■■■: No longer have piece: 635

[2009-02-13 12:12:05] ■■■: No longer have piece: 661

[2009-02-13 12:12:55] ■■■: No longer have piece: 4948

[2009-02-13 12:12:55] ■■■: No longer have piece: 4949

[2009-02-13 19:04:34] ReadFile error: _____padding_file_10_if you see this file, please update to BitComet 0.85 or above____:■■■:■■■:■■■:■■■

[2009-02-13 19:51:25] ■■■: No longer have piece: 0

[2009-02-13 19:51:25] ■■■: No longer have piece: 2

[2009-02-13 19:51:25] ■■■: No longer have piece: 3

[2009-02-13 19:51:25] ■■■: No longer have piece: 8

[2009-02-13 19:51:25] ■■■: No longer have piece: 10

[2009-02-13 19:51:25] ■■■: No longer have piece: 15

[2009-02-13 19:51:25] ■■■: No longer have piece: 16

[2009-02-13 19:51:25] ■■■: No longer have piece: 17

[2009-02-13 19:51:35] ■■■: No longer have piece: 635

[2009-02-13 19:51:35] ■■■: No longer have piece: 661

[2009-02-13 19:52:22] ■■■: No longer have piece: 4948

[2009-02-13 19:52:22] ■■■: No longer have piece: 4949

In other words that's 3 times it's given me the "Element not found" error and 3 times I've had to force a recheck and restart the torrent (losing several pieces in the process, as you can see). I'd also like to point out that this problem isn't limited to these so called "padding files", it's just that in this torrent those were the ones I decided to skip (for obvious reasons); the same problem will occur regardless of the size or type of file as long as it's set to be skipped in a partially downloaded torrent.

P.S. On an unrelated note I'd also like to ask if there is some explanation for the help file 404.

Link to comment
Share on other sites

@zhong881209

Every time an outbound udp packet passes your NAT, it will remember the source IP,port and the destination IP,port for some period of time. This is so that if the destination IP responds, the NAT will be able to figure out who to forward the response to. If you send a lot of udp packets, your router may run out of space to store this information, and many router manufacturers decided that the best/most reasonable/most cost efficient way of dealing with this was to have the router crash.

Changing the transp_disposition will tell uTorrent which transports to use when it talks to peers. That particular value will make uTorrent not make outgoing uTP connections (which uses udp), but it will still make outgoing TCP connections (regular connections). It will also still accepting both uTP and TCP incoming connections.

Link to comment
Share on other sites

@arvid

If it is like this, wont this uTP technology will arise problems to many routers then?

By changing the transp_disposition, what is the advantage that i lost from not making outgoing uTP connections?

If i connected to a peer using uTP, i will receive data through uTP, but i will uploading data to it using TCP?

this mean that i cannot use setting "10 or 255" anymore?

Link to comment
Share on other sites

- Change: optimize torrent generator to move the largest file to the front of the torrent

When uploading TV series and new episode comes out there is a practice to add this new episode at the end of the torrent and replace old torrent with new one. This way people can download just the new episode and still seed all the other episodes. New behavior of the torrent generator reorders files by their size and thus breaks this practice. Please make it optional.

Link to comment
Share on other sites

It was originally sorted alphabetically for creation, and changed.

@chupakabra: At worst, the new file layout might cause a few extra edge pieces to have to be redownloaded if you simply add a new file to a group of files and recreate the .torrent for that batch. The practice isn't broken in the least.

Link to comment
Share on other sites

why i away get this message when i close utorrent 1.9 then open back

[2009-02-16 13:17:51] UDP port bind failed 0.0.0.0:41343: (10048) Only one usage of each socket address (protocol/network address/port) is normally permitted.

[2009-02-16 13:17:51] UDP port bind failed [::]:41343: (10048) Only one usage of each socket address (protocol/network address/port) is normally permitted.

did my setting wrong ??? pls help

Link to comment
Share on other sites

Hi,

I'm having a problem of having my internet connection virtually cut off for a few minutes while uTorrent starts up. I am unable to surf the web at all until uTorrent finishes it's initial startup connections. My router doesn't crash during this period though. Also, I know autoupdate is delayed, but it's been five days since the new build has come out, and autoupdate still isn't picking it up. I was using 1.8.2 for the longest time without any autoupdate notifications.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.


×
×
  • Create New...