From: Bernhard Schmidt <berni@birkenwald.de>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: conntrack segfault
Date: Wed, 24 Jun 2009 22:05:26 +0200 [thread overview]
Message-ID: <20090624200526.GA14607@pest> (raw)
In-Reply-To: <4A426932.1030607@netfilter.org>
On Wed, Jun 24, 2009 at 07:58:10PM +0200, Pablo Neira Ayuso wrote:
> > The problem is, we currently run conntrack -L every minute. It segfaults
> > about 20 times a day, usually during the period with the highest number
> > of connections. Unless I can always run conntrack in valgrind/gdb
> > automatically and get a usable dump when it fails I have a hard time to
> > get any information from it.
>
> Are you using latest version?
Yeah, pretty much.
libnfnetlink 0.0.41
libnetfilter_log 0.0.16
libnetfilter_conntrack 0.0.99
conntrack-tools 0.9.12
So the only thing that isn't up to date anymore (since two days) is
libnfnetlink. I can't see anything important in the changelog though.
The base system is a SLES 11 with vanilla kernel 2.6.27.23, so that's a
bit aged as well.
Bernhard
next prev parent reply other threads:[~2009-06-24 20:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-23 7:27 null-pointer deref in ulogd2 Bernhard Schmidt
2009-06-23 8:31 ` Bernhard Schmidt
2009-06-23 15:40 ` Pablo Neira Ayuso
2009-06-23 16:54 ` Bernhard Schmidt
2009-06-23 22:39 ` Bernhard Schmidt
2009-06-24 10:59 ` conntrack segfault (was: Re: null-pointer deref in ulogd2) Bernhard Schmidt
2009-06-24 11:17 ` Krzysztof Oledzki
2009-06-24 11:57 ` Jan Engelhardt
2009-06-24 12:56 ` conntrack segfault Bernhard Schmidt
2009-06-24 17:58 ` Pablo Neira Ayuso
2009-06-24 20:05 ` Bernhard Schmidt [this message]
2009-06-24 22:18 ` Bernhard Schmidt
2009-07-02 16:30 ` Pablo Neira Ayuso
2009-07-06 10:29 ` Krzysztof Oledzki
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=20090624200526.GA14607@pest \
--to=berni@birkenwald.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@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.