Displaying 7 results from an estimated 7 matches for "moveip".
Did you mean:
moveit
2017 Nov 08
1
ctdb vacuum timeouts and record locks
...external. Although we have tested
> it, we haven't actually seen it used in production before! 10.external
> is a hack to allow use of CTDB's connection tracking while managing the
> public IP addresses externally. That is, you tell CTDB about the
> public IPs, use "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.
Hm, okay, I was clear that using 10.external it is a human's
responsibility to deal with assigning IPs to physic...
2017 Nov 02
2
ctdb vacuum timeouts and record locks
....
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 vault2:/service/ctdb/log/main# ctdb moveip 192.168.120.90 1
Control TAKEOVER_IP failed, ret=-1
Failed to takeover IP on node 1
root at vault1:~# ctdb moveip 192.168.120.90 0
Memory allocation error
root at vault2:/service/ctdb/log/main# ctdb ipinfo 192.168.120.90
Public IP[192.168.120.90] info on node 1
IP:192.168.120.90
CurrentNode:0
Num...
2017 Nov 06
0
ctdb vacuum timeouts and record locks
...0.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 vault2:/service/ctdb/log/main# ctdb moveip 192.168.120.90 1
> Control TAKEOVER_IP failed, ret=-1
> Failed to takeover IP on node 1
>
> root at vault1:~# ctdb moveip 192.168.120.90 0
> Memory allocation error
>
> root at vault2:/service/ctdb/log/main# ctdb ipinfo 192.168.120.90
> Public IP[192.168.120.90] info on no...
2016 Nov 10
1
CTDB IP takeover/failover tunables - do you use them?
...another node.
When this tunable is enabled, ctdb will no longer attempt to recover
the cluster by failing IP addresses over to other nodes. This leads to
a service outage until the administrator has manually performed IP
failover to replacement nodes using the 'ctdb moveip' command.
NoIPFailback
Default: 0
When set to 1, ctdb will not perform failback of IP addresses when a
node becomes healthy. When a node becomes UNHEALTHY, ctdb WILL perform
failover of public IP addresses, but when the node becomes HEALTHY
again, ctdb wi...
2016 Jul 18
1
File locks are not preserved when IP is moved to another node.
...sted domains = yes
[gluster]
inherit acls=yes
inherit owner=no
map acl inherit=yes
strict allocate=no
locking=yes
guest ok=no
valid users="DEV+administrator"
path=/mnt/glusterfs
read only=no
guest only=no
Content of locking.tdb before "ctdb moveip"
ctdb catdb locking.tdb
key(24) =
"\00\00\00\00\00\00\00\00\9E\C7\A8m\B85\91\B0\00\00\00\00\00\00\00\00"
dmaster: 1
rsn: 6
data(324) =
"\FF\F2S\AD\8F9}\04\00\00\02\00\04\00\02\00\00\00\00\00\01\00\00\00\01\00\00\00\00\00\00\00\A3,\00\00\00\00\00\00\00\00\00\00\01\00\00\00\BAj\E...
2017 Oct 27
3
ctdb vacuum timeouts and record locks
Hi Martin,
Thanks for reading and taking the time to reply
>> ctdbd[89]: Unable to get RECORD lock on database locking.tdb for 20 seconds
>> /usr/local/samba/etc/ctdb/debug_locks.sh: 142:
>> /usr/local/samba/etc/ctdb/debug_locks.sh: cannot create : Directory
>> nonexistent
>> sh: echo: I/O error
>> sh: echo: I/O error
>
> That's weird. The only
2023 Feb 16
1
ctdb tcp kill: remaining connections
On Thu, 16 Feb 2023 17:30:37 +0000, Ulrich Sibiller
<ulrich.sibiller at atos.net> wrote:
> Martin Schwenke schrieb am 15.02.2023 23:23:
> > OK, this part looks kind-of good. It would be interesting to know how
> > long the entire failover process is taking.
>
> What exactly would you define as the begin and end of the failover?
From "Takeover run