From: Evan Borgstrom <evan@fatbox.ca>
To: netfilter@vger.kernel.org
Subject: Re: conntrackd: segfault at ignore_pool.c:37
Date: Wed, 02 Jul 2008 02:15:07 -0400 [thread overview]
Message-ID: <486B1CEB.8090800@fatbox.ca> (raw)
In-Reply-To: <486B144A.8070707@fatbox.ca>
> Both nodes are set with CacheWriteThrough on. When I run Sync in FTFW
> mode the segfault usually takes a little while to occur. If I switch to
> NOTRACK or ALARM mode the segfault happens almost immediately.
>
> In all instances the segfault looks the same and happens at the same
> point at ignore_pool.c.
Go figure... after spending awhile trying to solve this before I sent
the first message, I finally got it within 5 minutes of sending it.
On the node that was having this issue the nf_conntrack_ipv4 module was
not loaded. Once I loaded that module everything is up and running and
there hasn't been a segfault in about 45 minutes.
-Evan
--
Evan Borgstrom <evan@fatbox.ca>
FatBox Inc.
255 Richmond St East, Suite 1213
Toronto, Ontario, M5A 4T7
t:416.833.3763 | f:888.829.5963
msn: evan@fatbox.ca | aim: evan@fatbox.ca
prev parent reply other threads:[~2008-07-02 6:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-02 5:38 conntrackd: segfault at ignore_pool.c:37 Evan Borgstrom
2008-07-02 6:15 ` Evan Borgstrom [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=486B1CEB.8090800@fatbox.ca \
--to=evan@fatbox.ca \
--cc=netfilter@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 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.