1 <?xml version="1.0" encoding="iso-8859-1"?>
3 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
4 "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
10 This documentation was written by
19 <holder>Andrew Tridgell</holder>
20 <holder>Ronnie Sahlberg</holder>
24 This program is free software; you can redistribute it and/or
25 modify it under the terms of the GNU General Public License as
26 published by the Free Software Foundation; either version 3 of
27 the License, or (at your option) any later version.
30 This program is distributed in the hope that it will be
31 useful, but WITHOUT ANY WARRANTY; without even the implied
32 warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR
33 PURPOSE. See the GNU General Public License for more details.
36 You should have received a copy of the GNU General Public
37 License along with this program; if not, see
38 <ulink url="http://www.gnu.org/licenses"/>.
44 <refentrytitle>ctdb</refentrytitle>
45 <manvolnum>1</manvolnum>
46 <refmiscinfo class="source">ctdb</refmiscinfo>
47 <refmiscinfo class="manual">CTDB - clustered TDB database</refmiscinfo>
51 <refname>ctdb</refname>
52 <refpurpose>CTDB management utility</refpurpose>
57 <command>ctdb</command>
58 <arg rep="repeat"><replaceable>OPTION</replaceable></arg>
59 <arg choice="req"><replaceable>COMMAND</replaceable></arg>
60 <arg choice="opt"><replaceable>COMMAND-ARGS</replaceable></arg>
65 <title>DESCRIPTION</title>
67 ctdb is a utility to view and manage a CTDB cluster.
71 The following terms are used when referring to nodes in a
78 Physical Node Number. The physical node number is an
79 integer that describes the node in the cluster. The
80 first node has physical node number 0. in a cluster.
88 This is either a single PNN, a comma-separate list of PNNs
97 Commands that reference a database use the following terms:
103 This is either a database name, such as
104 <filename>locking.tdb</filename> or a database ID such
113 A space separated list of at least one
114 <parameter>DB</parameter>.
123 <title>OPTIONS</title>
126 <varlistentry><term>-n <parameter>PNN-LIST</parameter></term>
129 The nodes specified by PNN-LIST should be queried for the
130 requested information. Default is to query the daemon
131 running on the local host.
136 <varlistentry><term>-Y</term>
139 Produce output in machine readable form for easier parsing
140 by scripts. This uses a field delimiter of ':'. Not all
141 commands support this option.
146 <varlistentry><term>-x <parameter>SEPARATOR</parameter></term>
149 Use SEPARATOR to delimit fields in machine readable output.
155 <varlistentry><term>-X</term>
158 Produce output in machine readable form for easier parsing
159 by scripts. This uses a field delimiter of '|'. Not all
160 commands support this option.
163 This is equivalent to "-x|" and avoids some shell quoting
169 <varlistentry><term>-t <parameter>TIMEOUT</parameter></term>
172 Indicates that ctdb should wait up to TIMEOUT seconds for
173 a response to most commands sent to the CTDB daemon. The
174 default is 10 seconds.
179 <varlistentry><term>-T <parameter>TIMELIMIT</parameter></term>
182 Indicates that TIMELIMIT is the maximum run time (in
183 seconds) for the ctdb command. When TIMELIMIT is exceeded
184 the ctdb command will terminate with an error. The default
190 <varlistentry><term>-? --help</term>
193 Print some help text to the screen.
198 <varlistentry><term>--usage</term>
201 Print useage information to the screen.
206 <varlistentry><term>-d --debug=<parameter>DEBUGLEVEL</parameter></term>
209 Change the debug level for the command. Default is NOTICE (2).
214 <varlistentry><term>--socket=<parameter>FILENAME</parameter></term>
217 Specify that FILENAME is the name of the Unix domain
218 socket to use when connecting to the local CTDB
219 daemon. The default is
220 <filename>/usr/local/var/run/ctdb/ctdbd.socket</filename>.
229 <title>ADMINISTRATIVE COMMANDS</title>
231 These are commands used to monitor and administer a CTDB cluster.
237 This command displays the PNN of the current node.
242 <title>status</title>
244 This command shows the current status of all CTDB nodes based
245 on information from the queried node.
249 Note: If the the queried node is INACTIVE then the status
250 might not be current.
254 <title>Node status</title>
256 This includes the number of physical nodes and the status of
257 each node. See <citerefentry><refentrytitle>ctdb</refentrytitle>
258 <manvolnum>7</manvolnum></citerefentry> for information
264 <title>Generation</title>
266 The generation id is a number that indicates the current generation
267 of a cluster instance. Each time a cluster goes through a
268 reconfiguration or a recovery its generation id will be changed.
271 This number does not have any particular meaning other than
272 to keep track of when a cluster has gone through a
273 recovery. It is a random number that represents the current
274 instance of a ctdb cluster and its databases. The CTDB
275 daemon uses this number internally to be able to tell when
276 commands to operate on the cluster and the databases was
277 issued in a different generation of the cluster, to ensure
278 that commands that operate on the databases will not survive
279 across a cluster database recovery. After a recovery, all
280 old outstanding commands will automatically become invalid.
283 Sometimes this number will be shown as "INVALID". This only means that
284 the ctdbd daemon has started but it has not yet merged with the cluster through a recovery.
285 All nodes start with generation "INVALID" and are not assigned a real
286 generation id until they have successfully been merged with a cluster
292 <title>Virtual Node Number (VNN) map</title>
294 Consists of the number of virtual nodes and mapping from
295 virtual node numbers to physical node numbers. Virtual
296 nodes host CTDB databases. Only nodes that are
297 participating in the VNN map can become lmaster or dmaster
298 for database records.
303 <title>Recovery mode</title>
305 This is the current recovery mode of the cluster. There are two possible modes:
308 NORMAL - The cluster is fully operational.
311 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.
314 Once the recovery master detects an inconsistency, for example a node
315 becomes disconnected/connected, the recovery daemon will trigger a
316 cluster recovery process, where all databases are remerged across the
317 cluster. When this process starts, the recovery master will first
318 "freeze" all databases to prevent applications such as samba from
319 accessing the databases and it will also mark the recovery mode as
323 When the CTDB daemon starts up, it will start in RECOVERY
324 mode. Once the node has been merged into a cluster and all
325 databases have been recovered, the node mode will change into
326 NORMAL mode and the databases will be "thawed", allowing samba
327 to access the databases again.
331 <title>Recovery master</title>
333 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.
336 Only one node at a time can be the designated recovery master. Which
337 node is designated the recovery master is decided by an election
338 process in the recovery daemons running on each node.
343 <title>Example</title>
347 pnn:0 192.168.2.200 OK (THIS NODE)
348 pnn:1 192.168.2.201 OK
349 pnn:2 192.168.2.202 OK
350 pnn:3 192.168.2.203 OK
351 Generation:1362079228
357 Recovery mode:NORMAL (0)
364 <title>nodestatus <optional><parameter>PNN-LIST</parameter></optional></title>
366 This command is similar to the <command>status</command>
367 command. It displays the "node status" subset of output. The
368 main differences are:
374 The exit code is the bitwise-OR of the flags for each
375 specified node, while <command>ctdb status</command> exits
376 with 0 if it was able to retrieve status for all nodes.
382 <command>ctdb status</command> provides status information
383 for all nodes. <command>ctdb nodestatus</command>
384 defaults to providing status for only the current node.
385 If PNN-LIST is provided then status is given for
386 the indicated node(s).
392 A common invocation in scripts is <command>ctdb nodestatus
393 all</command> to check whether all nodes in a cluster are
398 <title>Example</title>
401 pnn:0 10.0.0.30 OK (THIS NODE)
403 # ctdb nodestatus all
405 pnn:0 10.0.0.30 OK (THIS NODE)
412 <title>recmaster</title>
414 This command shows the pnn of the node which is currently the recmaster.
418 Note: If the the queried node is INACTIVE then the status
419 might not be current.
424 <title>uptime</title>
426 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.
430 <title>Example</title>
433 Current time of node : Thu Oct 29 10:38:54 2009
434 Ctdbd start time : (000 16:54:28) Wed Oct 28 17:44:26 2009
435 Time of last recovery/failover: (000 16:53:31) Wed Oct 28 17:45:23 2009
436 Duration of last recovery/failover: 2.248552 seconds
442 <title>listnodes</title>
444 This command shows lists the ip addresses of all the nodes in the cluster.
448 <title>Example</title>
460 <title>natgw {master|list|status}</title>
462 This command shows different aspects of NAT gateway status.
463 For an overview of CTDB's NAT gateway functionality please see
464 the <citetitle>NAT GATEWAY</citetitle> section in
465 <citerefentry><refentrytitle>ctdb</refentrytitle>
466 <manvolnum>7</manvolnum></citerefentry>.
474 Show the PNN and private IP address of the current NAT
489 List the private IP addresses of nodes in the current
490 NAT gateway group, annotating the master node.
507 List the nodes in the current NAT gateway group and
514 pnn:0 192.168.2.200 UNHEALTHY (THIS NODE)
515 pnn:1 192.168.2.201 OK
516 pnn:2 192.168.2.202 OK
517 pnn:3 192.168.2.203 OK
527 This command will "ping" specified CTDB nodes in the cluster
528 to verify that they are running.
531 <title>Example</title>
534 response from 0 time=0.000054 sec (3 clients)
540 <title>ifaces</title>
542 This command will display the list of network interfaces, which could
543 host public addresses, along with their status.
546 <title>Example</title>
550 name:eth5 link:up references:2
551 name:eth4 link:down references:0
552 name:eth3 link:up references:1
553 name:eth2 link:up references:1
556 |Name|LinkStatus|References|
568 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 all".
571 <title>Example</title>
575 172.31.91.82 node[1] active[] available[eth2,eth3] configured[eth2,eth3]
576 172.31.91.83 node[0] active[eth3] available[eth2,eth3] configured[eth2,eth3]
577 172.31.91.84 node[1] active[] available[eth2,eth3] configured[eth2,eth3]
578 172.31.91.85 node[0] active[eth2] available[eth2,eth3] configured[eth2,eth3]
579 172.31.92.82 node[1] active[] available[eth5] configured[eth4,eth5]
580 172.31.92.83 node[0] active[eth5] available[eth5] configured[eth4,eth5]
581 172.31.92.84 node[1] active[] available[eth5] configured[eth4,eth5]
582 172.31.92.85 node[0] active[eth5] available[eth5] configured[eth4,eth5]
585 |Public IP|Node|ActiveInterface|AvailableInterfaces|ConfiguredInterfaces|
586 |172.31.91.82|1||eth2,eth3|eth2,eth3|
587 |172.31.91.83|0|eth3|eth2,eth3|eth2,eth3|
588 |172.31.91.84|1||eth2,eth3|eth2,eth3|
589 |172.31.91.85|0|eth2|eth2,eth3|eth2,eth3|
590 |172.31.92.82|1||eth5|eth4,eth5|
591 |172.31.92.83|0|eth5|eth5|eth4,eth5|
592 |172.31.92.84|1||eth5|eth4,eth5|
593 |172.31.92.85|0|eth5|eth5|eth4,eth5|
599 <title>ipinfo <parameter>IP</parameter></title>
601 This command will display details about the specified public addresses.
604 <title>Example</title>
606 # ctdb ipinfo 172.31.92.85
607 Public IP[172.31.92.85] info on node 0
611 Interface[1]: Name:eth4 Link:down References:0
612 Interface[2]: Name:eth5 Link:up References:2 (active)
618 <title>scriptstatus</title>
620 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.
623 <title>Example</title>
626 7 scripts were executed last monitoring cycle
627 00.ctdb Status:OK Duration:0.056 Tue Mar 24 18:56:57 2009
628 10.interface Status:OK Duration:0.077 Tue Mar 24 18:56:57 2009
629 11.natgw Status:OK Duration:0.039 Tue Mar 24 18:56:57 2009
630 20.multipathd Status:OK Duration:0.038 Tue Mar 24 18:56:57 2009
631 31.clamd Status:DISABLED
632 40.vsftpd Status:OK Duration:0.045 Tue Mar 24 18:56:57 2009
633 41.httpd Status:OK Duration:0.039 Tue Mar 24 18:56:57 2009
634 50.samba Status:ERROR Duration:0.082 Tue Mar 24 18:56:57 2009
635 OUTPUT:ERROR: Samba tcp port 445 is not responding
641 <title>disablescript <parameter>SCRIPT</parameter></title>
643 This command is used to disable an eventscript.
646 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'.
651 <title>enablescript <parameter>SCRIPT</parameter></title>
653 This command is used to enable an eventscript.
656 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'.
661 <title>listvars</title>
663 List all tuneable variables, except the values of the obsolete tunables
664 like VacuumMinInterval. The obsolete tunables can be retrieved only
665 explicitly with the "ctdb getvar" command.
668 <title>Example</title>
671 SeqnumInterval = 1000
674 KeepaliveInterval = 5
681 TickleUpdateInterval = 20
682 EventScriptTimeout = 30
683 MonitorTimeoutCount = 20
684 RecoveryGracePeriod = 120
685 RecoveryBanPeriod = 300
686 DatabaseHashSize = 100001
688 RerecoveryTimeout = 10
693 DisableIPFailover = 0
694 VerboseMemoryNames = 0
698 RecLockLatencyMs = 1000
699 RecoveryDropAllIPs = 120
701 VacuumMaxRunTime = 120
704 VacuumFastPathCount = 60
705 MaxQueueDropMsg = 1000000
706 AllowUnhealthyDBRead = 0
707 StatHistoryInterval = 1
708 DeferredAttachTO = 120
709 AllowClientDBAttach = 1
710 RecoverPDBBySeqNum = 1
711 DeferredRebalanceOnNodeAdd = 300
713 HopcountMakeSticky = 50
717 DBRecordCountWarn = 100000
718 DBRecordSizeWarn = 10000000
719 DBSizeWarn = 100000000
720 PullDBPreallocation = 10485760
721 NoIPHostOnAllDisabled = 0
722 Samba3AvoidDeadlocks = 0
724 LockProcessesPerDB = 200
730 <title>getvar <parameter>NAME</parameter></title>
732 Get the runtime value of a tuneable variable.
735 <title>Example</title>
737 # ctdb getvar MonitorInterval
744 <title>setvar <parameter>NAME</parameter> <parameter>VALUE</parameter></title>
746 Set the runtime value of a tuneable variable.
749 <title>Example</title>
751 # ctdb setvar MonitorInterval 20
757 <title>lvs {master|list|status}</title>
759 This command shows different aspects of LVS status. For an
760 overview of CTDB's LVS functionality please see the
761 <citetitle>LVS</citetitle> section in
762 <citerefentry><refentrytitle>ctdb</refentrytitle>
763 <manvolnum>7</manvolnum></citerefentry>.
771 Shows the PNN of the current LVS master node.
785 Lists the currently usable LVS nodes.
800 List the nodes in the current LVS group and their status.
806 pnn:0 10.0.0.11 UNHEALTHY (THIS NODE)
807 pnn:1 10.0.0.12 UNHEALTHY
819 <title>getcapabilities</title>
822 This command shows the capabilities of the current node. See
823 the <citetitle>CAPABILITIES</citetitle> section in
824 <citerefentry><refentrytitle>ctdb</refentrytitle>
825 <manvolnum>7</manvolnum></citerefentry> for more details.
839 <title>statistics</title>
841 Collect statistics from the CTDB daemon about
842 how many calls it has served. Information about
843 various fields in statistics can be found in
844 <citerefentry><refentrytitle>ctdb-statistics</refentrytitle>
845 <manvolnum>7</manvolnum></citerefentry>.
848 <title>Example</title>
852 Current time of statistics : Tue Mar 8 15:18:51 2016
853 Statistics collected since : (003 21:31:32) Fri Mar 4 17:47:19 2016
858 client_packets_sent 8170534
859 client_packets_recv 7166132
860 node_packets_sent 16549998
861 node_packets_recv 5244418
862 keepalive_packets_sent 201969
863 keepalive_packets_recv 201969
872 reply_control 6831284
889 pending_childwrite_calls 0
892 total_ro_delegations 0
894 hop_count_buckets: 8 5 0 0 0 0 0 0 0 0 0 0 0 0 0 0
895 lock_buckets: 0 0 8 0 0 0 0 0 0 0 0 0 0 0 0 0
896 locks_latency MIN/AVG/MAX 0.010005/0.010418/0.011010 sec out of 8
897 reclock_ctdbd MIN/AVG/MAX 0.002538/0.002538/0.002538 sec out of 1
898 reclock_recd MIN/AVG/MAX 0.000000/0.000000/0.000000 sec out of 0
899 call_latency MIN/AVG/MAX 0.000044/0.002142/0.011702 sec out of 15
900 childwrite_latency MIN/AVG/MAX 0.000000/0.000000/0.000000 sec out of 0
906 <title>statisticsreset</title>
908 This command is used to clear all statistics counters in a node.
911 Example: ctdb statisticsreset
916 <title>dbstatistics <parameter>DB</parameter></title>
918 Display statistics about the database DB. Information
919 about various fields in dbstatistics can be found in
920 <citerefentry><refentrytitle>ctdb-statistics</refentrytitle>
921 <manvolnum>7</manvolnum></citerefentry>.
924 <title>Example</title>
926 # ctdb dbstatistics locking.tdb
927 DB Statistics: locking.tdb
935 hop_count_buckets: 28087 2 1 0 0 0 0 0 0 0 0 0 0 0 0 0
936 lock_buckets: 0 14188 38 76 32 19 3 0 0 0 0 0 0 0 0 0
937 locks_latency MIN/AVG/MAX 0.001066/0.012686/4.202292 sec out of 14356
938 vacuum_latency MIN/AVG/MAX 0.000472/0.002207/15.243570 sec out of 224530
940 Count:8 Key:ff5bd7cb3ee3822edc1f0000000000000000000000000000
946 <title>getreclock</title>
948 Show details of the recovery lock, if any.
955 /clusterfs/.ctdb/recovery.lock
961 <title>getdebug</title>
963 Get the current debug level for the node. the debug level controls what information is written to the log file.
966 The debug levels are mapped to the corresponding syslog levels.
967 When a debug level is set, only those messages at that level and higher
968 levels will be printed.
971 The list of debug levels from highest to lowest are :
974 ERROR WARNING NOTICE INFO DEBUG
979 <title>setdebug <parameter>DEBUGLEVEL</parameter></title>
981 Set the debug level of a node. This controls what information will be logged.
984 The debuglevel is one of ERROR WARNING NOTICE INFO DEBUG
989 <title>getpid</title>
991 This command will return the process id of the ctdb daemon.
996 <title>disable</title>
998 This command is used to administratively disable a node in the cluster.
999 A disabled node will still participate in the cluster and host
1000 clustered TDB records but its public ip address has been taken over by
1001 a different node and it no longer hosts any services.
1006 <title>enable</title>
1008 Re-enable a node that has been administratively disabled.
1015 This command is used to administratively STOP a node in the cluster.
1016 A STOPPED node is connected to the cluster but will not host any
1017 public ip addresse, nor does it participate in the VNNMAP.
1018 The difference between a DISABLED node and a STOPPED node is that
1019 a STOPPED node does not host any parts of the database which means
1020 that a recovery is required to stop/continue nodes.
1025 <title>continue</title>
1027 Re-start a node that has been administratively stopped.
1032 <title>addip <parameter>IPADDR</parameter>/<parameter>mask</parameter> <parameter>IFACE</parameter></title>
1034 This command is used to add a new public ip to a node during runtime.
1035 This allows public addresses to be added to a cluster without having
1036 to restart the ctdb daemons.
1039 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.
1040 If you want this change to be permanent you must also update the public addresses file manually.
1045 <title>delip <parameter>IPADDR</parameter></title>
1047 This command flags IPADDR for deletion from a node at runtime.
1048 It should be followed by a <command>ctdb
1049 ipreallocate</command>. If IPADDR is currently hosted by the
1050 node it is being removed from, this ensures that the IP will
1051 first be failed over to another node, if possible, and that it
1052 is then actually removed.
1055 Note that this only updates the runtime instance of CTDB. Any
1056 changes will be lost next time CTDB is restarted and the
1057 public addresses file is re-read. If you want this change to
1058 be permanent you must also update the public addresses file
1064 <title>moveip <parameter>IPADDR</parameter> <parameter>PNN</parameter></title>
1066 This command can be used to manually fail a public ip address to a
1070 In order to manually override the "automatic" distribution of public
1071 ip addresses that ctdb normally provides, this command only works
1072 when you have changed the tunables for the daemon to:
1075 DeterministicIPs = 0
1083 <title>shutdown</title>
1085 This command will shutdown a specific CTDB daemon.
1090 <title>setlmasterrole on|off</title>
1092 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.
1096 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.
1099 Once this setting has been enabled/disabled, you need to perform a recovery for it to take effect.
1102 See also "ctdb getcapabilities"
1107 <title>setrecmasterrole on|off</title>
1109 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.
1113 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.
1116 See also "ctdb getcapabilities"
1121 <title>reloadnodes</title>
1123 This command is used when adding new nodes, or removing
1124 existing nodes from an existing cluster.
1127 Procedure to add nodes:
1132 To expand an existing cluster, first ensure with
1133 <command>ctdb status</command> that all nodes are up and
1134 running and that they are all healthy. Do not try to
1135 expand a cluster unless it is completely healthy!
1140 On all nodes, edit <filename>/usr/local/etc/ctdb/nodes</filename>
1141 and <emphasis>add the new nodes at the end of this
1147 Verify that all the nodes have identical
1148 <filename>/usr/local/etc/ctdb/nodes</filename> files after adding
1154 Run <command>ctdb reloadnodes</command> to force all nodes
1155 to reload the nodes file.
1160 Use <command>ctdb status</command> on all nodes and verify
1161 that they now show the additional nodes.
1166 Install and configure the new node and bring it online.
1171 Procedure to remove nodes:
1176 To remove nodes from an existing cluster, first ensure
1177 with <command>ctdb status</command> that all nodes, except
1178 the node to be deleted, are up and running and that they
1179 are all healthy. Do not try to remove nodes from a
1180 cluster unless the cluster is completely healthy!
1185 Shutdown and power off the node to be removed.
1190 On all other nodes, edit the
1191 <filename>/usr/local/etc/ctdb/nodes</filename> file and
1192 <emphasis>comment out</emphasis> the nodes to be removed.
1193 <emphasis>Do not delete the lines for the deleted
1194 nodes</emphasis>, just comment them out by adding a '#' at
1195 the beginning of the lines.
1200 Run <command>ctdb reloadnodes</command> to force all nodes
1201 to reload the nodes file.
1206 Use <command>ctdb status</command> on all nodes and verify
1207 that the deleted nodes are no longer listed.
1217 <optional><parameter>PNN-LIST</parameter></optional>
1220 This command reloads the public addresses configuration file
1221 on the specified nodes. When it completes addresses will be
1222 reconfigured and reassigned across the cluster as necessary.
1226 This command is currently unable to make changes to the
1227 netmask or interfaces associated with existing addresses.
1228 Such changes must be made in 2 steps by deleting addresses in
1229 question and re-adding then. Unfortunately this will disrupt
1230 connections to the changed addresses.
1235 <title>getdbmap</title>
1237 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.
1240 If a PERSISTENT database is not in a healthy state the database is
1241 flagged as UNHEALTHY. If there's at least one completely healthy node running in
1242 the cluster, it's possible that the content is restored by a recovery
1243 run automaticly. Otherwise an administrator needs to analyze the
1247 See also "ctdb getdbstatus", "ctdb backupdb", "ctdb restoredb",
1248 "ctdb dumpbackup", "ctdb wipedb", "ctdb setvar AllowUnhealthyDBRead 1"
1249 and (if samba or tdb-utils are installed) "tdbtool check".
1252 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.
1256 <title>Example</title>
1259 Number of databases:10
1260 dbid:0x435d3410 name:notify.tdb path:/usr/local/var/lib/ctdb/notify.tdb.0
1261 dbid:0x42fe72c5 name:locking.tdb path:/usr/local/var/lib/ctdb/locking.tdb.0
1262 dbid:0x1421fb78 name:brlock.tdb path:/usr/local/var/lib/ctdb/brlock.tdb.0
1263 dbid:0x17055d90 name:connections.tdb path:/usr/local/var/lib/ctdb/connections.tdb.0
1264 dbid:0xc0bdde6a name:sessionid.tdb path:/usr/local/var/lib/ctdb/sessionid.tdb.0
1265 dbid:0x122224da name:test.tdb path:/usr/local/var/lib/ctdb/test.tdb.0
1266 dbid:0x2672a57f name:idmap2.tdb path:/usr/local/var/lib/ctdb/persistent/idmap2.tdb.0 PERSISTENT
1267 dbid:0xb775fff6 name:secrets.tdb path:/usr/local/var/lib/ctdb/persistent/secrets.tdb.0 PERSISTENT
1268 dbid:0xe98e08b6 name:group_mapping.tdb path:/usr/local/var/lib/ctdb/persistent/group_mapping.tdb.0 PERSISTENT
1269 dbid:0x7bbbd26c name:passdb.tdb path:/usr/local/var/lib/ctdb/persistent/passdb.tdb.0 PERSISTENT
1271 # ctdb getdbmap # example for unhealthy database
1272 Number of databases:1
1273 dbid:0xb775fff6 name:secrets.tdb path:/usr/local/var/lib/ctdb/persistent/secrets.tdb.0 PERSISTENT UNHEALTHY
1276 |ID|Name|Path|Persistent|Unhealthy|
1277 |0x7bbbd26c|passdb.tdb|/usr/local/var/lib/ctdb/persistent/passdb.tdb.0|1|0|
1285 <parameter>DB</parameter>
1286 <parameter>FILE</parameter>
1289 Copy the contents of database DB to FILE. FILE can later be
1290 read back using <command>restoredb</command>. This is mainly
1291 useful for backing up persistent databases such as
1292 <filename>secrets.tdb</filename> and similar.
1299 <parameter>FILE</parameter>
1300 <optional><parameter>DB</parameter></optional>
1303 This command restores a persistent database that was
1304 previously backed up using backupdb. By default the data will
1305 be restored back into the same database as it was created
1306 from. By specifying dbname you can restore the data into a
1312 <title>setdbreadonly <parameter>DB</parameter></title>
1314 This command will enable the read-only record support for a
1315 database. This is an experimental feature to improve
1316 performance for contended records primarily in locking.tdb and
1317 brlock.tdb. When enabling this feature you must set it on all
1318 nodes in the cluster.
1323 <title>setdbsticky <parameter>DB</parameter></title>
1325 This command will enable the sticky record support for the
1326 specified database. This is an experimental feature to
1327 improve performance for contended records primarily in
1328 locking.tdb and brlock.tdb. When enabling this feature you
1329 must set it on all nodes in the cluster.
1336 <title>INTERNAL COMMANDS</title>
1339 Internal commands are used by CTDB's scripts and are not
1340 required for managing a CTDB cluster. Their parameters and
1341 behaviour are subject to change.
1345 <title>gettickles <parameter>IPADDR</parameter></title>
1347 Show TCP connections that are registered with CTDB to be
1348 "tickled" if there is a failover.
1353 <title>gratiousarp <parameter>IPADDR</parameter> <parameter>INTERFACE</parameter></title>
1355 Send out a gratious ARP for the specified interface through
1356 the specified interface. This command is mainly used by the
1363 pdelete <parameter>DB</parameter> <parameter>KEY</parameter>
1372 pfetch <parameter>DB</parameter> <parameter>KEY</parameter>
1375 Print the value associated with KEY in DB.
1382 <parameter>DB</parameter>
1383 <parameter>KEY</parameter>
1384 <parameter>FILE</parameter>
1387 Store KEY in DB with contents of FILE as the associated value.
1394 <parameter>DB</parameter>
1395 <optional><parameter>FILE</parameter></optional>
1398 Read a list of key-value pairs, one per line from FILE, and
1399 store them in DB using a single transaction. An empty value
1400 is equivalent to deleting the given key.
1403 The key and value should be separated by spaces or tabs. Each
1404 key/value should be a printable string enclosed in
1410 <title>runstate [setup|first_recovery|startup|running]</title>
1412 Print the runstate of the specified node. Runstates are used
1413 to serialise important state transitions in CTDB, particularly
1417 If one or more optional runstate arguments are specified then
1418 the node must be in one of these runstates for the command to
1422 <title>Example</title>
1431 <title>setifacelink <parameter>IFACE</parameter> up|down</title>
1433 Set the internal state of network interface IFACE. This is
1434 typically used in the <filename>10.interface</filename> script
1435 in the "monitor" event.
1438 Example: ctdb setifacelink eth0 up
1443 <title>tickle <parameter>SRC-IPADDR</parameter>:<parameter>SRC-PORT</parameter> <parameter>DST-IPADDR</parameter>:<parameter>DST-PORT</parameter></title>
1445 Send a TCP tickle to the source host for the specified TCP
1446 connection. A TCP tickle is a TCP ACK packet with an invalid
1447 sequence and acknowledge number and will when received by the
1448 source host result in it sending an immediate correct ACK back
1452 TCP tickles are useful to "tickle" clients after a IP failover has
1453 occured since this will make the client immediately recognize the
1454 TCP connection has been disrupted and that the client will need
1455 to reestablish. This greatly speeds up the time it takes for a client
1456 to detect and reestablish after an IP failover in the ctdb cluster.
1461 <title>version</title>
1463 Display the CTDB version.
1470 <title>DEBUGGING COMMANDS</title>
1472 These commands are primarily used for CTDB development and testing and
1473 should not be used for normal administration.
1478 <title>OPTIONS</title>
1481 <varlistentry><term>--print-emptyrecords</term>
1484 This enables printing of empty records when dumping databases
1485 with the catdb, cattbd and dumpdbbackup commands. Records with
1486 empty data segment are considered deleted by ctdb and cleaned
1487 by the vacuuming mechanism, so this switch can come in handy for
1488 debugging the vacuuming behaviour.
1493 <varlistentry><term>--print-datasize</term>
1496 This lets database dumps (catdb, cattdb, dumpdbbackup) print the
1497 size of the record data instead of dumping the data contents.
1502 <varlistentry><term>--print-lmaster</term>
1505 This lets catdb print the lmaster for each record.
1510 <varlistentry><term>--print-hash</term>
1513 This lets database dumps (catdb, cattdb, dumpdbbackup) print the
1514 hash for each record.
1519 <varlistentry><term>--print-recordflags</term>
1522 This lets catdb and dumpdbbackup print the
1523 record flags for each record. Note that cattdb always
1533 <title>process-exists <parameter>PID</parameter></title>
1535 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.
1540 <title>getdbstatus <parameter>DB</parameter></title>
1542 This command displays more details about a database.
1545 <title>Example</title>
1547 # ctdb getdbstatus test.tdb.0
1550 path: /usr/local/var/lib/ctdb/test.tdb.0
1554 # ctdb getdbstatus registry.tdb # with a corrupted TDB
1557 path: /usr/local/var/lib/ctdb/persistent/registry.tdb.0
1559 HEALTH: NO-HEALTHY-NODES - ERROR - Backup of corrupted TDB in '/usr/local/var/lib/ctdb/persistent/registry.tdb.0.corrupted.20091208091949.0Z'
1565 <title>catdb <parameter>DB</parameter></title>
1567 Print a dump of the clustered TDB database DB.
1572 <title>cattdb <parameter>DB</parameter></title>
1574 Print a dump of the contents of the local TDB database DB.
1579 <title>dumpdbbackup <parameter>FILE</parameter></title>
1581 Print a dump of the contents from database backup FILE,
1582 similar to <command>catdb</command>.
1587 <title>wipedb <parameter>DB</parameter></title>
1589 Remove all contents of database DB.
1594 <title>recover</title>
1596 This command will trigger the recovery daemon to do a cluster
1602 <title>ipreallocate, sync</title>
1604 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.
1609 <title>getmonmode</title>
1611 This command prints the monitoring mode of a node. This
1612 indicates when CTDB is monitoring services on the node. The
1613 monitoring mode is either ENABLED or DISABLED.
1618 <title>attach <parameter>DBNAME</parameter> [persistent]</title>
1620 Create a new CTDB database called DBNAME and attach to it on
1626 <title>detach <parameter>DB-LIST</parameter></title>
1628 Detach specified non-persistent database(s) from the cluster. This
1629 command will disconnect specified database(s) on all nodes in
1630 the cluster. This command should only be used when none of the
1631 specified database(s) are in use.
1634 All nodes should be active and tunable AllowClientDBAccess should
1635 be disabled on all nodes before detaching databases.
1640 <title>dumpmemory</title>
1642 This is a debugging command. This command will make the ctdb
1643 daemon to write a fill memory allocation map to standard output.
1648 <title>rddumpmemory</title>
1650 This is a debugging command. This command will dump the talloc memory
1651 allocation tree for the recovery daemon to standard output.
1656 <title>eventscript <parameter>ARGUMENTS</parameter></title>
1658 This is a debugging command. This command can be used to manually
1659 invoke and run the eventscritps with arbitrary arguments.
1664 <title>ban <parameter>BANTIME</parameter></title>
1666 Administratively ban a node for BANTIME seconds. The node
1667 will be unbanned after BANTIME seconds have elapsed.
1670 A banned node does not participate in the cluster. It does
1671 not host any records for the clustered TDB and does not host
1672 any public IP addresses.
1675 Nodes are automatically banned if they misbehave. For
1676 example, a node may be banned if it causes too many cluster
1680 To administratively exclude a node from a cluster use the
1681 <command>stop</command> command.
1686 <title>unban</title>
1688 This command is used to unban a node that has either been
1689 administratively banned using the ban command or has been
1690 automatically banned.
1695 <title>check_srvids <parameter>SRVID</parameter> ...</title>
1697 This command checks whether a set of srvid message ports are
1698 registered on the node or not. The command takes a list of
1702 <title>Example</title>
1704 # ctdb check_srvids 1 2 3 14765
1705 Server id 0:1 does not exist
1706 Server id 0:2 does not exist
1707 Server id 0:3 does not exist
1708 Server id 0:14765 exists
1715 <!-- UNDOCUMENTED: showban stats disablemonitor enablemonitor
1716 isnotrecmaster addtickle deltickle
1718 tfetch tstore readkey writekey
1719 checktcpport getdbseqnum ipiface
1723 <title>SEE ALSO</title>
1725 <citerefentry><refentrytitle>ctdbd</refentrytitle>
1726 <manvolnum>1</manvolnum></citerefentry>,
1728 <citerefentry><refentrytitle>onnode</refentrytitle>
1729 <manvolnum>1</manvolnum></citerefentry>,
1731 <citerefentry><refentrytitle>ctdb</refentrytitle>
1732 <manvolnum>7</manvolnum></citerefentry>,
1734 <citerefentry><refentrytitle>ctdb-statistics</refentrytitle>
1735 <manvolnum>7</manvolnum></citerefentry>,
1737 <citerefentry><refentrytitle>ctdb-tunables</refentrytitle>
1738 <manvolnum>7</manvolnum></citerefentry>,
1740 <ulink url="http://ctdb.samba.org/"/>