From: John Salmon <jsalmon@thesalmons.org>
To: linux-net@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: negative tcp_tw_count and other TIME_WAIT weirdness?
Date: Mon, 30 Jun 2003 17:25:16 -0700 [thread overview]
Message-ID: <200307010025.h610PGmX007656@river.fishnet> (raw)
I have several fairly busy servers reporting a negative value
for tcp_tw_count. For example:
bash-2.05a# cat /proc/net/sockstat
sockets: used 121
TCP: inuse 50 orphan 0 tw -65048 alloc 81 mem 26
UDP: inuse 15
RAW: inuse 1
FRAG: inuse 0 memory 0
bash-2.05a#
When I look at netstat -n, I see many (hundreds) connections
stuck in TIME_WAIT. They've been there for at least a few hours,
and probably much longer (days).
Is this expected behavior? A known bug?
FWIW, I'm using a RedHat kernel, 2.4.18-24.7.xsmp on a 2-processor Athlon
system. If this looks like a bug I'll try to reproduce it with
an unmodified kernel.
Thanks,
John Salmon
next reply other threads:[~2003-07-01 0:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-01 0:25 John Salmon [this message]
2003-07-01 8:21 ` negative tcp_tw_count and other TIME_WAIT weirdness? David S. Miller
2003-07-01 17:12 ` John Salmon
2003-07-01 17:15 ` Nivedita Singhvi
2003-07-01 21:22 ` John Salmon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200307010025.h610PGmX007656@river.fishnet \
--to=jsalmon@thesalmons.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).