search for: deterministicip

...d > it sends grat ARPs and tickle ACKs on the takeover node. It doesn't > actually assign the public IP addresses to nodes. Hm, okay, I was clear that using 10.external it is a human's responsibility to deal with assigning IPs to physical interfaces. In re-reading the docs, I see DeterministicIPs and NoIPFailback are required for moveip, which I am not sure are set. will check next opportunity, if they aren't that might explain the behaviour, however, the ips were correctly assigned using the ip command. The reason I am using 10.external is because when I initially set up my clus...

...2. If you do this, can you please explain why? :-) I would like to make all of the above tunables global but I will not do that if it breaks an existing use case and I can't find a different way. There are also 2 tunables to choose the algorithm used to calculate the IP address layout: DeterministicIPs Default: 0 When set to 1, ctdb will try to keep public IP addresses locked to specific nodes as far as possible. This makes it easier for debugging since you can know that as long as all nodes are healthy public IP X will always be hosted by node Y. The...

...16:07:59.053378 [33243]: Freeze priority 2 2014/07/03 16:07:59.053602 [33243]: Freeze priority 3 2014/07/03 16:07:59.229670 [33243]: Freeze priority 1 2014/07/03 16:07:59.229780 [33243]: Freeze priority 2 2014/07/03 16:07:59.229863 [33243]: Freeze priority 3 2014/07/03 16:07:59.247015 [33243]: Set DeterministicIPs to 0 2014/07/03 16:07:59.253600 [33243]: Set NoIpFailback to 1 2014/07/03 16:08:03.235484 [33287]: Taking out recovery lock from recovery daemon 2014/07/03 16:08:03.235584 [33287]: Take the recovery lock 2014/07/03 16:08:03.236070 [33287]: Recovery lock taken successfully 2014/07/03 16:08:03.23619...

...er subsystem * The mapping between symbolic and numeric debug levels has changed Configurations containing numeric debug levels should be updated. Symbolic debug levels are recommended. See the DEBUG LEVEL section of ctdb(7) for details. * Tunable IPAllocAlgorithm replaces LCP2PublicIPs, DeterministicIPs See ctdb-tunables(7) for details * CTDB's configuration tunables should be consistently set across a cluster This has always been the cases for most tunables but this fact is now documented. * CTDB ships with recovery lock helper call-outs for etcd and Ceph RADOS To build/install...

...er subsystem * The mapping between symbolic and numeric debug levels has changed Configurations containing numeric debug levels should be updated. Symbolic debug levels are recommended. See the DEBUG LEVEL section of ctdb(7) for details. * Tunable IPAllocAlgorithm replaces LCP2PublicIPs, DeterministicIPs See ctdb-tunables(7) for details * CTDB's configuration tunables should be consistently set across a cluster This has always been the cases for most tunables but this fact is now documented. * CTDB ships with recovery lock helper call-outs for etcd and Ceph RADOS To build/install...

...er subsystem * The mapping between symbolic and numeric debug levels has changed Configurations containing numeric debug levels should be updated. Symbolic debug levels are recommended. See the DEBUG LEVEL section of ctdb(7) for details. * Tunable IPAllocAlgorithm replaces LCP2PublicIPs, DeterministicIPs See ctdb-tunables(7) for details * CTDB's configuration tunables should be consistently set across a cluster This has always been the cases for most tunables but this fact is now documented. * CTDB ships with recovery lock helper call-outs for etcd and Ceph RADOS To build/install...

...er subsystem * The mapping between symbolic and numeric debug levels has changed Configurations containing numeric debug levels should be updated. Symbolic debug levels are recommended. See the DEBUG LEVEL section of ctdb(7) for details. * Tunable IPAllocAlgorithm replaces LCP2PublicIPs, DeterministicIPs See ctdb-tunables(7) for details * CTDB's configuration tunables should be consistently set across a cluster This has always been the cases for most tunables but this fact is now documented. * CTDB ships with recovery lock helper call-outs for etcd and Ceph RADOS To build/install...

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

...between symbolic and numeric debug levels has changed > > Configurations containing numeric debug levels should be updated. > Symbolic debug levels are recommended. See the DEBUG LEVEL section > of ctdb(7) for details. > > * Tunable IPAllocAlgorithm replaces LCP2PublicIPs, DeterministicIPs > > See ctdb-tunables(7) for details > > * CTDB's configuration tunables should be consistently set across a cluster > > This has always been the cases for most tunables but this fact is > now documented. > > * CTDB ships with recovery lock helper call-outs fo...

...er subsystem * The mapping between symbolic and numeric debug levels has changed Configurations containing numeric debug levels should be updated. Symbolic debug levels are recommended. See the DEBUG LEVEL section of ctdb(7) for details. * Tunable IPAllocAlgorithm replaces LCP2PublicIPs, DeterministicIPs See ctdb-tunables(7) for details * CTDB's configuration tunables should be consistently set across a cluster This has always been the cases for most tunables but this fact is now documented. * CTDB ships with recovery lock helper call-outs for etcd and Ceph RADOS To build/install...

...er subsystem * The mapping between symbolic and numeric debug levels has changed Configurations containing numeric debug levels should be updated. Symbolic debug levels are recommended. See the DEBUG LEVEL section of ctdb(7) for details. * Tunable IPAllocAlgorithm replaces LCP2PublicIPs, DeterministicIPs See ctdb-tunables(7) for details * CTDB's configuration tunables should be consistently set across a cluster This has always been the cases for most tunables but this fact is now documented. * CTDB ships with recovery lock helper call-outs for etcd and Ceph RADOS To build/install...

...ver subsystem * The mapping between symbolic and numeric debug levels has changed Configurations containing numeric debug levels should be updated. Symbolic debug levels are recommended. See the DEBUG LEVEL section of ctdb(7) for details. * Tunable IPAllocAlgorithm replaces LCP2PublicIPs, DeterministicIPs See ctdb-tunables(7) for details. * CTDB's configuration tunables should be consistently set across a cluster This has always been the cases for most tunables but this fact is now documented. * CTDB ships with recovery lock helper call-outs for etcd and Ceph RADOS To build/install...

...ver subsystem * The mapping between symbolic and numeric debug levels has changed Configurations containing numeric debug levels should be updated. Symbolic debug levels are recommended. See the DEBUG LEVEL section of ctdb(7) for details. * Tunable IPAllocAlgorithm replaces LCP2PublicIPs, DeterministicIPs See ctdb-tunables(7) for details. * CTDB's configuration tunables should be consistently set across a cluster This has always been the cases for most tunables but this fact is now documented. * CTDB ships with recovery lock helper call-outs for etcd and Ceph RADOS To build/install...

...etween symbolic and numeric debug levels has changed > > Configurations containing numeric debug levels should be updated. > Symbolic debug levels are recommended. See the DEBUG LEVEL section > of ctdb(7) for details. > > * Tunable IPAllocAlgorithm replaces LCP2PublicIPs, DeterministicIPs > > See ctdb-tunables(7) for details. > > * CTDB's configuration tunables should be consistently set across a > cluster > > This has always been the cases for most tunables but this fact is > now documented. > > * CTDB ships with recovery lock helper cal...