3 .\" Generator: DocBook XSL Stylesheets v1.72.0 <http://docbook.sf.net/>
8 .TH "CTDB" "1" "07/05/2007" "" ""
9 .\" disable hyphenation
11 .\" disable justification (adjust text to left margin only)
14 ctdb \- clustered tdb database management utility
17 \fBctdb [ OPTIONS ] COMMAND ...\fR
19 \fBctdb\fR [\-n\ <node>] [\-Y] [\-t\ <timeout>] [\-?\ \-\-help] [\-\-usage] [\-d\ \-\-debug=<INTEGER>] [\-\-socket=<filename>]
22 ctdb is a utility to view and manage a ctdb cluster.
27 This specifies on which node to execute the command. Default is to run the command on the deamon running on the local host.
32 Produce output in machinereadable form for easier parsing by scripts. Not all commands support this option.
37 How long should ctdb wait for a command to complete before timing out. Default is 3 seconds.
42 Print some help text to the screen.
47 Print useage information to the screen.
50 \-d \-\-debug=<debuglevel>
52 Change the debug level for the command. Default is 0.
57 Specify the socketname to use when connecting to the local ctdb daemon. The default is /tmp/ctdb.socket .
59 You only need to specify this parameter if you run multiple ctdb daemons on the same physical host and thus can not use the default name for the domain socket.
61 .SH "ADMINISTRATIVE COMMANDS"
63 These are commands used to monitor and administrate a CTDB cluster.
66 This command shows the current status of the ctdb node.
69 .nr an-no-space-flag 1
75 Node status reflects the current status of the node. There are four possible states:
77 OK \- This node is fully functional.
79 DISCONNECTED \- This node could not be connected through the network and is currently not parcipitating in the cluster. If there is a public IP address associated with this node it should have been taken over by a different node. No services are running on this node.
81 DISABLED \- This node has been administratively disabled. This node is still functional and participates in the CTDB cluster but its IP addresses have been taken over by a different node and no services are currently being hosted.
83 UNHEALTHY \- A service provided by this node is malfunctioning and should be investigated. The CTDB daemon itself is operational and participates in the cluster. Its public IP address has been taken over by a different node and no services are currnetly being hosted. All unhealthy nodes should be investigated and require an administrative action to rectify.
85 BANNED \- This node failed too many recovery attempts and has been banned from participating in the cluster for a period of RecoveryBanPeriod seconds. Any public IP address has been taken over by other nodes. This node does not provide any services. All banned nodes should be investigated and require an administrative action to rectify. This node does not perticipate in the CTDB cluster but can still be communicated with. I.e. ctdb commands can be sent to it.
89 .nr an-no-space-flag 1
95 The generation id is a number that indicates the current generation of a cluster instance. Each time a cluster goes through a reconfiguration or a recovery its generation id will be changed.
99 .nr an-no-space-flag 1
105 The list of Virtual Node Numbers. This is a list of all nodes that actively participates in the cluster and that share the workload of hosting the Clustered TDB database records. Only nodes that are parcipitating in the vnnmap can become lmaster or dmaster for a database record.
109 .nr an-no-space-flag 1
115 This is the current recovery mode of the cluster. There are two possible modes:
117 NORMAL \- The cluster is fully operational.
119 RECOVERY \- The cluster databases have all been frozen, pausing all services while the cluster awaits a recovery process to complete. A recovery process should finish within seconds. If a cluster is stuck in the RECOVERY state this would indicate a cluster malfunction which needs to be investigated.
123 .nr an-no-space-flag 1
126 \fBRecovery master\fR
129 This is the cluster node that is currently designated as the recovery master. This node is responsible of monitoring the consistency of the cluster and to perform the actual recovery process when reqired.
139 vnn:0 11.1.2.200 OK (THIS NODE)
143 Generation:1362079228
149 Recovery mode:NORMAL (0)
156 This command will "ping" all CTDB daemons in the cluster to verify that they are processing commands correctly.
164 response from 0 time=0.000054 sec (3 clients)
165 response from 1 time=0.000144 sec (2 clients)
166 response from 2 time=0.000105 sec (2 clients)
167 response from 3 time=0.000114 sec (2 clients)
173 This command will display the list of public addresses that are provided by the cluster and which physical node is currently serving this ip.
191 Get the runtime value of a tuneable variable.
193 Example: ctdb getvar MaxRedirectCount
203 .SS "setvar <name> <value>"
205 Set the runtime value of a tuneable variable.
207 Example: ctdb setvar MaxRedirectCount 5
210 List all tuneable variables.
212 Example: ctdb listvars
222 KeepaliveInterval = 2
230 EventScriptTimeout = 20
231 RecoveryGracePeriod = 60
232 RecoveryBanPeriod = 300
238 Collect statistics from the CTDB daemon about how many calls it has served.
240 Example: ctdb statistics
250 client_packets_sent 360489
251 client_packets_recv 360466
252 node_packets_sent 480931
253 node_packets_recv 240120
254 keepalive_packets_sent 4
255 keepalive_packets_recv 3
276 pending_lockwait_calls 0
279 max_call_latency 4.948321 sec
280 max_lockwait_latency 0.000000 sec
284 .SS "statisticsreset"
286 This command is used to clear all statistics counters in a node.
288 Example: ctdb statisticsreset
291 Get the current debug level for the node. the debug level controls what information is written to the log file.
292 .SS "setdebug <debuglevel>"
294 Set the debug level of a node. This is a number between 0 and 9 and controls what information will be written to the logfile.
297 This command will return the process id of the ctdb daemon.
300 This command is used to administratively disable a node in the cluster. A disabled node will still participate in the cluster and host clustered TDB records but its public ip address has been taken over by a different node and it no longer hosts any services.
303 Re\-enable a node that has been administratively disabled.
304 .SS "ban <bantime|0>"
306 Administratively ban a node for bantime seconds. A bantime of 0 means that the node should be permanently banned.
308 A banned node does not participate in the cluster and does not host any records for the clustered TDB. Its ip address has been taken over by an other node and no services are hosted.
310 Nodes are automatically banned if they are the cause of too many cluster recoveries.
313 This command is used to unban a node that has either been administratively banned using the ban command or has been automatically banned by the recovery daemon.
316 This command will shutdown a specific CTDB daemon.
319 This command will trigger the recovery daemon to do a cluster recovery.
320 .SS "killtcp <srcip:port> <dstip:port>"
322 This command will kill the specified TCP connection by issuing a TCP RST to the srcip:port endpoint.
323 .SS "tickle <srcip:port> <dstip:port>"
325 This command will will send a TCP tickle to the source host for the specified TCP connection. A TCP tickle is a TCP ACK packet with an invalid sequence and acknowledge number and will when received by the source host result in it sending an immediate correct ACK back to the other end.
327 TCP tickles are useful to "tickle" clients after a IP failover has occured since this will make the client immediately recognize the TCP connection has been disrupted and that the client will need to reestablish. This greatly speeds up the time it takes for a client to detect and reestablish after an IP failover in the ctdb cluster.
328 .SH "DEBUGGING COMMANDS"
330 These commands are primarily used for CTDB development and testing and should not be used for normal administration.
331 .SS "process\-exists <pid>"
333 This command checks if a specific process exists on the CTDB host. This is mainly used by Samba to check if remote instances of samba are still running or not.
336 This command lists all clustered TDB databases that the CTDB daemon has attahced to.
338 Example: ctdb getdbmap
344 Number of databases:4
345 dbid:0x42fe72c5 name:locking.tdb path:/var/ctdb/locking.tdb.0
346 dbid:0x1421fb78 name:brlock.tdb path:/var/ctdb/brlock.tdb.0
347 dbid:0x17055d90 name:connections.tdb path:/var/ctdb/connections.tdb.0
348 dbid:0xc0bdde6a name:sessionid.tdb path:/var/ctdb/sessionid.tdb.0
354 This command will dump a clustered TDB database to the screen. This is a debugging command.
357 This command returns the monutoring mode of a node. The monitoring mode is either ACTIVE or DISABLED. Normally a node will continously monitor that all other nodes that are expected are in fact connected and that they respond to commands.
359 ACTIVE \- This is the normal mode. The node is actively monitoring all other nodes, both that the transport is connected and also that the node responds to commands. If a node becomes unavailable, it will be marked as DISCONNECTED and a recovery is initiated to restore the cluster.
361 DISABLED \- This node is not monitoring that other nodes are available. In this mode a node failure will not be detected and no recovery will be performed. This mode is useful when for debugging purposes one wants to attach GDB to a ctdb process but wants to prevent the rest of the cluster from marking this node as DISCONNECTED and do a recovery.
362 .SS "setmonmode <0|1>"
364 This command can be used to explicitely disable/enable monitoring mode on a node. The main purpose is if one wants to attach GDB to a running ctdb daemon but wants to prevent the other nodes from marking it as DISCONNECTED and issuing a recovery. To do this, set monitoring mode to 0 on all nodes before attaching with GDB. Remember to set monitoring mode back to 1 afterwards.
365 .SS "attach <dbname>"
367 This is a debugging command. This command will make the CTDB daemon create a new CTDB database and attach to it.
370 This is a debugging command. This command will make the ctdb daemon to write a fill memory allocation map to the log file.
373 This command will lock all the local TDB databases causing clients that are accessing these TDBs such as samba3 to block until the databases are thawed.
375 This is primarily used by the recovery daemon to stop all samba daemons from accessing any databases while the database is recovered and rebuilt.
378 Thaw a previously frozen node.
382 \fI\%http://ctdb.samba.org/\fR
383 .SH "COPYRIGHT/LICENSE"
387 Copyright (C) Andrew Tridgell 2007
388 Copyright (C) Ronnie sahlberg 2007
390 This program is free software; you can redistribute it and/or modify
391 it under the terms of the GNU General Public License as published by
392 the Free Software Foundation; either version 3 of the License, or (at
393 your option) any later version.
395 This program is distributed in the hope that it will be useful, but
396 WITHOUT ANY WARRANTY; without even the implied warranty of
397 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
398 General Public License for more details.
400 You should have received a copy of the GNU General Public License
401 along with this program; if not, write to the Free Software
402 Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.