1 <?xml version="1.0" encoding="iso-8859-1"?>
2 <!DOCTYPE refentry PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
6 <refentrytitle>ctdb</refentrytitle>
7 <manvolnum>1</manvolnum>
8 <refmiscinfo class="source">ctdb</refmiscinfo>
9 <refmiscinfo class="manual">CTDB - clustered TDB database</refmiscinfo>
14 <refname>ctdb</refname>
15 <refpurpose>clustered tdb database management utility</refpurpose>
20 <command>ctdb [ OPTIONS ] COMMAND ...</command>
24 <command>ctdb</command>
25 <arg choice="opt">-n <node></arg>
26 <arg choice="opt">-Y</arg>
27 <arg choice="opt">-t <timeout></arg>
28 <arg choice="opt">-T <timelimit></arg>
29 <arg choice="opt">-? --help</arg>
30 <arg choice="opt">--usage</arg>
31 <arg choice="opt">-d --debug=<INTEGER></arg>
32 <arg choice="opt">--socket=<filename></arg>
37 <refsect1><title>DESCRIPTION</title>
39 ctdb is a utility to view and manage a ctdb cluster.
45 <title>OPTIONS</title>
48 <varlistentry><term>-n <pnn></term>
51 This specifies the physical node number on which to execute the
52 command. Default is to run the command on the daemon running on
56 The physical node number is an integer that describes the node in the
57 cluster. The first node has physical node number 0.
62 <varlistentry><term>-Y</term>
65 Produce output in machine readable form for easier parsing by scripts. Not all commands support this option.
70 <varlistentry><term>-t <timeout></term>
73 How long should ctdb wait for the local ctdb daemon to respond to a command before timing out. Default is 3 seconds.
78 <varlistentry><term>-T <timelimit></term>
81 A limit on how long the ctdb command will run for before it will
82 be aborted. When this timelimit has been exceeded the ctdb command will
88 <varlistentry><term>-? --help</term>
91 Print some help text to the screen.
96 <varlistentry><term>--usage</term>
99 Print useage information to the screen.
104 <varlistentry><term>-d --debug=<debuglevel></term>
107 Change the debug level for the command. Default is 0.
112 <varlistentry><term>--socket=<filename></term>
115 Specify the socketname to use when connecting to the local ctdb
116 daemon. The default is /tmp/ctdb.socket .
119 You only need to specify this parameter if you run multiple ctdb
120 daemons on the same physical host and thus can not use the default
121 name for the domain socket.
130 <refsect1><title>Administrative Commands</title>
132 These are commands used to monitor and administrate a CTDB cluster.
135 <refsect2><title>pnn</title>
137 This command displays the pnn of the current node.
141 <refsect2><title>status</title>
143 This command shows the current status of the ctdb node.
146 <refsect3><title>node status</title>
148 Node status reflects the current status of the node. There are five possible states:
151 OK - This node is fully functional.
154 DISCONNECTED - This node could not be connected through the network and is currently not participating 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.
157 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.
160 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.
163 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.
166 STOPPED - A node that is stopped does not host any public ip addresses,
167 nor is it part of the VNNMAP. A stopped node can not become LVSMASTER,
169 This node does not perticipate in the CTDB cluster but can still be
170 communicated with. I.e. ctdb commands can be sent to it.
173 PARTIALLYONLINE - A node that is partially online participates
174 in a cluster like a node that is ok. Some interfaces to serve
175 public ip addresses are down, but at least one interface is up.
176 See also "ctdb ifaces".
180 <refsect3><title>generation</title>
182 The generation id is a number that indicates the current generation
183 of a cluster instance. Each time a cluster goes through a
184 reconfiguration or a recovery its generation id will be changed.
187 This number does not have any particular meaning other than to keep
188 track of when a cluster has gone through a recovery. It is a random
189 number that represents the current instance of a ctdb cluster
191 CTDBD uses this number internally to be able to tell when commands
192 to operate on the cluster and the databases was issued in a different
193 generation of the cluster, to ensure that commands that operate
194 on the databases will not survive across a cluster database recovery.
195 After a recovery, all old outstanding commands will automatically
199 Sometimes this number will be shown as "INVALID". This only means that
200 the ctdbd daemon has started but it has not yet merged with the cluster through a recovery.
201 All nodes start with generation "INVALID" and are not assigned a real
202 generation id until they have successfully been merged with a cluster
207 <refsect3><title>VNNMAP</title>
209 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.
210 Only nodes that are participating in the vnnmap can become lmaster or dmaster for a database record.
214 <refsect3><title>Recovery mode</title>
216 This is the current recovery mode of the cluster. There are two possible modes:
219 NORMAL - The cluster is fully operational.
222 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.
225 Once the recovery master detects an inconsistency, for example a node
226 becomes disconnected/connected, the recovery daemon will trigger a
227 cluster recovery process, where all databases are remerged across the
228 cluster. When this process starts, the recovery master will first
229 "freeze" all databases to prevent applications such as samba from
230 accessing the databases and it will also mark the recovery mode as
234 When CTDBD starts up, it will start in RECOVERY mode.
235 Once the node has been merged into a cluster and all databases
236 have been recovered, the node mode will change into NORMAL mode
237 and the databases will be "thawed", allowing samba to access the
242 <refsect3><title>Recovery master</title>
244 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.
247 Only one node at a time can be the designated recovery master. Which
248 node is designated the recovery master is decided by an election
249 process in the recovery daemons running on each node.
256 <para>Example output:</para>
257 <screen format="linespecific">
259 pnn:0 11.1.2.200 OK (THIS NODE)
263 Generation:1362079228
269 Recovery mode:NORMAL (0)
274 <refsect2><title>recmaster</title>
276 This command shows the pnn of the node which is currently the recmaster.
280 <refsect2><title>uptime</title>
282 This command shows the uptime for the ctdb daemon. When the last recovery or ip-failover completed and how long it took. If the "duration" is shown as a negative number, this indicates that there is a recovery/failover in progress and it started that many seconds ago.
288 <para>Example output:</para>
289 <screen format="linespecific">
290 Current time of node : Thu Oct 29 10:38:54 2009
291 Ctdbd start time : (000 16:54:28) Wed Oct 28 17:44:26 2009
292 Time of last recovery/failover: (000 16:53:31) Wed Oct 28 17:45:23 2009
293 Duration of last recovery/failover: 2.248552 seconds
297 <refsect2><title>listnodes</title>
299 This command shows lists the ip addresses of all the nodes in the cluster.
303 Example: ctdb listnodes
305 <para>Example output:</para>
306 <screen format="linespecific">
314 <refsect2><title>ping</title>
316 This command will "ping" all CTDB daemons in the cluster to verify that they are processing commands correctly.
324 <screen format="linespecific">
325 response from 0 time=0.000054 sec (3 clients)
326 response from 1 time=0.000144 sec (2 clients)
327 response from 2 time=0.000105 sec (2 clients)
328 response from 3 time=0.000114 sec (2 clients)
332 <refsect2><title>ifaces</title>
334 This command will display the list of network interfaces, which could
335 host public addresses, along with their status.
343 <screen format="linespecific">
345 name:eth5 link:up references:2
346 name:eth4 link:down references:0
347 name:eth3 link:up references:1
348 name:eth2 link:up references:1
351 Example: ctdb ifaces -Y
356 <screen format="linespecific">
357 :Name:LinkStatus:References:
365 <refsect2><title>setifacelink <iface> <status></title>
367 This command will set the status of a network interface.
368 The status needs to be "up" or "down". This is typically
369 used in the 10.interfaces script in the "monitor" event.
372 Example: ctdb setifacelink eth0 up
376 <refsect2><title>ip</title>
378 This command will display the list of public addresses that are provided by the cluster and which physical node is currently serving this ip. By default this command will ONLY show those public addresses that are known to the node itself. To see the full list of all public ips across the cluster you must use "ctdb ip -n all".
386 <screen format="linespecific">
388 172.31.91.82 node[1] active[] available[eth2,eth3] configured[eth2,eth3]
389 172.31.91.83 node[0] active[eth3] available[eth2,eth3] configured[eth2,eth3]
390 172.31.91.84 node[1] active[] available[eth2,eth3] configured[eth2,eth3]
391 172.31.91.85 node[0] active[eth2] available[eth2,eth3] configured[eth2,eth3]
392 172.31.92.82 node[1] active[] available[eth5] configured[eth4,eth5]
393 172.31.92.83 node[0] active[eth5] available[eth5] configured[eth4,eth5]
394 172.31.92.84 node[1] active[] available[eth5] configured[eth4,eth5]
395 172.31.92.85 node[0] active[eth5] available[eth5] configured[eth4,eth5]
403 <screen format="linespecific">
404 :Public IP:Node:ActiveInterface:AvailableInterfaces:ConfiguredInterfaces:
405 :172.31.91.82:1::eth2,eth3:eth2,eth3:
406 :172.31.91.83:0:eth3:eth2,eth3:eth2,eth3:
407 :172.31.91.84:1::eth2,eth3:eth2,eth3:
408 :172.31.91.85:0:eth2:eth2,eth3:eth2,eth3:
409 :172.31.92.82:1::eth5:eth4,eth5:
410 :172.31.92.83:0:eth5:eth5:eth4,eth5:
411 :172.31.92.84:1::eth5:eth4,eth5:
412 :172.31.92.85:0:eth5:eth5:eth4,eth5:
416 <refsect2><title>ipinfo <ip></title>
418 This command will display details about the specified public addresses.
421 Example: ctdb ipinfo 172.31.92.85
426 <screen format="linespecific">
427 Public IP[172.31.92.85] info on node 0
431 Interface[1]: Name:eth4 Link:down References:0
432 Interface[2]: Name:eth5 Link:up References:2 (active)
436 <refsect2><title>scriptstatus</title>
438 This command displays which scripts where run in the previous monitoring cycle and the result of each script. If a script failed with an error, causing the node to become unhealthy, the output from that script is also shown.
441 Example: ctdb scriptstatus
446 <screen format="linespecific">
447 7 scripts were executed last monitoring cycle
448 00.ctdb Status:OK Duration:0.056 Tue Mar 24 18:56:57 2009
449 10.interface Status:OK Duration:0.077 Tue Mar 24 18:56:57 2009
450 11.natgw Status:OK Duration:0.039 Tue Mar 24 18:56:57 2009
451 20.multipathd Status:OK Duration:0.038 Tue Mar 24 18:56:57 2009
452 31.clamd Status:DISABLED
453 40.vsftpd Status:OK Duration:0.045 Tue Mar 24 18:56:57 2009
454 41.httpd Status:OK Duration:0.039 Tue Mar 24 18:56:57 2009
455 50.samba Status:ERROR Duration:0.082 Tue Mar 24 18:56:57 2009
456 OUTPUT:ERROR: Samba tcp port 445 is not responding
460 <refsect2><title>disablescript <script></title>
462 This command is used to disable an eventscript.
465 This will take effect the next time the eventscripts are being executed so it can take a short while until this is reflected in 'scriptstatus'.
469 <refsect2><title>enablescript <script></title>
471 This command is used to enable an eventscript.
474 This will take effect the next time the eventscripts are being executed so it can take a short while until this is reflected in 'scriptstatus'.
478 <refsect2><title>getvar <name></title>
480 Get the runtime value of a tuneable variable.
483 Example: ctdb getvar MaxRedirectCount
488 <screen format="linespecific">
493 <refsect2><title>setvar <name> <value></title>
495 Set the runtime value of a tuneable variable.
498 Example: ctdb setvar MaxRedirectCount 5
502 <refsect2><title>listvars</title>
504 List all tuneable variables.
507 Example: ctdb listvars
512 <screen format="linespecific">
514 SeqnumInterval = 1000
517 KeepaliveInterval = 5
525 TickleUpdateInterval = 20
526 EventScriptTimeout = 30
527 EventScriptBanCount = 10
528 EventScriptUnhealthyOnTimeout = 0
529 RecoveryGracePeriod = 120
530 RecoveryBanPeriod = 300
531 DatabaseHashSize = 10000
533 RerecoveryTimeout = 10
536 DisableWhenUnhealthy = 0
537 ReclockPingPeriod = 60
539 VerboseMemoryNames = 0
543 RecLockLatencyMs = 1000
544 RecoveryDropAllIPs = 60
545 VerifyRecoveryLock = 1
546 VacuumDefaultInterval = 300
547 VacuumMaxRunTime = 30
550 VacuumMinInterval = 60
551 VacuumMaxInterval = 600
552 MaxQueueDropMsg = 1000
554 AllowUnhealthyDBRead = 0
558 <refsect2><title>lvsmaster</title>
560 This command shows which node is currently the LVSMASTER. The
561 LVSMASTER is the node in the cluster which drives the LVS system and
562 which receives all incoming traffic from clients.
565 LVS is the mode where the entire CTDB/Samba cluster uses a single
566 ip address for the entire cluster. In this mode all clients connect to
567 one specific node which will then multiplex/loadbalance the clients
568 evenly onto the other nodes in the cluster. This is an alternative to using
569 public ip addresses. See the manpage for ctdbd for more information
574 <refsect2><title>lvs</title>
576 This command shows which nodes in the cluster are currently active in the
577 LVS configuration. I.e. which nodes we are currently loadbalancing
578 the single ip address across.
582 LVS will by default only loadbalance across those nodes that are both
583 LVS capable and also HEALTHY. Except if all nodes are UNHEALTHY in which
584 case LVS will loadbalance across all UNHEALTHY nodes as well.
585 LVS will never use nodes that are DISCONNECTED, STOPPED, BANNED or
592 <screen format="linespecific">
600 <refsect2><title>getcapabilities</title>
602 This command shows the capabilities of the current node.
603 Please see manpage for ctdbd for a full list of all capabilities and
604 more detailed description.
608 RECMASTER and LMASTER capabilities are primarily used when CTDBD
609 is used to create a cluster spanning across WAN links. In which case
610 ctdbd acts as a WAN accelerator.
614 LVS capabile means that the node is participating in LVS, a mode
615 where the entire CTDB cluster uses one single ip address for the
616 entire cluster instead of using public ip address failover.
617 This is an alternative to using a loadbalancing layer-4 switch.
623 <screen format="linespecific">
631 <refsect2><title>statistics</title>
633 Collect statistics from the CTDB daemon about how many calls it has served.
636 Example: ctdb statistics
641 <screen format="linespecific">
646 client_packets_sent 360489
647 client_packets_recv 360466
648 node_packets_sent 480931
649 node_packets_recv 240120
650 keepalive_packets_sent 4
651 keepalive_packets_recv 3
672 pending_lockwait_calls 0
675 max_call_latency 4.948321 sec
676 max_lockwait_latency 0.000000 sec
680 <refsect2><title>statisticsreset</title>
682 This command is used to clear all statistics counters in a node.
685 Example: ctdb statisticsreset
689 <refsect2><title>getreclock</title>
691 This command is used to show the filename of the reclock file that is used.
697 <screen format="linespecific">
698 Reclock file:/gpfs/.ctdb/shared
703 <refsect2><title>setreclock [filename]</title>
705 This command is used to modify, or clear, the file that is used as the reclock file at runtime. When this command is used, the reclock file checks are disabled. To re-enable the checks the administrator needs to activate the "VerifyRecoveryLock" tunable using "ctdb setvar".
709 If run with no parameter this will remove the reclock file completely. If run with a parameter the parameter specifies the new filename to use for the recovery lock.
713 This command only affects the runtime settings of a ctdb node and will be lost when ctdb is restarted. For persistent changes to the reclock file setting you must edit /etc/sysconfig/ctdb.
719 <refsect2><title>getdebug</title>
721 Get the current debug level for the node. the debug level controls what information is written to the log file.
724 The debug levels are mapped to the corresponding syslog levels.
725 When a debug level is set, only those messages at that level and higher
726 levels will be printed.
729 The list of debug levels from highest to lowest are :
732 EMERG ALERT CRIT ERR WARNING NOTICE INFO DEBUG
736 <refsect2><title>setdebug <debuglevel></title>
738 Set the debug level of a node. This controls what information will be logged.
741 The debuglevel is one of EMERG ALERT CRIT ERR WARNING NOTICE INFO DEBUG
745 <refsect2><title>getpid</title>
747 This command will return the process id of the ctdb daemon.
751 <refsect2><title>disable</title>
753 This command is used to administratively disable a node in the cluster.
754 A disabled node will still participate in the cluster and host
755 clustered TDB records but its public ip address has been taken over by
756 a different node and it no longer hosts any services.
760 <refsect2><title>enable</title>
762 Re-enable a node that has been administratively disabled.
766 <refsect2><title>stop</title>
768 This command is used to administratively STOP a node in the cluster.
769 A STOPPED node is connected to the cluster but will not host any
770 public ip addresse, nor does it participate in the VNNMAP.
771 The difference between a DISABLED node and a STOPPED node is that
772 a STOPPED node does not host any parts of the database which means
773 that a recovery is required to stop/continue nodes.
777 <refsect2><title>continue</title>
779 Re-start a node that has been administratively stopped.
783 <refsect2><title>addip <public_ip/mask> <iface></title>
785 This command is used to add a new public ip to a node during runtime.
786 This allows public addresses to be added to a cluster without having
787 to restart the ctdb daemons.
790 Note that this only updates the runtime instance of ctdb. Any changes will be lost next time ctdb is restarted and the public addresses file is re-read.
791 If you want this change to be permanent you must also update the public addresses file manually.
795 <refsect2><title>delip <public_ip></title>
797 This command is used to remove a public ip from a node during runtime.
798 If this public ip is currently hosted by the node it being removed from, the ip will first be failed over to another node, if possible, before it is removed.
801 Note that this only updates the runtime instance of ctdb. Any changes will be lost next time ctdb is restarted and the public addresses file is re-read.
802 If you want this change to be permanent you must also update the public addresses file manually.
806 <refsect2><title>moveip <public_ip> <node></title>
808 This command can be used to manually fail a public ip address to a
812 In order to manually override the "automatic" distribution of public
813 ip addresses that ctdb normally provides, this command only works
814 when you have changed the tunables for the daemon to:
824 <refsect2><title>shutdown</title>
826 This command will shutdown a specific CTDB daemon.
830 <refsect2><title>recover</title>
832 This command will trigger the recovery daemon to do a cluster
837 <refsect2><title>ipreallocate</title>
839 This command will force the recovery master to perform a full ip reallocation process and redistribute all ip addresses. This is useful to "reset" the allocations back to its default state if they have been changed using the "moveip" command. While a "recover" will also perform this reallocation, a recovery is much more hevyweight since it will also rebuild all the databases.
843 <refsect2><title>setlmasterrole <on|off></title>
845 This command is used ot enable/disable the LMASTER capability for a node at runtime. This capability determines whether or not a node can be used as an LMASTER for records in the database. A node that does not have the LMASTER capability will not show up in the vnnmap.
849 Nodes will by default have this capability, but it can be stripped off nodes by the setting in the sysconfig file or by using this command.
852 Once this setting has been enabled/disabled, you need to perform a recovery for it to take effect.
855 See also "ctdb getcapabilities"
859 <refsect2><title>setrecmasterrole <on|off></title>
861 This command is used ot enable/disable the RECMASTER capability for a node at runtime. This capability determines whether or not a node can be used as an RECMASTER for the cluster. A node that does not have the RECMASTER capability can not win a recmaster election. A node that already is the recmaster for the cluster when the capability is stripped off the node will remain the recmaster until the next cluster election.
865 Nodes will by default have this capability, but it can be stripped off nodes by the setting in the sysconfig file or by using this command.
868 See also "ctdb getcapabilities"
872 <refsect2><title>killtcp <srcip:port> <dstip:port></title>
874 This command will kill the specified TCP connection by issuing a
875 TCP RST to the srcip:port endpoint. This is a command used by the
880 <refsect2><title>gratiousarp <ip> <interface></title>
882 This command will send out a gratious arp for the specified interface
883 through the specified interface. This command is mainly used by the
888 <refsect2><title>reloadnodes</title>
890 This command is used when adding new nodes, or removing existing nodes from an existing cluster.
893 Procedure to add a node:
896 1, To expand an existing cluster, first ensure with 'ctdb status' that
897 all nodes are up and running and that they are all healthy.
898 Do not try to expand a cluster unless it is completely healthy!
901 2, On all nodes, edit /etc/ctdb/nodes and add the new node as the last
902 entry to the file. The new node MUST be added to the end of this file!
905 3, Verify that all the nodes have identical /etc/ctdb/nodes files after you edited them and added the new node!
908 4, Run 'ctdb reloadnodes' to force all nodes to reload the nodesfile.
911 5, Use 'ctdb status' on all nodes and verify that they now show the additional node.
914 6, Install and configure the new node and bring it online.
917 Procedure to remove a node:
920 1, To remove a node from an existing cluster, first ensure with 'ctdb status' that
921 all nodes, except the node to be deleted, are up and running and that they are all healthy.
922 Do not try to remove a node from a cluster unless the cluster is completely healthy!
925 2, Shutdown and poerwoff the node to be removed.
928 3, On all other nodes, edit the /etc/ctdb/nodes file and comment out the node to be removed. Do not delete the line for that node, just comment it out by adding a '#' at the beginning of the line.
931 4, Run 'ctdb reloadnodes' to force all nodes to reload the nodesfile.
934 5, Use 'ctdb status' on all nodes and verify that the deleted node no longer shows up in the list..
941 <refsect2><title>tickle <srcip:port> <dstip:port></title>
943 This command will will send a TCP tickle to the source host for the
944 specified TCP connection.
945 A TCP tickle is a TCP ACK packet with an invalid sequence and
946 acknowledge number and will when received by the source host result
947 in it sending an immediate correct ACK back to the other end.
950 TCP tickles are useful to "tickle" clients after a IP failover has
951 occured since this will make the client immediately recognize the
952 TCP connection has been disrupted and that the client will need
953 to reestablish. This greatly speeds up the time it takes for a client
954 to detect and reestablish after an IP failover in the ctdb cluster.
958 <refsect2><title>gettickles <ip></title>
960 This command is used to show which TCP connections are registered with
961 CTDB to be "tickled" if there is a failover.
964 <refsect2><title>repack [max_freelist]</title>
966 Over time, when records are created and deleted in a TDB, the TDB list of free space will become fragmented. This can lead to a slowdown in accessing TDB records.
967 This command is used to defragment a TDB database and pruning the freelist.
971 If [max_freelist] is specified, then a database will only be repacked if it has more than this number of entries in the freelist.
974 During repacking of the database, the entire TDB database will be locked to prevent writes. If samba tries to write to a record in the database during a repack operation, samba will block until the repacking has completed.
978 This command can be disruptive and can cause samba to block for the duration of the repack operation. In general, a repack operation will take less than one second to complete.
982 A repack operation will only defragment the local TDB copy of the CTDB database. You need to run this command on all of the nodes to repack a CTDB database completely.
986 Example: ctdb repack 1000
990 By default, this operation is issued from the 00.ctdb event script every 5 minutes.
995 <refsect2><title>vacuum [max_records]</title>
997 Over time CTDB databases will fill up with empty deleted records which will lead to a progressive slow down of CTDB database access.
998 This command is used to prune all databases and delete all empty records from the cluster.
1002 By default, vacuum will delete all empty records from all databases.
1003 If [max_records] is specified, the command will only delete the first
1004 [max_records] empty records for each database.
1008 Vacuum only deletes records where the local node is the lmaster.
1009 To delete all records from the entire cluster you need to run a vacuum from each node.
1011 This command is not disruptive. Samba is unaffected and will still be able to read/write records normally while the database is being vacuumed.
1015 Example: ctdb vacuum
1019 By default, this operation is issued from the 00.ctdb event script every 5 minutes.
1023 <refsect2><title>backupdb <dbname> <file></title>
1025 This command can be used to copy the entire content of a database out to a file. This file can later be read back into ctdb using the restoredb command.
1026 This is mainly useful for backing up persistent databases such as secrets.tdb and similar.
1030 <refsect2><title>restoredb <file> [dbname]</title>
1032 This command restores a persistent database that was previously backed up using backupdb.
1033 By default the data will be restored back into the same database as
1034 it was created from. By specifying dbname you can restore the data
1035 into a different database.
1039 <refsect2><title>wipedb <dbname></title>
1041 This command can be used to remove all content of a database.
1047 <refsect2><title>getlog <level></title>
1049 In addition to the normal loggign to a log file,
1050 CTDBD also keeps a in-memory ringbuffer containing the most recent
1051 log entries for all log levels (except DEBUG).
1053 This is useful since it allows for keeping continous logs to a file
1054 at a reasonable non-verbose level, but shortly after an incident has
1055 occured, a much more detailed log can be pulled from memory. This
1056 can allow you to avoid having to reproduce an issue due to the
1057 on-disk logs being of insufficient detail.
1059 This command extracts all messages of level or lower log level from
1060 memory and prints it to the screen.
1064 <refsect2><title>clearlog</title>
1066 This command clears the in-memory logging ringbuffer.
1071 <refsect1><title>Debugging Commands</title>
1073 These commands are primarily used for CTDB development and testing and
1074 should not be used for normal administration.
1076 <refsect2><title>process-exists <pid></title>
1078 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.
1082 <refsect2><title>getdbmap</title>
1084 This command lists all clustered TDB databases that the CTDB daemon has attached to. Some databases are flagged as PERSISTENT, this means that the database stores data persistently and the data will remain across reboots. One example of such a database is secrets.tdb where information about how the cluster was joined to the domain is stored.
1087 If a PERSISTENT database is not in a healthy state the database is
1088 flagged as UNHEALTHY. If there's at least one completely healthy node running in
1089 the cluster, it's possible that the content is restored by a recovery
1090 run automaticly. Otherwise an administrator needs to analyze the
1094 See also "ctdb getdbstatus", "ctdb backupdb", "ctdb restoredb",
1095 "ctdb dumpbackup", "ctdb wipedb", "ctdb setvar AllowUnhealthyDBRead 1"
1096 and (if samba or tdb-utils are installed) "tdbtool check".
1099 Most databases are not persistent and only store the state information that the currently running samba daemons need. These databases are always wiped when ctdb/samba starts and when a node is rebooted.
1102 Example: ctdb getdbmap
1107 <screen format="linespecific">
1108 Number of databases:10
1109 dbid:0x435d3410 name:notify.tdb path:/var/ctdb/notify.tdb.0
1110 dbid:0x42fe72c5 name:locking.tdb path:/var/ctdb/locking.tdb.0
1111 dbid:0x1421fb78 name:brlock.tdb path:/var/ctdb/brlock.tdb.0
1112 dbid:0x17055d90 name:connections.tdb path:/var/ctdb/connections.tdb.0
1113 dbid:0xc0bdde6a name:sessionid.tdb path:/var/ctdb/sessionid.tdb.0
1114 dbid:0x122224da name:test.tdb path:/var/ctdb/test.tdb.0
1115 dbid:0x2672a57f name:idmap2.tdb path:/var/ctdb/persistent/idmap2.tdb.0 PERSISTENT
1116 dbid:0xb775fff6 name:secrets.tdb path:/var/ctdb/persistent/secrets.tdb.0 PERSISTENT
1117 dbid:0xe98e08b6 name:group_mapping.tdb path:/var/ctdb/persistent/group_mapping.tdb.0 PERSISTENT
1118 dbid:0x7bbbd26c name:passdb.tdb path:/var/ctdb/persistent/passdb.tdb.0 PERSISTENT
1121 Example output for an unhealthy database:
1123 <screen format="linespecific">
1124 Number of databases:1
1125 dbid:0xb775fff6 name:secrets.tdb path:/var/ctdb/persistent/secrets.tdb.0 PERSISTENT UNHEALTHY
1129 Example output for a healthy database as machinereadable output -Y:
1131 <screen format="linespecific">
1132 :ID:Name:Path:Persistent:Unhealthy:
1133 :0x7bbbd26c:passdb.tdb:/var/ctdb/persistent/passdb.tdb.0:1:0:
1137 <refsect2><title>getdbstatus <dbname></title>
1139 This command displays more details about a database.
1142 Example: ctdb getdbstatus test.tdb.0
1147 <screen format="linespecific">
1150 path: /var/ctdb/test.tdb.0
1155 Example: ctdb getdbstatus registry.tdb (with a corrupted TDB)
1160 <screen format="linespecific">
1163 path: /var/ctdb/persistent/registry.tdb.0
1165 HEALTH: NO-HEALTHY-NODES - ERROR - Backup of corrupted TDB in '/var/ctdb/persistent/registry.tdb.0.corrupted.20091208091949.0Z'
1169 <refsect2><title>catdb <dbname></title>
1171 This command will dump a clustered TDB database to the screen. This is a debugging command.
1175 <refsect2><title>dumpdbbackup <backup-file></title>
1177 This command will dump the content of database backup to the screen
1178 (similar to ctdb catdb). This is a debugging command.
1182 <refsect2><title>getmonmode</title>
1184 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.
1187 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.
1190 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.
1195 <refsect2><title>setmonmode <0|1></title>
1197 This command can be used to explicitly 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.
1201 <refsect2><title>attach <dbname></title>
1203 This is a debugging command. This command will make the CTDB daemon create a new CTDB database and attach to it.
1207 <refsect2><title>dumpmemory</title>
1209 This is a debugging command. This command will make the ctdb
1210 daemon to write a fill memory allocation map to standard output.
1214 <refsect2><title>rddumpmemory</title>
1216 This is a debugging command. This command will dump the talloc memory
1217 allocation tree for the recovery daemon to standard output.
1221 <refsect2><title>thaw</title>
1223 Thaw a previously frozen node.
1228 <refsect2><title>eventscript <arguments></title>
1230 This is a debugging command. This command can be used to manually
1231 invoke and run the eventscritps with arbitrary arguments.
1235 <refsect2><title>ban <bantime|0></title>
1237 Administratively ban a node for bantime seconds. A bantime of 0 means that the node should be permanently banned.
1240 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 another node and no services are hosted.
1243 Nodes are automatically banned if they are the cause of too many
1248 <refsect2><title>unban</title>
1250 This command is used to unban a node that has either been
1251 administratively banned using the ban command or has been automatically
1252 banned by the recovery daemon.
1259 <refsect1><title>SEE ALSO</title>
1262 <ulink url="http://ctdb.samba.org/"/>
1265 <refsect1><title>COPYRIGHT/LICENSE</title>
1267 Copyright (C) Andrew Tridgell 2007
1268 Copyright (C) Ronnie sahlberg 2007
1270 This program is free software; you can redistribute it and/or modify
1271 it under the terms of the GNU General Public License as published by
1272 the Free Software Foundation; either version 3 of the License, or (at
1273 your option) any later version.
1275 This program is distributed in the hope that it will be useful, but
1276 WITHOUT ANY WARRANTY; without even the implied warranty of
1277 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
1278 General Public License for more details.
1280 You should have received a copy of the GNU General Public License
1281 along with this program; if not, see http://www.gnu.org/licenses/.