From: "Marco Barbero" <marco.barbero@gmail.com>
To: netfilter@vger.kernel.org
Subject: conntrackd [ERROR] commit: Invalid argument
Date: Mon, 9 Jun 2008 15:21:20 +0200 [thread overview]
Message-ID: <e1aa27e00806090621r3fa83ac0s7bb89d903de3be41@mail.gmail.com> (raw)
Hi list
Short story:
My scenario:
conntrack-tools-0.9.7
libnetfilter_conntrack-0.0.94
libnfnetlink-0.0.38
kernel 2.6.25.5
Mode ALARM
conntrackd -c from node master:
looking logs:
a lot of [ERROR] commit: Invalid argument
Mon Jun 9 15:01:26 2008 tcp 6 180 TIME_WAIT
src=192.168.200.14 dst=62.149.195.137 sport=47144 dport=80 src=x.x.x.x
dst=192.168.200.14 sport=80 dport=47144 [ASSURED] mark=0
and at the end:
[Mon Jun 9 15:01:26 2008] (pid=13176) [notice] Committed 1172 new entries
[Mon Jun 9 15:01:26 2008] (pid=13176) [notice] 3294 entries can't be committed
Any hints?
Long story is:
I have a similar scenario on backend cluster firewall
using
conntrack-tools-0.9.6
libnfnetlink-0.0.33
libnetfilter_conntrack-0.0.89
kernel 2.6.24.3
Mode ALARM
All is working great and I don't get any 'entries can't be committed'
Same packages on frontend firewall I got:
'entries can't be committed' and often a kernel panic (related to nfnetlink)
Upgrading to
conntrack-tools-0.9.7
libnetfilter_conntrack-0.0.94
libnfnetlink-0.0.38
kernel 2.6.25.5
Mode ALARM
solved kernel panic issues but still I got 'entries can't be committed'
[ERROR] commit: Invalid argument
Pablo, have you any idea?
Thanks in advance
next reply other threads:[~2008-06-09 13:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-09 13:21 Marco Barbero [this message]
2008-06-11 13:25 ` conntrackd [ERROR] commit: Invalid argument Pablo Neira Ayuso
2008-06-11 13:45 ` Rainer Sabelka
2008-06-11 16:26 ` Pablo Neira Ayuso
2008-06-11 17:15 ` Rainer Sabelka
2008-06-12 15:01 ` Pablo Neira Ayuso
2008-06-12 15:04 ` Patrick McHardy
2008-06-12 21:37 ` Rainer Sabelka
2008-06-12 23:22 ` Rainer Sabelka
2008-06-16 0:31 ` Pablo Neira Ayuso
2008-06-16 20:28 ` Rainer Sabelka
2008-08-08 8:27 ` Pablo Neira Ayuso
2008-06-11 18:11 ` Marco Barbero
2008-06-12 15:05 ` Pablo Neira Ayuso
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=e1aa27e00806090621r3fa83ac0s7bb89d903de3be41@mail.gmail.com \
--to=marco.barbero@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox