Displaying 3 results from an estimated 3 matches for "start_recovery".
2018 Sep 05
1
[ctdb]Unable to run startrecovery event(if mail content is encrypted, please see the attached file)
...04 04:35:09.413319 ctdb-recoverd[9437]: ../ctdb/server/ctdb_recoverd.c:1380 Recovery - updated flags
2018/09/04 04:35:09.417616 ctdb-recovery[1562]: set recovery mode to ACTIVE
2018/09/04 04:35:09.417765 ctdbd[8488]: Recovery has started
2018/09/04 04:35:09.722686 ctdb-recovery[1562]: failed to run start_recovery event on node 1, ret=-1
2018/09/04 04:35:09.722732 ctdb-recovery[1562]: database recovery failed, ret=-1
What happened?
e.g.
node1: IP: 10.231.8.65 VIP: 10.231.8.68
node2: IP: 10.231.8.66 VIP: 10.231.8.69
node3: IP: 10.231.8.67 VIP: 10.231.8.70
Power down node3
The node1 log is as follow:
201...
2018 May 04
2
CTDB Path
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
2018 May 07
2
CTDB Path
...107052 ctdb-recoverd[2160]: Set recovery_helper to
"/usr/local/samba/libexec/ctdb/ctdb_recovery_helper"
2018/05/07 15:31:44.115882 ctdb-recovery[2161]: Set recovery mode to ACTIVE
2018/05/07 15:31:44.116131 ctdbd[2093]: Recovery has started
2018/05/07 15:31:44.195601 ctdb-recovery[2161]: start_recovery event
finished
2018/05/07 15:31:44.195982 ctdb-recovery[2161]: updated VNNMAP
2018/05/07 15:31:44.196048 ctdb-recovery[2161]: recover database 0x6645c6c4
2018/05/07 15:31:44.196632 ctdbd[2093]: Freeze db: ctdb.tdb frozen
2018/05/07 15:31:44.243352 ctdbd[2093]: Thaw db: ctdb.tdb generation
1340321...