search for: ctdb_wait_until_recov

...COVERY (3) 2018/02/12 19:38:54.882020 ctdb-recoverd[7182]: monitor_cluster starting 2018/02/12 19:38:54.882620 ctdb-recoverd[7182]: Initial recovery master set - forcing election 2018/02/12 19:38:54.882702 ctdbd[6602]: This node (1) is now the recovery master 2018/02/12 19:38:55.882735 ctdbd[6602]: CTDB_WAIT_UNTIL_RECOVERED 2018/02/12 19:38:56.902874 ctdbd[6602]: CTDB_WAIT_UNTIL_RECOVERED 2018/02/12 19:38:57.885800 ctdb-recoverd[7182]: Election period ended 2018/02/12 19:38:57.886134 ctdb-recoverd[7182]: Node:1 was in recovery mode. Start recovery process 2018/02/12 19:38:57.886160 ctdb-recoverd[7182]: ../ctdb/ser...

...COVERY (3) 2018/02/12 19:38:54.882020 ctdb-recoverd[7182]: monitor_cluster starting 2018/02/12 19:38:54.882620 ctdb-recoverd[7182]: Initial recovery master set - forcing election 2018/02/12 19:38:54.882702 ctdbd[6602]: This node (1) is now the recovery master 2018/02/12 19:38:55.882735 ctdbd[6602]: CTDB_WAIT_UNTIL_RECOVERED 2018/02/12 19:38:56.902874 ctdbd[6602]: CTDB_WAIT_UNTIL_RECOVERED 2018/02/12 19:38:57.885800 ctdb-recoverd[7182]: Election period ended 2018/02/12 19:38:57.886134 ctdb-recoverd[7182]: Node:1 was in recovery mode. Start recovery process 2018/02/12 19:38:57.886160 ctdb-recoverd[7182]: ../ctdb/ser...

...COVERY (3) 2018/02/12 19:38:54.882020 ctdb-recoverd[7182]: monitor_cluster starting 2018/02/12 19:38:54.882620 ctdb-recoverd[7182]: Initial recovery master set - forcing election 2018/02/12 19:38:54.882702 ctdbd[6602]: This node (1) is now the recovery master 2018/02/12 19:38:55.882735 ctdbd[6602]: CTDB_WAIT_UNTIL_RECOVERED 2018/02/12 19:38:56.902874 ctdbd[6602]: CTDB_WAIT_UNTIL_RECOVERED 2018/02/12 19:38:57.885800 ctdb-recoverd[7182]: Election period ended 2018/02/12 19:38:57.886134 ctdb-recoverd[7182]: Node:1 was in recovery mode. Start recovery process 2018/02/12 19:38:57.886160 ctdb-recoverd[7182]: ../ctdb/ser...

...d 2010/05/20 09:35:40.092516 [31866]: server/eventscript.c:715 Starting eventscript recovered 2010/05/20 09:35:40.378186 [31866]: server/eventscript.c:466 Eventscript recovered finished with state 0 2010/05/20 09:35:40.378264 [31866]: Monitoring has been enabled 2010/05/20 09:35:40.534741 [31866]: CTDB_WAIT_UNTIL_RECOVERED 2010/05/20 09:35:40.534809 [31866]: server/ctdb_monitor.c:251 wait for pending recoveries to end. Wait one more second. 2010/05/20 09:35:41.088485 [31923]: The interfaces status has changed on local node 1 - force takeover run 2010/05/20 09:35:41.088730 [31923]: Trigger takeoverrun 2010/05/20 0...

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

...COVERY (3) 2018/02/12 19:38:54.882020 ctdb-recoverd[7182]: monitor_cluster starting 2018/02/12 19:38:54.882620 ctdb-recoverd[7182]: Initial recovery master set - forcing election 2018/02/12 19:38:54.882702 ctdbd[6602]: This node (1) is now the recovery master 2018/02/12 19:38:55.882735 ctdbd[6602]: CTDB_WAIT_UNTIL_RECOVERED 2018/02/12 19:38:56.902874 ctdbd[6602]: CTDB_WAIT_UNTIL_RECOVERED 2018/02/12 19:38:57.885800 ctdb-recoverd[7182]: Election period ended 2018/02/12 19:38:57.886134 ctdb-recoverd[7182]: Node:1 was in recovery mode. Start recovery process 2018/02/12 19:38:57.886160 ctdb-recoverd[7182]: ../ctdb/ser...

...VERY (3) 2018/05/07 15:31:41.098653 ctdb-recoverd[2160]: monitor_cluster starting 2018/05/07 15:31:41.102114 ctdb-recoverd[2160]: Initial recovery master set - forcing election 2018/05/07 15:31:41.102652 ctdbd[2093]: This node (1) is now the recovery master 2018/05/07 15:31:42.098950 ctdbd[2093]: CTDB_WAIT_UNTIL_RECOVERED 2018/05/07 15:31:43.099496 ctdbd[2093]: CTDB_WAIT_UNTIL_RECOVERED 2018/05/07 15:31:44.100002 ctdbd[2093]: CTDB_WAIT_UNTIL_RECOVERED 2018/05/07 15:31:44.103288 ctdb-recoverd[2160]: Election period ended 2018/05/07 15:31:44.105712 ctdb-recoverd[2160]: Node:1 was in recovery mode. Start recovery...

...:10:00.253673 [30575]: Freeze priority 1 2013/04/09 16:10:00.253783 [30575]: Freeze priority 2 2013/04/09 16:10:00.253901 [30575]: Freeze priority 3 2013/04/09 16:10:00.254181 [recoverd:30648]: server/ctdb_recoverd.c:2005 Send election request to all active nodes 2013/04/09 16:10:01.249677 [30575]: CTDB_WAIT_UNTIL_RECOVERED 2013/04/09 16:10:02.249961 [30575]: CTDB_WAIT_UNTIL_RECOVERED 2013/04/09 16:10:03.250141 [30575]: CTDB_WAIT_UNTIL_RECOVERED 2013/04/09 16:10:03.257560 [recoverd:30648]: server/ctdb_recoverd.c:1055 Election timed out 2013/04/09 16:10:03.258563 [recoverd:30648]: The interfaces status has changed...

...is always zero bytes. If I start all 3 nodes at once, none of them become healthy. Somewhere along the line I once managed to get two nodes healthy at once, and they agreed on who was recmaster. This was a fluke that I cannot reproduce. Typical log messages 2011/04/27 07:33:23.633970 [25303]: CTDB_WAIT_UNTIL_RECOVERED 2011/04/27 07:33:23.634002 [25303]: server/ctdb_monitor.c:232 generation is INVALID. Wait one more second 2011/04/27 07:33:23.695058 [recoverd:25365]: server/ctdb_recoverd.c:1812 Send election request to all active nodes 2011/04/27 07:33:24.196099 [recoverd:25365]: server/ctdb_recoverd.c:1812 S...