Bernhard Bock wrote: > Pablo Neira Ayuso wrote: >> As you're using the Alarm mode, the time required to resynchronize the >> backup and the master is RefreshTime (which is 15 seconds in your config >> files). Are you probably triggering the fail-over before that amount of >> time? > > No, I always waited longer. My keepalived has a pre-emption delay of > 30sec before becoming master, and I always did wait at least a minute or > so before triggering a failback. Right, I didn't look the config files in deep. >> Basically, you must to find the same >> set of flows in the master's internal-cache and the backup's >> external-cache if everything goes fine. > > That's exactly what I can observe. They are consistent when the failover > goes fine, and they're not when I have INVALID packets. Why did you set cache-write through on? You have a basic primary-backup failover, right? Set it off, please. > I also see 'conntrack -E' working with 100 parallel TCP connections, and > dying with "Operation failed: No buffer space available" with 1000 > connections. Maybe this is related? No, that's a different point. That's a bug in the CLI, I'll add a parameter to increase the buffer size. > As written in my last mail, I increased the SocketBufferSize to 256M and > the SocketBufferSizemaxGrown to 1024M in conntrackd.conf. That's too much, why did you set such a high buffer? Are you getting some log messages that tells you to do so? >> Until we reach conntrack-tools-1.0, which I expect to reach soon since >> most of the pending work is already done, I suggest you to upgrade to >> lastest (as for now, it is 0.9.7). This release includes important >> improvements, fixes and features. The alarm mode is a bit spamming, I >> also suggest you to give a try to the ft-fw and the notrack approaches. > > Let me give you a short update after upgrading: > > I upgraded to conntrack-tools 0.9.7, libnflink 0.0.39 and > libnetfilter_conntrack 0.0.96. Basically, I took already available > Fedora 10 source RPMs and compiled them for Fedora 9. > > Without failover, it seems to work at the first glance. In 'conntrackd > -s' I see plausible numbers of entries in internal and external caches. > Unfortunately, it still breaks on many failovers with 1000 parallel TCP > connections. > > Now I get a lot of the following entries in syslog in addition to the > INVALID packets: > conntrack-tools[21319]: cache_wt crt-upd: Invalid argument > conntrack-tools[21319]: cache_wt update:Invalid argument Please, enable logging via /var/log/conntrackd.log. The syslog logging is not including the information about the entry that has failed. I'll fix this to make both logging approaches consistent. > After a failed failover, I have to flush the connection table and > stop/restart both conntrackd processes in order to make it work again. > > > In FT-FW mode, the failover always fails, and it produces log entries like: Please, too many issues at the same time. Let's try to get it working without the cachewritethrough clause and then we'll get back to this, OK? -- "Los honestos son inadaptados sociales" -- Les Luthiers -- To unsubscribe from this list: send the line "unsubscribe netfilter" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
