Displaying 8 results from an estimated 8 matches for "ctdb_monitor".
2010 May 20
0
WG: Which version of CTDB
...y"
CTDB_PUBLIC_ADDRESSES=/etc/ctdb/public_addresses
CTDB_MANAGES_SAMBA=yes
ulimit -n 10000
CTDB_NOTIFY_SCRIPT=/etc/ctdb/notify.sh
CTDB_DBDIR=/var/ctdb
CTDB_DBDIR_PERSISTENT=/var/ctdb/persistent
CTDB_EVENT_SCRIPT_DIR=/etc/ctdb/events.d
CTDB_SOCKET=/tmp/ctdb.socket
CTDB_TRANSPORT="tcp"
CTDB_MONITOR_FREE_MEMORY=100
CTDB_LOGFILE=/var/log/log.ctdbq
My /etc/ctdb/nodes
192.168.134.28
192.168.134.27
My /etc/ctdb/public_addresses
192.168.134.100/24 eth0
192.168.134.101/24 eth0
My /etc/samba/smb.conf
[global]
workgroup = domain-cluster
security=user
clustering=yes
p...
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
...ecoveries for
10 seconds
2018/05/07 15:31:44.826298 ctdbd[2093]: Recovery mode set to ACTIVE
2018/05/07 15:31:44.827914 ctdbd[2093]: Remote node (0) is now the
recovery master
2018/05/07 15:31:45.100166 ctdbd[2093]: CTDB_WAIT_UNTIL_RECOVERED
2018/05/07 15:31:45.100245 ctdbd[2093]:
../ctdb/server/ctdb_monitor.c:329 in recovery. Wait one more second
2018/05/07 15:31:46.099005 ctdbd[2093]: 192.168.199.53:4379: connected
to 192.168.199.52:4379 - 1 connected
2018/05/07 15:31:46.101234 ctdbd[2093]: CTDB_WAIT_UNTIL_RECOVERED
2018/05/07 15:31:46.101301 ctdbd[2093]:
../ctdb/server/ctdb_monitor.c:329 in recove...
2013 Apr 09
0
Failed to start CTDB first time after install
...72044 [30575]: Recovery has finished
2013/04/09 16:10:03.972067 [30575]: Monitoring has been disabled
2013/04/09 16:10:03.972083 [30575]: server/eventscript.c:800 Starting eventscript recovered
2013/04/09 16:10:04.250561 [30575]: CTDB_WAIT_UNTIL_RECOVERED
2013/04/09 16:10:04.250613 [30575]: server/ctdb_monitor.c:261 wait for pending recoveries to end. Wait one more second.
2013/04/09 16:10:04.322804 [30575]: server/eventscript.c:486 Eventscript recovered finished with state 0
2013/04/09 16:10:04.322870 [30575]: Monitoring has been enabled
2013/04/09 16:10:04.322983 [recoverd:30648]: server/ctdb_recoverd...
2014 Oct 07
1
CDTB On Samba 4.1.12 As Member files server.
...CTDB_SERVICE_SMB=samba
CTDB_SERVICE_WINBIND=winbind
CTDB_NODES=/etc/ctdb/nodes
CTDB_NOTIFY_SCRIPT=/etc/ctdb/notify.sh
CTDB_DBDIR=/var/lib/ctdb
CTDB_DBDIR_PERSISTENT=/var/lib/ctdb/persistent
CTDB_EVENT_SCRIPT_DIR=/etc/ctdb/events.d
CTDB_SOCKET=/var/lib/ctdb/ctdb.socket
CTDB_TRANSPORT="tcp"
CTDB_MONITOR_FREE_MEMORY=100
CTDB_START_AS_DISABLED="yes"
CTDB_CAPABILITY_RECMASTER=yes
CTDB_CAPABILITY_LMASTER=yes
NATGW_PUBLIC_IP=
NATGW_PUBLIC_IFACE=
NATGW_DEFAULT_GATEWAY=
NATGW_PRIVATE_IFACE=
NATGW_PRIVATE_NETWORK=
NATGW_NODES=/etc/ctdb/natgw_nodes
CTDB_LOGFILE=/var/log/messages
CTDB_DEBUGLEVEL=2...
2009 Jul 31
0
CTDB Node unnecessarily banning other nodes
...nned - forcing
freeze and recovery
node3 (should not ban itself):
2009/07/29 23:23:37.748506 [19892]: Got a ban request for pnn:0 but our pnn
is 2. Ignoring ban request
2009/07/29 23:23:37.749575 [19750]: This node has been banned - forcing
freeze and recovery
Existing Version 1.0.77: ctdb-1.0.77/ctdb_monitor.c
241 if ((node->flags & NODE_FLAGS_BANNED) && !(c->old_flags &
NODE_FLAGS _BANNED)) {
242 /* make sure we are frozen */
243 DEBUG(DEBUG_NOTICE,("This node has been banned - forcing
fre eze and recovery\n"));
--
I see...
2011 Apr 27
1
CTDB / Samba4. Nodes don't become healthy on first startup
...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
Send election request to all active nodes
So I have a number...
2014 Feb 26
0
CTDB Debug Help
...#39;
2014/02/26 12:13:37.856639 [10027232]: server/ctdb_recover.c:1006 Failed
to start recovery
2014/02/26 12:13:37.856705 [10027232]: pnn 1 Invalid reqid 0 in
ctdb_reply_control
2014/02/26 12:14:37.858397 [10027232]: Banning this node for 300 seconds
2014/02/26 12:14:38.033523 [10027232]: server/ctdb_monitor.c:485 Node 0
became healthy - force recovery for startup
2014/02/26 12:14:38.581971 [recoverd:11272374]: Refusing to disable
takeover runs on inactive node
2014/02/26 12:14:38.702472 [10027232]: Failed to open event script
directory '/usr/smb_cluster/etc/ctdb/events.d'
2014/02/26 12:14:3...