mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg Stark <gsstark@mit.edu>
To: Martin Josefsson <gandalf@wlug.westbo.se>
Cc: Greg Stark <gsstark@mit.edu>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.20-ac2 Memory Leak?
Date: 18 Mar 2003 19:05:11 -0500	[thread overview]
Message-ID: <87u1e09q6g.fsf@stark.dyndns.tv> (raw)
In-Reply-To: <1048031585.748.83.camel@tux.rsn.bth.se>

Martin Josefsson <gandalf@wlug.westbo.se> writes:

> On Wed, 2003-03-19 at 00:46, Greg Stark wrote:
> > Martin Josefsson <gandalf@wlug.westbo.se> writes:
> > 
> > > This can be the source of your problems, connections can get very long
> > > timeouts and stay in ip_conntrack.
> > 
> > Is there a way to list the connections and confirm this is the problem?
> > It seems it would require an awful lot of connections to consume megabytes of
> > memory.
> 
> cat /proc/net/ip_conntrack
> 
> The third field is the timeout in seconds.
> The fourth field is the state of the connection, if it's TIME_WAIT with
> a large timeout then it's the list handling bug. (iirc it was TIME_WAIT
> that showed the problem...)

Nope, a total of 16 entries in ip_conntrack, one of which is in TIME_WAIT with
a timeout of 2m.



> The default tcp timeout is 5 days for esatblished connections.
> 
> There's a patch in patch-o-matic that enables you to tune the timeouts
> without having to edit the source. Instructions on how to get
> patch-o-matic are availiable on http://www.netfilter.org

Thanks.

-- 
greg


  reply	other threads:[~2003-03-19  0:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-18 23:17 Gregory Stark
2003-03-18 23:28 ` Martin Josefsson
2003-03-18 23:46   ` Greg Stark
2003-03-18 23:53     ` Martin Josefsson
2003-03-19  0:05       ` Greg Stark [this message]
2003-03-19 14:55   ` Greg Stark

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=87u1e09q6g.fsf@stark.dyndns.tv \
    --to=gsstark@mit.edu \
    --cc=gandalf@wlug.westbo.se \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®