From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Jiri Kosina <jikos@kernel.org>
Cc: Arturo Borrero Gonzalez <arturo@debian.org>,
Netfilter Users Mailing list <netfilter@vger.kernel.org>,
info@jablonka.cz
Subject: Re: conntrackd: synchronization failures
Date: Mon, 16 Jan 2017 11:16:29 +0100 [thread overview]
Message-ID: <20170116101629.GA5107@salvia> (raw)
In-Reply-To: <alpine.LRH.2.00.1701131558020.25853@gjva.wvxbf.pm>
On Fri, Jan 13, 2017 at 04:01:43PM +0100, Jiri Kosina wrote:
> On Thu, 12 Jan 2017, Arturo Borrero Gonzalez wrote:
>
> > I can see them too, in NATed connections most of the time:
> >
> > Jan 12 08:54:09 cf03 conntrack-tools[32717]: inject-upd1: File exists
> > Jan 12 08:54:09 cf03 conntrack-tools[32717]: tcp 6 120 TIME_WAIT
> > src=192.168.5.181 dst=31.13.65.1 sport=57419 dport=443 [ASSURED]
> > Jan 12 08:54:09 cf03 conntrack-tools[32717]: inject-upd1: File exists
> > Jan 12 08:54:09 cf03 conntrack-tools[32717]: tcp 6 10 CLOSE
> > src=192.168.5.181 dst=31.13.65.1 sport=57419 dport=443 [ASSURED]
> > Jan 12 08:55:15 cf03 conntrack-tools[32717]: inject-add2: File exists
> > Jan 12 08:55:15 cf03 conntrack-tools[32717]: tcp 6 120 SYN_SENT
> > src=192.168.5.219 dst=216.58.211.202 sport=45121 dport=443 [UNREPLIED]
> > Jan 12 08:55:15 cf03 conntrack-tools[32717]: inject-upd1: File exists
> > Jan 12 08:55:15 cf03 conntrack-tools[32717]: tcp 6 60 SYN_RECV
> > src=192.168.5.219 dst=216.58.211.202 sport=45121 dport=443
> > Jan 12 08:55:15 cf03 conntrack-tools[32717]: inject-upd1: File exists
> > Jan 12 08:55:15 cf03 conntrack-tools[32717]: tcp 6 432000
> > ESTABLISHED src=192.168.5.219 dst=216.58.211.202 sport=45121 dport=443
> > [ASSURED]
>
> Do you also experience (either from inject-upd2 or inject-add2 phase)
> EBUSY ones?
>
> I'm seeing quite a lot of entries such as
>
> (pid=9769) [ERROR] inject-add2: Device or resource busy
> tcp 6 300 CLOSE src=10.33.37.4 dst=77.75.77.94 sport=42653 dport=443 [UNREPLIED]
>
> I'm still trying to understand from the source what consequences this
> might have; any hint would be appreciated.
Some conntrack attributes can also be set up from NEW flows.
Most likely this entry already exists in the kernel, and conntrackd is
trying to update it.
next prev parent reply other threads:[~2017-01-16 10:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-11 20:06 conntrackd: synchronization failures Jiri Kosina
2017-01-11 20:12 ` Jiri Kosina
2017-01-11 21:57 ` Jiri Kosina
2017-01-12 7:58 ` Arturo Borrero Gonzalez
2017-01-13 15:01 ` Jiri Kosina
2017-01-16 10:16 ` Pablo Neira Ayuso [this message]
2017-03-10 11:26 ` 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=20170116101629.GA5107@salvia \
--to=pablo@netfilter.org \
--cc=arturo@debian.org \
--cc=info@jablonka.cz \
--cc=jikos@kernel.org \
--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.