From: Willy Tarreau <w@1wt.eu>
To: Stephane Bakhos <nuitari@nuitari.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: Infinite listens for haproxy in /proc/net/tcp
Date: Fri, 3 Dec 2010 00:02:45 +0100 [thread overview]
Message-ID: <20101202230245.GA29279@1wt.eu> (raw)
In-Reply-To: <Pine.LNX.4.64.1012021313080.25944@anvil.nuitari.net>
Hi,
On Thu, Dec 02, 2010 at 01:18:36PM -0500, Stephane Bakhos wrote:
> This happens whether the file is read directly, or using netstat.
> It looks like haproxy has millions of LISTEN.
I think what you see are not LISTEN sockets but mostly TIME_WAIT.
> We've tried to see if there is a definitive count, but after 20 minutes of
> running cat /proc/net/tcp we gave up. This is an intermittent problem.
I've been used to experience this on systems which process connections
at higher rates than netstat can output them. Thus, during the time it
takes to netstat to output a given number of connections, new ones
manage to complete the list. I've not tested on 2.6.36 yet, but this
has basically always been the case for me for a very long time, and as
such, I only use ss to display connections. I've recently discovered
that some versions of netstat use netlink to dump the socket list, so
on such versions it would not be an issue.
> According to ss, there is about 5500 connections running on the system.
What normally counts is the rate at which they're refreshed.
Regards,
Willy
prev parent reply other threads:[~2010-12-02 23:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-02 18:18 PROBLEM: Infinite listens for haproxy in /proc/net/tcp Stephane Bakhos
2010-12-02 23:02 ` Willy Tarreau [this message]
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=20101202230245.GA29279@1wt.eu \
--to=w@1wt.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=nuitari@nuitari.net \
/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