Colin, this is my setup where this bug first occured: * Ubuntu Linux with kernel 2.6.24-18-server * libnfnetlink 0.0.38 (compiled from sources) * libnetfilter-conntrack 0.0.94 (compiled from sources) * conntrack-tools 0.9.7 (compiled from sources) * Keepalived v1.1.15
Both machines have a rather identical configuation running a redundant iptables firewall. Conntrackd is running tpo replicate the connection state of the active firewall to the backup (I'll attach conntrackd.conf). The firewalls are in an active/standby configuration managed by keepalived (thoug I don't think you need keepalived to reproduce the bug). So to trigger this bug you'll need to: * make some connections over the active firewall. When I do "conntrackd -i" on the active firewall I see typically a few hundred lines. * Then execute "conntackd -c" on the other machine. This does not trigger the bug everytime, especially since I've turned on logging in conntrackd.conf the bug occured rather infrequent. But executing "while sleep 1 ; do conntrackd -c ; done" crashed the machine almost always within a few seconds. Here I've two references which probably describe the same bug: http://lists.netfilter.org/pipermail/netfilter-failover/2007-January/000710.html http://www.spinics.net/lists/netfilter-devel/msg04170.html ** Attachment added: "conntrackd.conf" http://launchpadlibrarian.net/17825508/conntrackd.conf -- kernel panics when executing "conntrackd -c" https://bugs.launchpad.net/bugs/239215 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
