EAGAIN error
- anarchogeek
- Private First Class
- Posts: 36
- Joined: Fri Jan 07, 2005 9:09 pm
EAGAIN error
Hi. I'm running a server on Windows XP (*crowd gasps at Happy Tanker's stupidity*). Anyway, it can only handle one client. It does this:
Player Happy Tanker Admin [1] removed at 2005-04-01 22:56:00: Write error EAGAIN
if more than one client tries to join. What's causing this? Any more information you need?
-Happy Tanker
Player Happy Tanker Admin [1] removed at 2005-04-01 22:56:00: Write error EAGAIN
if more than one client tries to join. What's causing this? Any more information you need?
-Happy Tanker
- wegstar
- Private First Class
- Posts: 127
- Joined: Sun Dec 26, 2004 4:33 am
- Location: Good ol' California
- Contact:
hmm.. If you stick too many flags on a map, you cannot spawn.. I wonder if this problem is related to that...
Formerly "nader"
---
Microsoft broke Volkswagen's world record: Volkswagen only made 22 million bugs!
-----
"Do not meddle in the affairs of cats, for they are subtle and will pee on your computer." -- Bruce Graham
---
Microsoft broke Volkswagen's world record: Volkswagen only made 22 million bugs!
-----
"Do not meddle in the affairs of cats, for they are subtle and will pee on your computer." -- Bruce Graham
- anarchogeek
- Private First Class
- Posts: 36
- Joined: Fri Jan 07, 2005 9:09 pm
Excellent. Thanks for the help. Just out of curiosity, why does this vary between operating systems? On Linux, I was able to insert over 200 flags of a particular type with ease, but on Windows I have this 40 limit. As examples...trepan wrote:+f good{40} is the breaking point on my machine.
you can use +f good{N}, just keep N reasonable.
BZLand running on Linux server. 50 Wings on map.
bzflag.norang.ca:5155
BZLand running on Windows server. 30 Wings on map.
69.205.201.251:5154
Anyway, it works great now. Thanks for all the help.
-Htanker
- anarchogeek
- Private First Class
- Posts: 36
- Joined: Fri Jan 07, 2005 9:09 pm
- anarchogeek
- Private First Class
- Posts: 36
- Joined: Fri Jan 07, 2005 9:09 pm
Well, we won't get anywhere without people whining about the issues .RPG wrote:I'm telling you, it's Windows. There has been a problem with BZFS and it's compatibility with Windows for a long time. The problem hasn't been tracked down yet, so for now BZFS will never be reliable on Windows.
Here's a partial debug from the server.
Player [8] accept() from 192.168.1.100:1811 on 1688
Player Happy Tanker 8 [8] has joined from x ═☺èzE at 2005-04-05 18:55:55 with to
ken ""
Player [9] accept() from 69.28.129.166:35259 on 1652
Player [9] removed at 2005-04-05 18:55:56: Disconnected
Player [9] accept() from 84.58.19.9:52517 on 1664
Player [9] removed at 2005-04-05 18:55:58: Disconnected
Player [9] accept() from 65.41.109.5:1310 on 1664
Player [10] accept() from 217.157.132.92:23426 on 1652
Player [11] accept() from 213.78.206.169:33956 on 1640
Player [11] removed at 2005-04-05 18:56:17: Disconnected
Player mx+b [9] has joined from ░τ¿☺èzE at 2005-04-05 18:56:20 with token ""
Player mx+b [9] removed at 2005-04-05 18:56:20: Write error EAGAIN
Player [9] accept() from 69.28.129.166:35292 on 1660
Player [9] removed at 2005-04-05 18:56:20: Disconnected
Player [10] removed at 2005-04-05 18:56:23: Disconnected
Player [9] accept() from 192.168.1.100:1825 on 1652
Player Happy Tanker [9] has joined from ╚≥¿☺èzE at 2005-04-05 18:56:32 with toke
n "1735611232"
Player Happy Tanker [0] removed at 2005-04-05 18:56:32: Ghost
Player [0] accept() from 69.28.129.166:35299 on 1716
Identify HAPPY TANKER
Player [0] removed at 2005-04-05 18:56:33: Disconnected
Player [0] accept() from 204.65.66.193:49874 on 1716
Player [10] accept() from 192.168.1.100:1833 on 1660
Player [11] accept() from 65.40.204.41:17799 on 1640
Player Grim [0] has joined from pª╟☺èzE at 2005-04-05 18:57:03 with token ""
Player Grim [0] removed at 2005-04-05 18:57:03: Write error EAGAIN
Player [0] accept() from 69.28.129.166:35323 on 1820
Player [0] removed at 2005-04-05 18:57:03: Disconnected
Player Happy Tanker 9 [10] has joined from ░τ¿☺èzE at 2005-04-05 18:57:05 with t
oken ""
Player [0] accept() from 69.28.129.166:35326 on 1628
Player [0] removed at 2005-04-05 18:57:05: Disconnected
Player [0] accept() from 80.139.102.177:3266 on 1820
Player davon [11] has joined from α²¿☺èzE at 2005-04-05 18:57:10 with token ""
Player davon [11] removed at 2005-04-05 18:57:10: Write error EAGAIN
Player [11] accept() from 69.28.129.166:35335 on 1632
Player [11] removed at 2005-04-05 18:57:10: Disconnected
Player the DENTIST7777 [0] has joined from pª╟☺èzE at 2005-04-05 18:57:12 with t
oken ""
Player the DENTIST7777 [0] removed at 2005-04-05 18:57:13: Write error EAGAIN
Even though it looks like it here, the problem is NOT always specific to remote clients. It often happens to me.
Last edited by anarchogeek on Wed Apr 06, 2005 1:36 am, edited 1 time in total.
- anarchogeek
- Private First Class
- Posts: 36
- Joined: Fri Jan 07, 2005 9:09 pm
Notice, also, that EAGAIN occurs only when someone has been accepted multiple times on the same connection (it appears that a list bot is logged on in the given player number every time someone attempts to logon to that same number). This is marked in blue in my table above.
I, therefore, believe that this WOULD NOT occur, were the map being served locally without bots in my face, and that this is the sole creation of the bots. This particular form of messup appears to be linked directly to operating system, nonexistant in on *nix machines and Macs.
I, therefore, believe that this WOULD NOT occur, were the map being served locally without bots in my face, and that this is the sole creation of the bots. This particular form of messup appears to be linked directly to operating system, nonexistant in on *nix machines and Macs.
as stated in another thread, windows XP has a connection limit. If you are going to use XP as a server, you will want to modfiy your settings ( your XP settings, it involves messing with windows files ). to allow for winsock to have more connections.
Or change to a version of windows that dosn't have the same limits ( 2000, or one of the 'server' Versions ).
Or change to a version of windows that dosn't have the same limits ( 2000, or one of the 'server' Versions ).
JeffM
- Tropican8
- Private First Class
- Posts: 312
- Joined: Fri Mar 18, 2005 11:51 pm
- Location: As close to the grove as you can get
Yes it was mentioned, but you didn't link a patch for it. I've been googling it all day, no luck. Do you have a link?JeffM2501 wrote:as stated in another thread, windows XP has a connection limit. If you are going to use XP as a server, you will want to modfiy your settings ( your XP settings, it involves messing with windows files ). to allow for winsock to have more connections.
The SP2 half-open packet issue to which you linked a hack for can produce the same error, but is clearly not the problem considering I'm not on SP2.