[311] in linux-net channel archive
Sockets/ports get al tied up
daemon@ATHENA.MIT.EDU (JAIME PIRNIE)
Fri May 12 13:13:25 1995
From: JAIME PIRNIE <JAIME@mailgate.diamondmm.com>
To: "linux-net@vger.rutgers.edu" <linux-net@vger.rutgers.edu>
Cc: James Cameron <cameron@sna.dec.com>, siegl <siegl@risc.uni-linz.ac.at>,
Nick Trown <trown@ecst.csuchico.edu>
Date: Fri, 12 May 95 08:53:00 PDT
Hello.. I was told that this is the place to report bugs with Linux
networking. I am trying to run a Netrek game server. I am using kernel
v1.2.6. If you are unfamiliar with Netrek, its a 16 player graphical
shoot'em up game that uses TCP, along with UDP. The way it works is this..
There is a program called newstartd. This listens on port 2592 for the
incoming client to play the game. Newstartd's only job is to listen for the
client on port 2592 and pass it off to ntserv. Once a player comes in,
newstartd passes the user off to a program called ntserv. This is the
program that the user plays through, on its own unique port #. The only
common port #, is 2592, used to the initial connect. What we are
experiencing is that after some time of heavy play, the port 2592 will not
accept connections. It seems that the port locks up or something. Then
after some time, it starts working again. Everything in the < > is my
comments. If there is -anything- I can do to help the troubleshooting
process out, please let me know. I have been banging my head on this with
three people that help maintain the server code, for about a week. Thank
you for your time.
-Jaime
This is the errors that comes up in the log file for newstartd:
-------------------------------------------------------------
<The server works perfectly for a few hours before any of this happens>
accept error!reporterror: unknown: 104
No one calling!
Possible Problem
<then it tries to listen in on 2592 again, nobody is able
to connect at this point>
I cant bind to the socket!
Error: 98
Error: 98
Error: 98 for about 50-80 times...
<people are able to connect again>
<then after some time, it starts working again, but
with a different error, every time someone connects>
<It prints these four lines every time somebody connects>
<Everything works fine at this point>
<user connects>
accept error!EBADF!
No one calling!
Possible problem!
listening on port 2592, connection will start ./ntserv "ntserv"
<user connects>
accept error!EBADF!
No one calling!
Possible problem!
listening on port 2592, connection will start ./ntserv "ntserv"
