"Select Error" Driving me fucking insane.

[saqt]

About every 10 minutes it says "Select Error" where it says "Network OK" and then all the torrents stop and start up about 5 minutes later. I thought it was my router so i took out the router and am going directly to my cable modem now. It still keeps doing this. I have the windows xp firewall disabled and no other firewall. Please fucking tell me how to stop this from happening.

[okasvi]

would FUCKING help tell about your settings etc. :|

[saqt]

heres the program settings

I'm running windows xp sp2 home ed. I just applied that lvllord tcp crack or whatever, and rebooted and it still is doing this.

[okasvi]

ermm... 2000 connections/torrent... isnt that a bit too much?!?!

[saqt]

ermm... 2000 connections/torrent... isnt that a bit too much?!?!

i dont think it really matters....

[saqt]

http://d17.yousendit.com/F/0SYR3BU7UM66T2SMDINQ3RJGPG/screen.avi

theres a video of my utorrent doing the stupid select error thing.

[eva.02]

I'd try putting your connection settings back to default.

[Ultima]

I agree, you should probably try changing the connection settings to default and see how it goes.

On another note... do you really have to cross-post?

[moPP]

I have the exact same error, and I still have the default settings.

It happens when I have more than two or three torrents, both seeding and leeching.

[lament]

also, people haven't been using ports 6881-6889 for a couple of years now.

the reason being is that ISPs are throttling bandwidth on those ports, and even using those will get you banned on some sites.

try a high port like 50000.

[moPP]

It has nothing to do with the ports either, I've always used a high port (as in 655**), and it has nothing to do with the bandwidth being throttled either, because this bug is like a yo-yo.

NAT okay (downloading/uploading) -> Select error (no transfer whatsoever) -> NAT okay -> Select error .... and so on, every few seconds.

[saqt]

It has nothing to do with the ports either, I've always used a high port (as in 655**), and it has nothing to do with the bandwidth being throttled either, because this bug is like a yo-yo.

NAT okay (downloading/uploading) -> Select error (no transfer whatsoever) -> NAT okay -> Select error .... and so on, every few seconds.

Yup, exact same problem for me. I bought a new router today too and it still dosnt work.

[lament]

It has nothing to do with the ports either, I've always used a high port (as in 655**), and it has nothing to do with the bandwidth being throttled either, because this bug is like a yo-yo.

NAT okay (downloading/uploading) -> Select error (no transfer whatsoever) -> NAT okay -> Select error .... and so on, every few seconds.

i'm not saying it's related to the error - i was just pointing out that one shouldn't be using ports 6881-6889.

[Michael_C]

I'm having the same problem.

[silverfire]

You know, instead of complaining that you have problems, posting the options you're using, your ISP, and other details might help people find out what's going on.

[Michael_C]

These ports are open:

5438(TCP & UDP), 6969(TCP) & 6881-6889(TCP)

Here are my settings:

Debug info:

[static-]

don't forget your name, date of birth, social security number and the sex of your cat.

[etimbo]

Im also having this problem

I keep persevearing because while its working its great but as soon as that select error raises its ugly head speeds drop and come back and drop ..... you know same old.

Its happened on two system for me, only common things have been SP2, nod32 and our ISP. On my system ports have been forwarded, on the other upnp was used.

If you need any information for debugging or anything else, yell out and ill grab it.

Thanks for the effort of developing the client

[vurlix]

I think I just found out why select error is happening.. As a temporary workaround, try setting the global maximum number of connections to 30 and let me know if the error happens again.

[etimbo]

Giving it ago now. Lets hope i get some speedy 30 peers

So far so good.

[etimbo]

Fantastic

Set global to 30 and Network OK.

To test it out I put the global back up and watched the peers rise. As soon as it hit 50 I got a select error.

Dropped it back down to 30 and select error hasnt come back.

Thanks vurlix. Im happy to keep my peers low for now. Is it something easily fixed?

[vurlix]

Assuming that I'm right, and that keeping the number of connections low fixes the problem, then the fault lies with whatever program (antivirus, firewall, bandwidth monitor, etc) is intercepting µTorrent's network function calls -- they're assuming that the maximum number of connections polled at the same time with the "select" function is 64. However, Microsoft allows you to increase this to whatever number you want, and µTorrent does exactly that. We'll have to use a workaround if this is indeed what is happening..

[Michael_C]

I'm using Zonealarm, settings max global connections to 30 seemed to do the trick but it has a bad effect on the download speed. Since I'm behind a router anyway I've disabled Zonealarm until there is a fix. 8)

[etimbo]

Looks like you are right vurlix.

Even though i should be doing work Ive been watching whats happening when i get a select error.

It will gradually pick up peers until it gets around 63 and then it will pop up with a select error and all speeds drop to zero. It then starts to drop off peers until it gets back down to around 50 and network ok comes back and speeds return. This pattern happens even when I have quit nod32 and my firewall (outpost).

Ive set a max of 55 peers globally and it seems to be working fine now. Speed limited to some extent, but just fine.

[vurlix]

*Sigh* I was kinda hoping that the developers of such common/popular firewall software would actually have a clue, but I guess they're all morons if they can't properly handle well documented behavior of the API they are supposed to emulate. Pathetic.