search for: ctdb_takeov

...t; assigned and we could serve this ip > 2012/05/24 14:32:09.442657 [recoverd: 6800]: Trigger takeoverrun On the other node: > 2012/05/24 14:32:26.458731 [recoverd: 2970]: Deterministic IPs enabled. Resettin > g all ip allocations > 2012/05/24 14:32:26.458779 [recoverd: 2970]: server/ctdb_takeover.c:1153 Could n > ot find node to take over public address '10.94.43.67' > 2012/05/24 14:32:26.458798 [recoverd: 2970]: Failed to find node to cover ip 10. > 94.43.67 > 2012/05/24 14:32:26.458814 [recoverd: 2970]: server/ctdb_takeover.c:1153 Could n > ot find node to take ov...

...t in /etc/sysconfig/ctdb file. So I had do mkdir /usr/local/var/ctdb manually. After starting ctdb on both nodes all nodes rest unhealthy. And my public addresses rest [-1]!? In my log file I find, ERROR: No link on the public network interface eth0 Or, 2010/05/20 09:36:14.767144 [31866]: server/ctdb_takeover.c:162 public address '192.168.134.101' now unassigned (old iface '__none__' refs[0]) 2010/05/20 09:36:14.767186 [31866]: server/ctdb_takeover.c:162 public address '192.168.134.100' now unassigned (old iface '__none__' refs[0] What Do I miss???? My ctdb status: N...

...opcode:43 dstnode:0 2015/05/18 14:24:23.375232 [ 6031]: client/ctdb_client.c:870 ctdb_control_recv failed 2015/05/18 14:24:23.375240 [ 6031]: Async operation failed with state 3, opcode:0 2015/05/18 14:24:23.375257 [ 6031]: Async wait failed - fail_count=1 2015/05/18 14:24:23.375263 [ 6031]: server/ctdb_takeover.c:1475 Async control CTDB_CONTROL_RELEASE_IP failed. We saw a different pattern yesterday when the smb.conf was edited ahead of the path being created and node 0 became unhealthy for a moment. Node 0: 2015/05/18 14:24:17.694058 [ 5972]: ERROR: samba directory /path/to/directory" not availa...

...2019/02/22 18:01:03.010937 ctdb-eventd[29542]: 60.nfs: boolean true 2019/02/22 18:01:03.010973 ctdb-eventd[29542]: 60.nfs: string "Started grace period" 2019/02/22 18:01:03.065121 ctdbd[29541]: Failed sendto (No route to host) 2019/02/22 18:01:03.065191 ctdbd[29541]: ../ctdb/server/ctdb_takeover.c:388 Failed to send tcp tickle ack for ::ffff:10.10.11.18 2019/02/22 18:01:03.303342 ctdb-eventd[29542]: 60.nfs: Reconfiguring service "nfs"... 2019/02/22 18:01:03.347137 ctdb-recoverd[29647]: Reenabling takeover runs 2019/02/22 18:01:04.172108 ctdbd[29541]: Failed sendto (No route to...

...ges in the log 2012/06/28 10:54:43.313227 [ 1820]: Async operation failed with ret=0 res=1 opcode=0 2012/06/28 10:54:43.313918 [ 1820]: Async operation failed with ret=0 res=1 opcode=0 2012/06/28 10:54:43.313929 [ 1820]: Async wait failed - fail_count=2 2012/06/28 10:54:43.313934 [ 1820]: server/ctdb_takeover.c:1517 Async control CTDB_CONTROL_TAKEOVER_IP failed 2012/06/28 10:54:43.313941 [ 1820]: server/ctdb_recoverd.c:1588 Unable to setup public takeover addresses 2012/06/28 10:54:44.316099 [ 1820]: Taking out recovery lock from recovery daemon 2012/06/28 10:54:44.316129 [ 1820]: Take the recovery...

...tdb.tdb 2018/09/04 04:30:55.564600 ctdb-recoverd[11302]: ../ctdb/client/ctdb_client.c:1010 reqid 50956260 not found 2018/09/04 04:31:33.420908 ctdbd[10129]: ../ctdb/server/ctdb_recover.c:821 Been in recovery mode for too long. Dropping all IPS 2018/09/04 04:31:33.421075 ctdbd[10129]: ../ctdb/server/ctdb_takeover.c:1584 Not releasing IP 10.231.8.70/27 on interface bond1.826, an update is already in progess 2018/09/04 04:31:33.421127 ctdbd[10129]: ../ctdb/server/ctdb_takeover.c:1618 Released 0 public IPs 2018/09/04 04:34:52.390122 ctdbd[10129]: Remote node (2) is now the recovery master 2018/09/04 04:34:55...

...g to stop doing that in the future. The 2nd is a mystery. Are you sure the network connection on node B was up? This message seems to indicate the network is down: 2019/02/22 18:01:03.065121 ctdbd[29541]: Failed sendto (No route to host) 2019/02/22 18:01:03.065191 ctdbd[29541]: ../ctdb/server/ctdb_takeover.c:388 Failed to send tcp tickle ack for ::ffff:10.10.11.18 peace & happiness, martin

Hi, I'm trying to set up a small CTDB cluster running in an IPoIB InfiniBand network. When I try to start up a cluster with a set of public IP addresses, the public addresses do not come online. So, I removed the public address configuration and started a single node up by hand, then tried to add a public address as follows: [root at gp-1-0 ctdb]# ctdb ip Public IPs on node 0 [root at

Hi Martin, Thanks for your answer... >> I am using the 10.external. ip addr show shows the correct IP addresses >> on eth0 in the lxc container. rebooted the physical machine, this node >> is buggered. shut it down, used ip addr add to put the addresses on the >> other node, used ctdb addip and the node took it and node1 is now >> functioning with all 4 IPs just

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

Hello, at this time i want to install a CTDB Cluster with SAMBA 4.7.7 from SOURCE! I compiled samba as follow: |./configure| |--with-cluster-support ||--with-shared-modules=idmap_rid,idmap_tdb2,idmap_ad| The whole SAMBA enviroment is located in /usr/local/samba/. CTDB is located in /usr/local/samba/etc/ctdb. I guess right that the correct path of ctdbd.conf (node file, public address file

....322510 ctdbd[2093]: Set runstate to STARTUP (4) 2018/05/07 15:31:44.322777 ctdb-recovery[2161]: recovered event finished 2018/05/07 15:31:44.323016 ctdb-recoverd[2160]: Takeover run starting 2018/05/07 15:31:44.323240 ctdb-recoverd[2160]: Set takeover_helper to "/usr/local/samba/libexec/ctdb/ctdb_takeover_helper" 2018/05/07 15:31:44.330647 ctdb-takeover[2214]: No nodes available to host public IPs yet 2018/05/07 15:31:44.406941 ctdb-recoverd[2160]: Takeover run completed successfully 2018/05/07 15:31:44.407040 ctdb-recoverd[2160]: ../ctdb/server/ctdb_recoverd.c:1399 Recovery complete 2018/...