From: Herve Eychenne <rv@wallfire.org>
To: Jens Hektor <hektor@rz.rwth-aachen.de>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: System with really big statetable crashing while doing "cat /proc/net/ip_conntrack | wc -l"
Date: Fri, 23 Apr 2004 18:31:30 +0200 [thread overview]
Message-ID: <20040423163130.GA1210@eychenne.org> (raw)
In-Reply-To: <40875ECE.1000405@rz.rwth-aachen.de>
On Thu, Apr 22, 2004 at 07:57:34AM +0200, Jens Hektor wrote:
Hi,
> we are running a production packetfilter based on Fedora Core-1
> actual vanilla 2.4.22-1.2179.nptl-smp.
> This packetfilter is in front of two class-B's and it has a big
> statetable, really. We guess that it's about 200k entries.
> So we only can guess for if doing
> cat /proc/net/ip_conntrack | wc -l
> the system reproducably crashes.
> We had the same effect on non-smp and 2.6 version of Fedora kernels
> and I guess that the same might happen with the vanilla kernel.
> Is this known, has anyone ever seen this?
Yes, alas! See
http://lists.netfilter.org/pipermail/netfilter-devel/2003-December/013557.html
But is wasn't reproduced since then because we didn't dare to touch
/proc/net/ip_conntrack after that ;-/, as it is a production machine...
No oops trace either, as we had to reboot it as soon as possible for
the same reason.
And let me tell you that tftp was absolutely not loaded, so it cannot
be the root of our problem.
Herve
--
_
(°= Hervé Eychenne
//)
v_/_ WallFire project: http://www.wallfire.org/
next prev parent reply other threads:[~2004-04-23 16:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-22 5:57 System with really big statetable crashing while doing "cat /proc/net/ip_conntrack | wc -l" Jens Hektor
2004-04-22 22:59 ` Phil Oester
2004-04-23 11:21 ` Chris Wilson
2004-04-23 16:31 ` Herve Eychenne [this message]
2004-04-23 16:50 ` Chris Wilson
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=20040423163130.GA1210@eychenne.org \
--to=rv@wallfire.org \
--cc=hektor@rz.rwth-aachen.de \
--cc=netfilter-devel@lists.netfilter.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.