From: KOVACS Krisztian <piglet@sch.bme.hu>
To: "Björn Reese" <ReeseB@minimax.de>
Cc: netfilter@lists.netfilter.org
Subject: Re: Server crash after LIST_DELETE in Log
Date: Wed, 24 Mar 2004 21:41:19 +0100 [thread overview]
Message-ID: <20040324204118.GA18860@sch.bme.hu> (raw)
In-Reply-To: <s061bfaf.021@odnw1.minimaxgmbh.de>
Hi,
On Wed, Mar 24, 2004 at 05:04:20PM +0100, Björn Reese wrote:
> I have a strange Problem with (I guess) the Netfilter. I have a Proxy-Server running, that is dual-homed with a transparent Squid on one Interface listening. After some time, the syslog lists these messages:
>
> Mar 24 15:36:18 Proxy kernel: LIST_DELETE: net/ipv4/netfilter/ip_conntrack_core.c:299 `&ct->tuplehash[IP_CT_DIR_REPLY]'(e96c0d64) not in &ip_conntrack_hash[hr].
> Mar 24 15:36:39 Proxy kernel: LIST_DELETE: net/ipv4/netfilter/ip_conntrack_core.c:299 `&ct->tuplehash[IP_CT_DIR_REPLY]'(dd67fd24) not in &ip_conntrack_hash[hr].
> Mar 24 15:36:55 Proxy kernel: LIST_DELETE: net/ipv4/netfilter/ip_conntrack_core.c:299 `&ct->tuplehash[IP_CT_DIR_REPLY]'(dc976864) not in &ip_conntrack_hash[hr].
>
> 5 seconds more...
> and the server freezes...
Although without your kernel config and exact iptables ruleset I cannot
be sure, but I think you've found the same bug as Jonathan Cooper (and a
few others). See the thread about the problem on netfilter-devel:
http://lists.netfilter.org/pipermail/netfilter-devel/2004-March/014532.html
Basically, you should try two things:
- check if using CONFIG_IP_NF_NAT_LOCAL (NAT of local connections)
solves the problem
- if i does, please try if Henrik's patch at
http://lists.netfilter.org/pipermail/netfilter-devel/2004-March/014616.html
solves your problem
To try the patch would be especially useful.
--
KOVACS Krisztian
prev parent reply other threads:[~2004-03-24 20:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-24 16:04 Server crash after LIST_DELETE in Log Björn Reese
2004-03-24 20:41 ` KOVACS Krisztian [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=20040324204118.GA18860@sch.bme.hu \
--to=piglet@sch.bme.hu \
--cc=ReeseB@minimax.de \
--cc=netfilter@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox