Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Yoann Juet <yoann.juet@univ-nantes.fr>
To: Pablo Neira Ayuso <pablo@netfilter.org>, netfilter@vger.kernel.org
Subject: Re: Second failover failure with conntrackd - INVALID packets
Date: Mon, 23 Feb 2009 16:38:26 +0100	[thread overview]
Message-ID: <49A2C2F2.2050604@univ-nantes.fr> (raw)
In-Reply-To: <499B0696.2020300@netfilter.org>

[-- Attachment #1: Type: text/plain, Size: 891 bytes --]

Pablo Neira Ayuso wrote:
> Pablo Neira Ayuso wrote:
>> Please, add the following line here to your scripts:
>>
>> conntrackd -B -C /etc/conntrackd.conf
>>
>> Let me now if that fixes your problem.
> 
> Updates? I'm intrigued with your problem. Some more info for
> troubleshooting. You have the commands:
> 
> display internal cache (states that belong to this node)
> # conntrackd -i
> 
> display external cache (states that belong to other nodes)
> # conntrackd -e
> 
> While trigering fail-overs, you should see the same states in the
> active's internal cache and the backup's external cache. If that does
> happen, there's a problem somewhere.
> 
> I'm about to release 0.9.11 but before I'd like to close pending issues.
> 

The issue is solved by adding "conntrackd -B" to my script. According to 
the logs, such instruction sends bulk update. What is it for exactly ?

Best regards,

[-- Attachment #2: yoann_juet.vcf --]
[-- Type: text/x-vcard, Size: 375 bytes --]

begin:vcard
fn:Yoann Juet
n:Juet;Yoann
org;quoted-printable:;DSI Universit=C3=A9 de Nantes
adr;quoted-printable:BP92208;;2, rue de la Houssini=C3=A8re;Nantes;;44322;France
email;internet:yoann.juet@univ-nantes.fr
title;quoted-printable:Ing=C3=A9nieur s=C3=A9curit=C3=A9 & r=C3=A9seau
tel;work:02.51.12.53.93
tel;fax:02.51.12.58.60
x-mozilla-html:FALSE
version:2.1
end:vcard


  parent reply	other threads:[~2009-02-23 15:38 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-21 17:52 Second failover failure with conntrackd - INVALID packets Yoann Juet
2009-01-21 20:52 ` Pablo Neira Ayuso
2009-01-22  9:54   ` Yoann Juet
2009-01-22 16:55     ` Pablo Neira Ayuso
2009-01-23 12:39       ` Yoann Juet
2009-01-25 10:51         ` Pablo Neira Ayuso
2009-01-25 17:55           ` Pablo Neira Ayuso
2009-01-26 19:27             ` Yoann Juet
2009-01-26 23:01               ` Pablo Neira Ayuso
2009-01-29 16:10                 ` Yoann Juet
2009-02-03 10:10                   ` Pablo Neira Ayuso
2009-02-04 10:37                     ` Yoann Juet
2009-02-04 10:43                       ` Pablo Neira Ayuso
2009-02-06  9:18                         ` Yoann Juet
2009-02-09 11:29                           ` Pablo Neira Ayuso
2009-02-10 13:13                             ` Yoann Juet
2009-02-11  8:49                               ` Pablo Neira Ayuso
2009-02-13  8:21                                 ` Yoann Juet
2009-02-13 15:20                                   ` Pablo Neira Ayuso
     [not found]                                     ` <499B0696.2020300@netfilter.org>
2009-02-23 15:38                                       ` Yoann Juet [this message]
2009-02-23 20:40                                         ` Pablo Neira Ayuso
2009-02-24 12:03                                           ` Yoann Juet

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=49A2C2F2.2050604@univ-nantes.fr \
    --to=yoann.juet@univ-nantes.fr \
    --cc=netfilter@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox