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>
12 <refname>ctdb</refname>
13 <refpurpose>clustered tdb database management utility</refpurpose>
18 <command>ctdb [ OPTIONS ] COMMAND ...</command>
22 <command>ctdb</command>
23 <arg choice="opt">-n <node></arg>
24 <arg choice="opt">-Y</arg>
25 <arg choice="opt">-t <timeout></arg>
26 <arg choice="opt">-T <timelimit></arg>
27 <arg choice="opt">-? --help</arg>
28 <arg choice="opt">--usage</arg>
29 <arg choice="opt">-d --debug=<INTEGER></arg>
30 <arg choice="opt">--socket=<filename></arg>
35 <refsect1><title>DESCRIPTION</title>
37 ctdb is a utility to view and manage a ctdb cluster.
43 <title>OPTIONS</title>
46 <varlistentry><term>-n <pnn></term>
49 This specifies the physical node number on which to execute the
50 command. Default is to run the command on the deamon running on
54 The physical node number is an integer that describes the node in the
55 cluster. The first node has physical node number 0.
60 <varlistentry><term>-Y</term>
63 Produce output in machine readable form for easier parsing by scripts. Not all commands support this option.
68 <varlistentry><term>-t <timeout></term>
71 How long should ctdb wait for the local ctdb daemon to respond to a command before timing out. Default is 3 seconds.
76 <varlistentry><term>-T <timelimit></term>
79 A limit on how long the ctdb command will run for before it will
80 be aborted. When this timelimit has been exceeded the ctdb command will
86 <varlistentry><term>-? --help</term>
89 Print some help text to the screen.
94 <varlistentry><term>--usage</term>
97 Print useage information to the screen.
102 <varlistentry><term>-d --debug=<debuglevel></term>
105 Change the debug level for the command. Default is 0.
110 <varlistentry><term>--socket=<filename></term>
113 Specify the socketname to use when connecting to the local ctdb
114 daemon. The default is /tmp/ctdb.socket .
117 You only need to specify this parameter if you run multiple ctdb
118 daemons on the same physical host and thus can not use the default
119 name for the domain socket.
128 <refsect1><title>Administrative Commands</title>
130 These are commands used to monitor and administrate a CTDB cluster.
133 <refsect2><title>pnn</title>
135 This command displays the pnn of the current node.
139 <refsect2><title>status</title>
141 This command shows the current status of the ctdb node.
144 <refsect3><title>node status</title>
146 Node status reflects the current status of the node. There are five possible states:
149 OK - This node is fully functional.
152 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.
155 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.
158 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.
161 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.
164 STOPPED - A node that is stopped does not host any public ip addresses,
165 nor is it part of the VNNMAP. A stopped node can not become LVSMASTER,
167 This node does not perticipate in the CTDB cluster but can still be
168 communicated with. I.e. ctdb commands can be sent to it.
172 <refsect3><title>generation</title>
174 The generation id is a number that indicates the current generation
175 of a cluster instance. Each time a cluster goes through a
176 reconfiguration or a recovery its generation id will be changed.
179 This number does not have any particular meaning other than to keep
180 track of when a cluster has gone through a recovery. It is a random
181 number that represents the current instance of a ctdb cluster
183 CTDBD uses this number internally to be able to tell when commands
184 to operate on the cluster and the databases was issued in a different
185 generation of the cluster, to ensure that commands that operate
186 on the databases will not survive across a cluster database recovery.
187 After a recovery, all old outstanding commands will automatically
191 Sometimes this number will be shown as "INVALID". This only means that
192 the ctdbd daemon has started but it has not yet merged with the cluster through a recovery.
193 All nodes start with generation "INVALID" and are not assigned a real
194 generation id until they have successfully been merged with a cluster
199 <refsect3><title>VNNMAP</title>
201 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.
202 Only nodes that are participating in the vnnmap can become lmaster or dmaster for a database record.
206 <refsect3><title>Recovery mode</title>
208 This is the current recovery mode of the cluster. There are two possible modes:
211 NORMAL - The cluster is fully operational.
214 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.
217 Once the recovery master detects an inconsistency, for example a node
218 becomes disconnected/connected, the recovery daemon will trigger a
219 cluster recovery process, where all databases are remerged across the
220 cluster. When this process starts, the recovery master will first
221 "freeze" all databases to prevent applications such as samba from
222 accessing the databases and it will also mark the recovery mode as
226 When CTDBD starts up, it will start in RECOVERY mode.
227 Once the node has been merged into a cluster and all databases
228 have been recovered, the node mode will change into NORMAL mode
229 and the databases will be "thawed", allowing samba to access the
234 <refsect3><title>Recovery master</title>
236 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.
239 Only one node at a time can be the designated recovery master. Which
240 node is designated the recovery master is decided by an election
241 process in the recovery daemons running on each node.
248 <para>Example output:</para>
249 <screen format="linespecific">
251 pnn:0 11.1.2.200 OK (THIS NODE)
255 Generation:1362079228
261 Recovery mode:NORMAL (0)
266 <refsect2><title>recmaster</title>
268 This command shows the pnn of the node which is currently the recmaster.
272 <refsect2><title>uptime</title>
274 This command shows the uptime for the ctdb daemon. When the last recovery completed and how long the last recovery took. If the "duration" is shown as a negative number, this indicates that there is a recovery in progress and it started that many seconds ago.
280 <para>Example output:</para>
281 <screen format="linespecific">
282 Current time of node : Tue Mar 24 18:27:54 2009
283 Ctdbd start time : (000 00:00:05) Tue Mar 24 18:27:49 2009
284 Time of last recovery : (000 00:00:05) Tue Mar 24 18:27:49 2009
285 Duration of last recovery : 0.000000 seconds
289 <refsect2><title>listnodes</title>
291 This command shows lists the ip addresses of all the nodes in the cluster.
295 Example: ctdb listnodes
297 <para>Example output:</para>
298 <screen format="linespecific">
306 <refsect2><title>ping</title>
308 This command will "ping" all CTDB daemons in the cluster to verify that they are processing commands correctly.
316 <screen format="linespecific">
317 response from 0 time=0.000054 sec (3 clients)
318 response from 1 time=0.000144 sec (2 clients)
319 response from 2 time=0.000105 sec (2 clients)
320 response from 3 time=0.000114 sec (2 clients)
324 <refsect2><title>ip</title>
326 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".
334 <screen format="linespecific">
335 Number of addresses:4
343 <refsect2><title>scriptstatus</title>
345 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.
348 Example: ctdb scriptstatus
353 <screen format="linespecific">
354 7 scripts were executed last monitoring cycle
355 00.ctdb Status:OK Duration:0.056 Tue Mar 24 18:56:57 2009
356 10.interface Status:OK Duration:0.077 Tue Mar 24 18:56:57 2009
357 11.natgw Status:OK Duration:0.039 Tue Mar 24 18:56:57 2009
358 20.multipathd Status:OK Duration:0.038 Tue Mar 24 18:56:57 2009
359 40.vsftpd Status:OK Duration:0.045 Tue Mar 24 18:56:57 2009
360 41.httpd Status:OK Duration:0.039 Tue Mar 24 18:56:57 2009
361 50.samba Status:ERROR Duration:0.082 Tue Mar 24 18:56:57 2009
362 OUTPUT:ERROR: Samba tcp port 445 is not responding
366 <refsect2><title>getvar <name></title>
368 Get the runtime value of a tuneable variable.
371 Example: ctdb getvar MaxRedirectCount
376 <screen format="linespecific">
381 <refsect2><title>setvar <name> <value></title>
383 Set the runtime value of a tuneable variable.
386 Example: ctdb setvar MaxRedirectCount 5
390 <refsect2><title>listvars</title>
392 List all tuneable variables.
395 Example: ctdb listvars
400 <screen format="linespecific">
405 KeepaliveInterval = 2
413 EventScriptTimeout = 20
414 RecoveryGracePeriod = 60
415 RecoveryBanPeriod = 300
419 <refsect2><title>lvsmaster</title>
421 This command shows which node is currently the LVSMASTER. The
422 LVSMASTER is the node in the cluster which drives the LVS system and
423 which receives all incoming traffic from clients.
426 LVS is the mode where the entire CTDB/Samba cluster uses a single
427 ip address for the entire cluster. In this mode all clients connect to
428 one specific node which will then multiplex/loadbalance the clients
429 evenly onto the other nodes in the cluster. This is an alternative to using
430 public ip addresses. See the manpage for ctdbd for more information
435 <refsect2><title>lvs</title>
437 This command shows which nodes in the cluster are currently active in the
438 LVS configuration. I.e. which nodes we are currently loadbalancing
439 the single ip address across.
443 LVS will by default only loadbalance across those nodes that are both
444 LVS capable and also HEALTHY. Except if all nodes are UNHEALTHY in which
445 case LVS will loadbalance across all UNHEALTHY nodes as well.
446 LVS will never use nodes that are DISCONNECTED, STOPPED, BANNED or
453 <screen format="linespecific">
461 <refsect2><title>getcapabilities</title>
463 This command shows the capabilities of the current node.
464 Please see manpage for ctdbd for a full list of all capabilities and
465 more detailed description.
469 RECMASTER and LMASTER capabilities are primarily used when CTDBD
470 is used to create a cluster spanning across WAN links. In which case
471 ctdbd acts as a WAN accelerator.
475 LVS capability means that the node is participating in LVS, a mode
476 where the entire CTDB cluster uses one single ip address for the
477 entire cluster instead of using public ip address failover.
478 This is an alternative to using a loadbalancing layer-4 switch.
482 NATGW capability means that the node participates in a NATGW group.
483 This flag can be modified using "ctdb setnatgwstate {on|off}"
489 <screen format="linespecific">
498 <refsect2><title>statistics</title>
500 Collect statistics from the CTDB daemon about how many calls it has served.
503 Example: ctdb statistics
508 <screen format="linespecific">
513 client_packets_sent 360489
514 client_packets_recv 360466
515 node_packets_sent 480931
516 node_packets_recv 240120
517 keepalive_packets_sent 4
518 keepalive_packets_recv 3
539 pending_lockwait_calls 0
542 max_call_latency 4.948321 sec
543 max_lockwait_latency 0.000000 sec
547 <refsect2><title>statisticsreset</title>
549 This command is used to clear all statistics counters in a node.
552 Example: ctdb statisticsreset
556 <refsect2><title>getreclock</title>
558 This command is used to show the filename of the reclock file that is used.
564 <screen format="linespecific">
565 Reclock file:/gpfs/.ctdb/shared
570 <refsect2><title>setreclock [filename]</title>
572 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".
576 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.
580 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.
586 <refsect2><title>getdebug</title>
588 Get the current debug level for the node. the debug level controls what information is written to the log file.
591 The debug levels are mapped to the corresponding syslog levels.
592 When a debug level is set, only those messages at that level and higher
593 levels will be printed.
596 The list of debug levels from highest to lowest are :
599 EMERG ALERT CRIT ERR WARNING NOTICE INFO DEBUG
603 <refsect2><title>setdebug <debuglevel></title>
605 Set the debug level of a node. This controls what information will be logged.
608 The debuglevel is one of EMERG ALERT CRIT ERR WARNING NOTICE INFO DEBUG
612 <refsect2><title>getpid</title>
614 This command will return the process id of the ctdb daemon.
618 <refsect2><title>disable</title>
620 This command is used to administratively disable a node in the cluster.
621 A disabled node will still participate in the cluster and host
622 clustered TDB records but its public ip address has been taken over by
623 a different node and it no longer hosts any services.
627 <refsect2><title>enable</title>
629 Re-enable a node that has been administratively disabled.
633 <refsect2><title>stop</title>
635 This command is used to administratively STOP a node in the cluster.
636 A STOPPED node is connected to the cluster but will not host any
637 public ip addresse, nor does it participate in the VNNMAP.
638 The difference between a DISABLED node and a STOPPED node is that
639 a STOPPED node does not host any parts of the database which means
640 that a recovery is required to stop/continue nodes.
644 <refsect2><title>continue</title>
646 Re-start a node that has been administratively stopped.
650 <refsect2><title>addip <public_ip/mask> <iface></title>
652 This command is used to add a new public ip to a node during runtime.
653 This allows public addresses to be added to a cluster without having
654 to restart the ctdb daemons.
657 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.
658 If you want this change to be permanent you must also update the public addresses file manually.
662 <refsect2><title>delip <public_ip></title>
664 This command is used to remove a public ip from a node during runtime.
665 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.
668 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.
669 If you want this change to be permanent you must also update the public addresses file manually.
673 <refsect2><title>moveip <public_ip> <node></title>
675 This command can be used to manually fail a public ip address to a
679 In order to manually override the "automatic" distribution of public
680 ip addresses that ctdb normally provides, this command only works
681 when you have changed the tunables for the daemon to:
691 <refsect2><title>shutdown</title>
693 This command will shutdown a specific CTDB daemon.
697 <refsect2><title>recover</title>
699 This command will trigger the recovery daemon to do a cluster
704 <refsect2><title>ipreallocate</title>
706 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.
710 <refsect2><title>killtcp <srcip:port> <dstip:port></title>
712 This command will kill the specified TCP connection by issuing a
713 TCP RST to the srcip:port endpoint. This is a command used by the
718 <refsect2><title>gratiousarp <ip> <interface></title>
720 This command will send out a gratious arp for the specified interface
721 through the specified interface. This command is mainly used by the
726 <refsect2><title>reloadnodes</title>
728 This command is used when adding new nodes, or removing existing nodes from an existing cluster.
731 Procedure to add a node:
734 1, To expand an existing cluster, first ensure with 'ctdb status' that
735 all nodes are up and running and that they are all healthy.
736 Do not try to expand a cluster unless it is completely healthy!
739 2, On all nodes, edit /etc/ctdb/nodes and add the new node as the last
740 entry to the file. The new node MUST be added to the end of this file!
743 3, Verify that all the nodes have identical /etc/ctdb/nodes files after you edited them and added the new node!
746 4, Run 'ctdb reloadnodes' to force all nodes to reload the nodesfile.
749 5, Use 'ctdb status' on all nodes and verify that they now show the additional node.
752 6, Install and configure the new node and bring it online.
755 Procedure to remove a node:
758 1, To remove a node from an existing cluster, first ensure with 'ctdb status' that
759 all nodes, except the node to be deleted, are up and running and that they are all healthy.
760 Do not try to remove a node from a cluster unless the cluster is completely healthy!
763 2, Shutdown and poerwoff the node to be removed.
766 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.
769 4, Run 'ctdb reloadnodes' to force all nodes to reload the nodesfile.
772 5, Use 'ctdb status' on all nodes and verify that the deleted node no longer shows up in the list..
779 <refsect2><title>tickle <srcip:port> <dstip:port></title>
781 This command will will send a TCP tickle to the source host for the
782 specified TCP connection.
783 A TCP tickle is a TCP ACK packet with an invalid sequence and
784 acknowledge number and will when received by the source host result
785 in it sending an immediate correct ACK back to the other end.
788 TCP tickles are useful to "tickle" clients after a IP failover has
789 occured since this will make the client immediately recognize the
790 TCP connection has been disrupted and that the client will need
791 to reestablish. This greatly speeds up the time it takes for a client
792 to detect and reestablish after an IP failover in the ctdb cluster.
796 <refsect2><title>gettickles <ip></title>
798 This command is used to show which TCP connections are registered with
799 CTDB to be "tickled" if there is a failover.
802 <refsect2><title>repack [max_freelist]</title>
804 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.
805 This command is used to defragment a TDB database and pruning the freelist.
809 If [max_freelist] is specified, then a database will only be repacked if it has more than this number of entries in the freelist.
812 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.
816 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.
820 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.
824 Example: ctdb repack 1000
828 By default, this operation is issued from the 00.ctdb event script every 5 minutes.
833 <refsect2><title>vacuum [max_records]</title>
835 Over time CTDB databases will fill up with empty deleted records which will lead to a progressive slow down of CTDB database access.
836 This command is used to prune all databases and delete all empty records from the cluster.
840 By default, vacuum will delete all empty records from all databases.
841 If [max_records] is specified, the command will only delete the first
842 [max_records] empty records for each database.
846 Vacuum only deletes records where the local node is the lmaster.
847 To delete all records from the entire cluster you need to run a vacuum from each node.
849 This command is not disruptive. Samba is unaffected and will still be able to read/write records normally while the database is being vacuumed.
857 By default, this operation is issued from the 00.ctdb event script every 5 minutes.
861 <refsect2><title>backupdb <database> <file></title>
863 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.
864 This is mainly useful for backing up persistent databases such as secrets.tdb and similar.
868 <refsect2><title>restoredb <file></title>
870 This command restores a persistent database that was previously backed up using backupdb.
877 <refsect1><title>Debugging Commands</title>
879 These commands are primarily used for CTDB development and testing and
880 should not be used for normal administration.
882 <refsect2><title>process-exists <pid></title>
884 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.
888 <refsect2><title>getdbmap</title>
890 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.
893 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.
896 Example: ctdb getdbmap
901 <screen format="linespecific">
902 Number of databases:10
903 dbid:0x435d3410 name:notify.tdb path:/var/ctdb/notify.tdb.0
904 dbid:0x42fe72c5 name:locking.tdb path:/var/ctdb/locking.tdb.0 dbid:0x1421fb78 name:brlock.tdb path:/var/ctdb/brlock.tdb.0
905 dbid:0x17055d90 name:connections.tdb path:/var/ctdb/connections.tdb.0
906 dbid:0xc0bdde6a name:sessionid.tdb path:/var/ctdb/sessionid.tdb.0
907 dbid:0x122224da name:test.tdb path:/var/ctdb/test.tdb.0
908 dbid:0x2672a57f name:idmap2.tdb path:/var/ctdb/persistent/idmap2.tdb.0 PERSISTENT
909 dbid:0xb775fff6 name:secrets.tdb path:/var/ctdb/persistent/secrets.tdb.0 PERSISTENT
910 dbid:0xe98e08b6 name:group_mapping.tdb path:/var/ctdb/persistent/group_mapping.tdb.0 PERSISTENT
911 dbid:0x7bbbd26c name:passdb.tdb path:/var/ctdb/persistent/passdb.tdb.0 PERSISTENT
915 <refsect2><title>catdb <dbname></title>
917 This command will dump a clustered TDB database to the screen. This is a debugging command.
921 <refsect2><title>getmonmode</title>
923 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.
926 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.
929 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.
934 <refsect2><title>setmonmode <0|1></title>
936 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.
940 <refsect2><title>attach <dbname></title>
942 This is a debugging command. This command will make the CTDB daemon create a new CTDB database and attach to it.
946 <refsect2><title>dumpmemory</title>
948 This is a debugging command. This command will make the ctdb
949 daemon to write a fill memory allocation map to standard output.
953 <refsect2><title>rddumpmemory</title>
955 This is a debugging command. This command will dump the talloc memory
956 allocation tree for the recovery daemon to standard output.
960 <refsect2><title>freeze</title>
962 This command will lock all the local TDB databases causing clients
963 that are accessing these TDBs such as samba3 to block until the
964 databases are thawed.
967 This is primarily used by the recovery daemon to stop all samba
968 daemons from accessing any databases while the database is recovered
973 <refsect2><title>thaw</title>
975 Thaw a previously frozen node.
980 <refsect2><title>eventscript <arguments></title>
982 This is a debugging command. This command can be used to manually
983 invoke and run the eventscritps with arbitrary arguments.
987 <refsect2><title>ban <bantime|0></title>
989 Administratively ban a node for bantime seconds. A bantime of 0 means that the node should be permanently banned.
992 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.
995 Nodes are automatically banned if they are the cause of too many
1000 <refsect2><title>unban</title>
1002 This command is used to unban a node that has either been
1003 administratively banned using the ban command or has been automatically
1004 banned by the recovery daemon.
1011 <refsect1><title>SEE ALSO</title>
1014 <ulink url="http://ctdb.samba.org/"/>
1017 <refsect1><title>COPYRIGHT/LICENSE</title>
1019 Copyright (C) Andrew Tridgell 2007
1020 Copyright (C) Ronnie sahlberg 2007
1022 This program is free software; you can redistribute it and/or modify
1023 it under the terms of the GNU General Public License as published by
1024 the Free Software Foundation; either version 3 of the License, or (at
1025 your option) any later version.
1027 This program is distributed in the hope that it will be useful, but
1028 WITHOUT ANY WARRANTY; without even the implied warranty of
1029 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
1030 General Public License for more details.
1032 You should have received a copy of the GNU General Public License
1033 along with this program; if not, see http://www.gnu.org/licenses/.