search for: disableipfailov

...all things have worked in production as they did in my testing environment, and doesn't always seem to work the same in production from one time to the next, for that matter... > The documentation might not be clear on this but if you're using > 10.external then you need to have the DisableIPFailover tunable set to > 1 on all nodes so that CTDB doesn't try to move the IPs itself. I do have the DisableIPFailover set. from the documentation, I am under the impression that if I do ctdb delip on one node, and ctdb addip on the other node, and make sure the other node shows the correct...

hm, I stand correct on the problem solved statement below. Ip addresses are simply not cooperating on the 2nd node. root at vault1:~# ctdb ip Public IPs on node 0 192.168.120.90 0 192.168.120.91 0 192.168.120.92 0 192.168.120.93 0 root at vault2:/service/ctdb/log/main# ctdb ip Public IPs on node 1 192.168.120.90 0 192.168.120.91 0 192.168.120.92 0 192.168.120.93 0 root at

...se "ctdb moveip" to inform CTDB about moved public IPs and it sends grat ARPs and tickle ACKs on the takeover node. It doesn't actually assign the public IP addresses to nodes. The documentation might not be clear on this but if you're using 10.external then you need to have the DisableIPFailover tunable set to 1 on all nodes so that CTDB doesn't try to move the IPs itself. Please let us know if the documentation could be improved... peace & happiness, martin

I'm currently hacking on CTDB's IP takeover/failover code. For Samba 4.6, I would like to rationalise the IP takeover-related tunable parameters. I would like to know if there are any users who set the values of these tunables to non-default values. The tunables in question are: DisableIPFailover Default: 0 When set to non-zero, ctdb will not perform failover or failback. Even if a node fails while holding public IPs, ctdb will not recover the IPs or assign them to another node. When this tunable is enabled, ctdb will no longer attempt to recover...