From: Tom van Leeuwen <tom.van.leeuwen@saasplaza.com>
To: netfilter@vger.kernel.org
Subject: netlink event socket buffer size cannot be doubled further
Date: Tue, 08 May 2012 08:25:51 +0200 [thread overview]
Message-ID: <4FA8BC6F.1080306@saasplaza.com> (raw)
Hi list,
I am having an active/backup firewall using ubuntu12.04 with keepalived
and conntrackd.
I'm using the provided primary-backup.sh script
(/usr/share/doc/conntrackd/examples/sync/primary-backup.sh).
When I've done a failover, I see the following in /var/log/syslog:
May 8 07:43:11 ubuntu conntrack-tools[2652]: flushing conntrack table
in 60 secs
May 8 07:43:11 ubuntu conntrack-tools[2652]: request resync
May 8 07:44:11 ubuntu conntrack-tools[2652]: flushing kernel conntrack
table (scheduled)
May 8 07:44:11 ubuntu conntrack-tools[2652]: netlink event socket
buffer size cannot be doubled further since it will exceed
NetlinkBufferSizeMaxGrowth. We are likely to be losing events, this may
lead to unsynchronized replicas. Please, consider increasing netlink
socket buffer size via NetlinkBufferSize and NetlinkBufferSizeMaxGrowth
clauses in conntrackd.conf
This is my configuration:
# cat /etc/conntrackd/conntrackd.conf
General {
HashSize 8192
HashLimit 1048576
Syslog on
LockFile /var/lock/conntrackd.lock
UNIX {
Path /var/run/conntrackd.sock
Backlog 20
}
#SocketBufferSize 262142
SocketBufferSize 524284
#SocketBufferSizeMaxGrown 655355
SocketBufferSizeMaxGrown 1310710
Filter {
Protocol Accept {
TCP
UDP
ICMP
}
Address Ignore {
IPv4_address 127.0.0.1 # loopback
IPv4_address 1.2.3.51
IPv4_address 1.2.3.6
}
}
}
Sync {
Mode FTFW {
}
UDP {
IPv4_address 1.2.3.51
IPv4_Destination_Address 1.2.3.50
Port 3780
Interface vlan888
Checksum on
}
}
I've already doubled the values which obviously are insufficient.
I don't know what sane values would be or what the impact is when I keep
increasing these values.
They have a default for a reason I suppose :-)
# conntrackd -i | wc -l
29228
Highest value I've seen is ~40000
Kind regards,
Tom van Leeuwen
reply other threads:[~2012-05-08 6:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4FA8BC6F.1080306@saasplaza.com \
--to=tom.van.leeuwen@saasplaza.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 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.