All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicolas RENAULT <nicolas_renault@yahoo.fr>
To: Netfilter Users Mailing list <netfilter@vger.kernel.org>
Subject: Re: conntrackd crash after few seconds
Date: Fri, 06 Jun 2014 14:37:54 +0200	[thread overview]
Message-ID: <5391B622.8030808@yahoo.fr> (raw)
In-Reply-To: <20140605160639.GB29302@finrod>

Le 05/06/2014 18:06, Martin Kraus a écrit :
> On Thu, Jun 05, 2014 at 05:59:19PM +0200, Arturo Borrero Gonzalez wrote:
>> On 5 June 2014 17:49, Martin Kraus <lists_mk@wujiman.net> wrote:
>>
>>> On Thu, Jun 05, 2014 at 05:19:26PM +0200, Nicolas RENAULT wrote:
>>>> informations :
>>>>
>>>> debian wheezy     3.2.0-4-amd64 #1 SMP Debian 3.2.57-3+deb7u2 x86_64
>>> Hi.
>>>
>>> We had crashes on debian wheezy which were solved by upgrade to
>>>
>>> linux-image-3.13-0.bpo.1-amd64
>>>
>>
>> Is this the same as the Debian bug #746464 [0]?
> probably not. we hit a kernel panic and when I redirected kernel console to
> the serial port for another run it showed that there was a stalled cpu core running
> conntrackd process and everything was just dead.
>
> mk
Hi,

I find the solution , the proble come from conntrackd.conf it was made 
from the one on a squeeze and with the example bring with the package a 
made this one :

Sync {
     Mode FTFW {
         DisableExternalCache On
     }
     UDP {
         IPv4_address 10.98.145.5
         IPv4_Destination_Address 10.98.145.6
         Port 3780
         Interface eth2
         SndSocketBuffer 1249280
         RcvSocketBuffer 1249280
         Checksum on
     }
}
General {
     HashSize 8192
     HashLimit 65535
     Syslog on
     LockFile /var/lock/conntrackd.lock
     UNIX {
         Path /var/run/conntrackd.sock
         Backlog 20
     }
     SocketBufferSize 262142
     SocketBufferSizeMaxGrown 655355
     Filter {
         Protocol Accept {
             TCP
         }
         Address Ignore {
             IPv4_address 10.98.0.0/16     #dedicated link #
         }
     }
}


diff :
                 old         new
HashSize  32768   8192
HashLimit 131072 65535

- NetlinkBufferSize 2097152
- NetlinkBufferSizeMaxGrowth 8388608
- NetlinkOverrunResync On
- NetlinkEventsReliable Off
- PollSecs 15
- EventIterationLimit 100
- Filter From Userspace {

+ SocketBufferSize 262142
+ SocketBufferSizeMaxGrown 655355
+ Filter {

can someone look at my new conntrackd.conf and says if i forget 
somethinks important ?.

regards


-- 
Nicolas


  parent reply	other threads:[~2014-06-06 12:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-05 15:19 conntrackd crash after few seconds Nicolas RENAULT
2014-06-05 15:49 ` Martin Kraus
     [not found]   ` <CAOkSjBifDQQNNQJbkdraYxNvStvK9CrWRNO7LtawpJJ5n=cTMg@mail.gmail.com>
2014-06-05 16:06     ` Martin Kraus
2014-06-06  7:49       ` Nicolas RENAULT
2014-06-06 12:37       ` Nicolas RENAULT [this message]
2014-06-05 16:04 ` Arturo Borrero Gonzalez
2014-06-16 12:08 ` 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=5391B622.8030808@yahoo.fr \
    --to=nicolas_renault@yahoo.fr \
    --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.