* 2.4.18+O(1) tcp timewait zombies
@ 2002-05-03 14:53 Jason Baietto
0 siblings, 0 replies; only message in thread
From: Jason Baietto @ 2002-05-03 14:53 UTC (permalink / raw)
To: lkml
Hi all,
After upgrading from stock 2.4.17 to 2.4.18 (with O(1) scheduler
patch) I'm seeing some strange networking behavior. Basically,
upon exit rsh connections seem to go into TIME_WAIT, count down
to zero, and then stick around forever. For example:
compy$ rsh hyena echo hello < /dev/null
hello
compy$
This leaves a socket connnection in TIME_WAIT state:
tcp ... TIME_WAIT timewait (51.75/0/0)
However, the strange thing is that after the connection times
out, it sticks around. I've got hundreds of these connections
open that look like this:
tcp ... TIME_WAIT timewait (0.00/0/0)
And never seem to go away. Eventually, this causes me to
get this message whenever I try to do an new rsh:
socket: All ports in use
Can anyone offer me any advice on how to debug this?
Take care,
Jason
--
Jason Baietto
jason.baietto@ccur.com
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2002-05-03 14:54 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-05-03 14:53 2.4.18+O(1) tcp timewait zombies Jason Baietto
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox