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. -
+
+ STOPPED - A node that is stopped does not host any public ip addresses, + nor is it part of the VNNMAP. A stopped node can not become LVSMASTER, + RECMASTER or NATGW. + This node does not perticipate in the CTDB cluster but can still be + communicated with. I.e. ctdb commands can be sent to it. +
The generation id is a number that indicates the current generation of a cluster instance. Each time a cluster goes through a reconfiguration or a recovery its generation id will be changed. @@ -67,10 +73,10 @@ All nodes start with generation "INVALID" and are not assigned a real generation id until they have successfully been merged with a cluster through a recovery. -
The list of Virtual Node Numbers. This is a list of all nodes that actively participates in the cluster and that share the workload of hosting the Clustered TDB database records. Only nodes that are participating in the vnnmap can become lmaster or dmaster for a database record. -
This is the current recovery mode of the cluster. There are two possible modes:
NORMAL - The cluster is fully operational. @@ -90,7 +96,7 @@ have been recovered, the node mode will change into NORMAL mode and the databases will be "thawed", allowing samba to access the databases again. -
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.
Only one node at a time can be the designated recovery master. Which @@ -112,9 +118,9 @@ hash:2 lmaster:2 hash:3 lmaster:3 Recovery mode:NORMAL (0) Recovery master:0 -
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.
Example: ctdb uptime @@ -123,7 +129,7 @@ Current time of node : Tue Mar 24 18:27:54 2009 Ctdbd start time : (000 00:00:05) Tue Mar 24 18:27:49 2009 Time of last recovery : (000 00:00:05) Tue Mar 24 18:27:49 2009 Duration of last recovery : 0.000000 seconds -
This command shows lists the ip addresses of all the nodes in the cluster.
Example: ctdb listnodes @@ -132,7 +138,7 @@ Duration of last recovery : 0.000000 seconds 10.0.0.72 10.0.0.73 10.0.0.74 -
This command will "ping" all CTDB daemons in the cluster to verify that they are processing commands correctly.
Example: ctdb ping @@ -143,7 +149,7 @@ response from 0 time=0.000054 sec (3 clients) response from 1 time=0.000144 sec (2 clients) response from 2 time=0.000105 sec (2 clients) response from 3 time=0.000114 sec (2 clients) -
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".
Example: ctdb ip @@ -155,7 +161,7 @@ Number of addresses:4 12.1.1.2 1 12.1.1.3 2 12.1.1.4 3 -
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.
Example: ctdb scriptstatus @@ -171,7 +177,7 @@ Number of addresses:4 41.httpd Status:OK Duration:0.039 Tue Mar 24 18:56:57 2009 50.samba Status:ERROR Duration:0.082 Tue Mar 24 18:56:57 2009 OUTPUT:ERROR: Samba tcp port 445 is not responding -
Get the runtime value of a tuneable variable.
Example: ctdb getvar MaxRedirectCount @@ -179,11 +185,11 @@ Number of addresses:4 Example output:
MaxRedirectCount = 3 -
Set the runtime value of a tuneable variable.
Example: ctdb setvar MaxRedirectCount 5 -
List all tuneable variables.
Example: ctdb listvars @@ -205,7 +211,7 @@ MonitorInterval = 15 EventScriptTimeout = 20 RecoveryGracePeriod = 60 RecoveryBanPeriod = 300 -
This command shows which node is currently the LVSMASTER. The LVSMASTER is the node in the cluster which drives the LVS system and which receives all incoming traffic from clients. @@ -216,7 +222,7 @@ RecoveryBanPeriod = 300 evenly onto the other nodes in the cluster. This is an alternative to using public ip addresses. See the manpage for ctdbd for more information about LVS. -
This command shows which nodes in the cluster are currently active in the LVS configuration. I.e. which nodes we are currently loadbalancing the single ip address across. @@ -224,13 +230,14 @@ RecoveryBanPeriod = 300 LVS will by default only loadbalance across those nodes that are both LVS capable and also HEALTHY. Except if all nodes are UNHEALTHY in which case LVS will loadbalance across all UNHEALTHY nodes as well. - LVS will never use nodes that are DISCONNECTED, BANNED or DISABLED. + LVS will never use nodes that are DISCONNECTED, STOPPED, BANNED or + DISABLED.
Example output:
2:10.0.0.13 3:10.0.0.14 -
This command shows the capabilities of the current node. Please see manpage for ctdbd for a full list of all capabilities and more detailed description. @@ -249,7 +256,7 @@ RecoveryBanPeriod = 300 RECMASTER: YES LMASTER: YES LVS: NO -
Collect statistics from the CTDB daemon about how many calls it has served.
Example: ctdb statistics @@ -291,23 +298,23 @@ CTDB version 1 max_hop_count 0 max_call_latency 4.948321 sec max_lockwait_latency 0.000000 sec -
This command is used to clear all statistics counters in a node.
Example: ctdb statisticsreset -
This command is used to show the filename of the reclock file that is used.
Example output:
Reclock file:/gpfs/.ctdb/shared -
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".
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.
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. -
Get the current debug level for the node. the debug level controls what information is written to the log file.
The debug levels are mapped to the corresponding syslog levels. @@ -317,40 +324,42 @@ Reclock file:/gpfs/.ctdb/shared The list of debug levels from highest to lowest are :
EMERG ALERT CRIT ERR WARNING NOTICE INFO DEBUG -
Set the debug level of a node. This controls what information will be logged.
The debuglevel is one of EMERG ALERT CRIT ERR WARNING NOTICE INFO DEBUG -
This command is used to administratively disable a node in the cluster. A disabled node will still participate in the cluster and host clustered TDB records but its public ip address has been taken over by a different node and it no longer hosts any services. -
- Administratively ban a node for bantime seconds. A bantime of 0 means that the node should be permanently banned. -
- 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. -
- Nodes are automatically banned if they are the cause of too many - cluster recoveries. -
+ This command is used to administratively STOP a node in the cluster. + A STOPPED node is connected to the cluster but will not host any + public ip addresse, nor does it participate in the VNNMAP. + The difference between a DISABLED node and a STOPPED node is that + a STOPPED node does not host any parts of the database which means + that a recovery is required to stop/continue nodes. +
This command is used to add a new public ip to a node during runtime. This allows public addresses to be added to a cluster without having to restart the ctdb daemons.
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. If you want this change to be permanent you must also update the public addresses file manually. -
This command is used to remove a public ip from a node during runtime. 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.
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. If you want this change to be permanent you must also update the public addresses file manually. -
This command can be used to manually fail a public ip address to a specific node.
@@ -361,26 +370,22 @@ Reclock file:/gpfs/.ctdb/shared DeterministicIPs = 0
NoIPFailback = 1 -
- This command is used to unban a node that has either been - administratively banned using the ban command or has been automatically - banned by the recovery daemon. -
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. -
This command will kill the specified TCP connection by issuing a TCP RST to the srcip:port endpoint. This is a command used by the ctdb eventscripts. -
This command will send out a gratious arp for the specified interface through the specified interface. This command is mainly used by the ctdb eventscripts. -
This command is used when adding new nodes, or removing existing nodes from an existing cluster.
Procedure to add a node: @@ -414,7 +419,7 @@ Reclock file:/gpfs/.ctdb/shared
5, Use 'ctdb status' on all nodes and verify that the deleted node no longer shows up in the list..
-
This command will will send a TCP tickle to the source host for the specified TCP connection. A TCP tickle is a TCP ACK packet with an invalid sequence and @@ -426,7 +431,7 @@ Reclock file:/gpfs/.ctdb/shared TCP connection has been disrupted and that the client will need to reestablish. This greatly speeds up the time it takes for a client to detect and reestablish after an IP failover in the ctdb cluster. -
This command is used to show which TCP connections are registered with CTDB to be "tickled" if there is a failover.
@@ -460,12 +465,17 @@ Reclock file:/gpfs/.ctdb/shared Example: ctdb vacuum
By default, this operation is issued from the 00.ctdb event script every 5 minutes. -
+ 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. +This is mainly useful for backing up persistent databases such as secrets.tdb and similar. +
+ This command restores a persistent database that was previously backed up using backupdb. +
These commands are primarily used for CTDB development and testing and should not be used for normal administration. -
+
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. -
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.
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. @@ -484,25 +494,25 @@ dbid:0x2672a57f name:idmap2.tdb path:/var/ctdb/persistent/idmap2.tdb.0 PERSISTEN dbid:0xb775fff6 name:secrets.tdb path:/var/ctdb/persistent/secrets.tdb.0 PERSISTENT dbid:0xe98e08b6 name:group_mapping.tdb path:/var/ctdb/persistent/group_mapping.tdb.0 PERSISTENT dbid:0x7bbbd26c name:passdb.tdb path:/var/ctdb/persistent/passdb.tdb.0 PERSISTENT -
This command will dump a clustered TDB database to the screen. This is a debugging command. -
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.
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.
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. -
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. -
This is a debugging command. This command will make the CTDB daemon create a new CTDB database and attach to it. -
This is a debugging command. This command will make the ctdb daemon to write a fill memory allocation map to standard output. -
This is a debugging command. This command will dump the talloc memory allocation tree for the recovery daemon to standard output. -
This command will lock all the local TDB databases causing clients that are accessing these TDBs such as samba3 to block until the databases are thawed. @@ -510,20 +520,26 @@ dbid:0x7bbbd26c name:passdb.tdb path:/var/ctdb/persistent/passdb.tdb.0 PERSISTEN This is primarily used by the recovery daemon to stop all samba daemons from accessing any databases while the database is recovered and rebuilt. -
This is a debugging command. This command can be used to manually invoke and run the eventscritps with arbitrary arguments. -
+ Administratively ban a node for bantime seconds. A bantime of 0 means that the node should be permanently banned. +
+ 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. +
+ Nodes are automatically banned if they are the cause of too many + cluster recoveries. +
+
ctdbd — The CTDB cluster daemon
+ ctdbd — The CTDB cluster daemon
ctdbd is the main ctdb daemon.
ctdbd provides a clustered version of the TDB database with automatic rebuild/recovery of the databases upon nodefailures.
@@ -8,7 +8,7 @@
ctdbd provides monitoring of all nodes in the cluster and automatically reconfigures the cluster and recovers upon node failures.
ctdbd is the main component in clustered Samba that provides a high-availability load-sharing CIFS server cluster.
-
+
Print some help text to the screen.
This option sets the debuglevel on the ctdbd daemon which controls what will be written to the logfile. The default is 0 which will only log important events and errors. A larger number will provide additional logging.
@@ -107,6 +107,15 @@
A node that is DISABLED will not host any services and will not be
reachable/used by any clients.
+
+ This makes the ctdb daemon to be STOPPED when it starts up.
+
+ A node that is STOPPED does not host any public addresses. It is not part of the VNNMAP so it does act as an LMASTER. It also has all databases locked in recovery mode until restarted.
+
+ To restart and activate a STOPPED node, the command "ctdb continue" is used.
+
+ A node that is STOPPED will not host any services and will not be
+ reachable/used by any clients.
Send all log messages to syslog instead of to the ctdb logfile.
@@ -120,10 +129,10 @@
implemented in the future.
Print useage information to the screen.
-
When used for ip takeover in a HA environment, each node in a ctdb
cluster has multiple ip addresses assigned to it. One private and one or more public.
-
+
This is the physical ip address of the node which is configured in
linux and attached to a physical interface. This address uniquely
identifies a physical node in the cluster and is the ip addresses
@@ -153,7 +162,7 @@
10.1.1.2
10.1.1.3
10.1.1.4
-
A public address on the other hand is not attached to an interface.
This address is managed by ctdbd itself and is attached/detached to
a physical node at runtime.
@@ -214,7 +223,7 @@
unavailable. 10.1.1.1 can not be failed over to node 2 or node 3 since
these nodes do not have this ip address listed in their public
addresses file.
-
The current status of each node in the cluster can be viewed by the
'ctdb status' command.
@@ -245,50 +254,56 @@
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.
-
+
+ STOPPED - A node that is stopped does not host any public ip addresses,
+ nor is it part of the VNNMAP. A stopped node can not become LVSMASTER,
+ RECMASTER or NATGW.
+ This node does not perticipate in the CTDB cluster but can still be
+ communicated with. I.e. ctdb commands can be sent to it.
+
These are the public tuneables that can be used to control how ctdb behaves.
- Default: 1
+ Default: 5
After how many keepalive intervals without any traffic should a node
wait until marking the peer as DISCONNECTED.
- Default: 15
How often should ctdb run the event scripts to check for a nodes health.
- Default: 20
How often will ctdb record and store the "tickle" information used to
kickstart stalled tcp connections after a recovery.
- Default: 20
How long should ctdb let an event script run before aborting it and
marking the node unhealthy.
- Default: 300
If a node becomes banned causing repetitive recovery failures. The node will
eventually become banned from the cluster.
This controls how long the culprit node will be banned from the cluster
before it is allowed to try to join the cluster again.
Dont set to small. A node gets banned for a reason and it is usually due
to real problems with the node.
- Default: 100000
Size of the hash chains for the local store of the tdbs that ctdb manages.
- Default: 10
Once a recovery has completed, no additional recoveries are permitted until this timeout has expired.
- Default: 1
When set to 0, this disables BANNING completely in the cluster and thus nodes can not get banned, even it they break. Dont set to 0.
- Default: 1
When enabled, this tunable makes ctdb try to keep public IP addresses locked to specific nodes as far as possible. This makes it easier for debugging since you can know that as long as all nodes are healthy public IP X will always be hosted by node Y.
The cost of using deterministic IP address assignment is that it disables part of the logic where ctdb tries to reduce the number of public IP assignment changes in the cluster. This tunable may increase the number of IP failover/failbacks that are performed on the cluster by a small margin.
- Default: 0
When set, As soon as a node becomes unhealthy, that node will also automatically become permanently DISABLED. Once a node is DISABLED, the only way to make it participate in the cluster again and host services is by manually enabling the node again using 'ctdb enable'.
This disables parts of the resilience and robustness of the cluster and should ONLY be used when the system administrator is actively monitoring the cluster, so that nodes can be enabled again.
- Default: 0
When set to 1, ctdb will not perform failback of IP addresses when a node becomes healthy. Ctdb WILL perform failover of public IP addresses when a node becomes UNHEALTHY, but when the node becomes HEALTHY again, ctdb will not fail the addresses back.
Use with caution! Normally when a node becomes available to the cluster
ctdb will try to reassign public IP addresses onto the new node as a way to distribute the workload evenly across the clusternode. Ctdb tries to make sure that all running nodes have approximately the same number of public addresses it hosts.
When you enable this tunable, CTDB will no longer attempt to rebalance the cluster by failing IP addresses back to the new nodes. An unbalanced cluster will therefore remain unbalanced until there is manual intervention from the administrator. When this parameter is set, you can manually fail public IP addresses over to the new node(s) using the 'ctdb moveip' command.
-
LVS is a mode where CTDB presents one single IP address for the entire
cluster. This is an alternative to using public IP addresses and round-robin
DNS to loadbalance clients across the cluster.
@@ -299,7 +314,7 @@ ctdb will try to reassign public IP addresses onto the new node as a way to dist
all client access to the LVS address across this set of nodes. This set of nodes are all LVS capable nodes that are HEALTHY, or if no HEALTHY nodes exists
all LVS capable nodes regardless of health status.
LVS will however never loadbalance traffic to nodes that are BANNED,
- DISABLED or DISCONNECTED. The "ctdb lvs" command is used to show
+ STOPPED, DISABLED or DISCONNECTED. The "ctdb lvs" command is used to show
which nodes are currently load-balanced across.
One of the these nodes are elected as the LVSMASTER. This node receives all
@@ -329,7 +344,7 @@ ctdb will try to reassign public IP addresses onto the new node as a way to dist
the processing node back to the clients. For read-intensive i/o patterns you can acheive very high throughput rates in this mode.
Note: you can use LVS and public addresses at the same time.
-
+
To activate LVS on a CTDB node you must specify CTDB_PUBLIC_INTERFACE and
CTDB_LVS_PUBLIC_ADDRESS in /etc/sysconfig/ctdb.
@@ -352,7 +367,7 @@ You must also specify the "--lvs" command line argument to ctdbd to activete LVS
all of the clients from the node BEFORE you enable LVS. Also make sure
that when you ping these hosts that the traffic is routed out through the
eth0 interface.
-
It is possible to have a CTDB cluster that spans across a WAN link.
For example where you have a CTDB cluster in your datacentre but you also
want to have one additional CTDB node located at a remote branch site.
@@ -381,7 +396,7 @@ CTDB_CAPABILITY_RECMASTER=no
Verify with the command "ctdb getcapabilities" that that node no longer
has the recmaster or the lmaster capabilities.
-
Sometimes it is desireable to run services on the CTDB node which will
need to originate outgoing traffic to external servers. This might
be contacting NIS servers, LDAP servers etc. etc.
@@ -404,7 +419,7 @@ CTDB_CAPABILITY_RECMASTER=no
if there are no public addresses assigned to the node.
This is the simplest way but it uses up a lot of ip addresses since you
have to assign both static and also public addresses to each node.
-
+
A second way is to use the built in NAT-GW feature in CTDB.
With NAT-GW you assign one public NATGW address for each natgw group.
Each NATGW group is a set of nodes in the cluster that shares the same
@@ -419,7 +434,7 @@ CTDB_CAPABILITY_RECMASTER=no
In each NATGW group, one of the nodes is designated the NAT Gateway
through which all traffic that is originated by nodes in this group
will be routed through if a public addresses are not available.
-
NAT-GW is configured in /etc/sysconfigctdb by setting the following
variables:
This is an ip address in the public network that is used for all outgoing
traffic when the public addresses are not assigned.
This address will be assigned to one of the nodes in the cluster which
will masquerade all traffic for the other nodes.
Format of this parameter is IPADDRESS/NETMASK
-
This is the physical interface where the CTDB_NATGW_PUBLIC_IP will be
assigned to. This should be an interface connected to the public network.
Format of this parameter is INTERFACE
-
This is the default gateway to use on the node that is elected to host
the CTDB_NATGW_PUBLIC_IP. This is the default gateway on the public network.
Format of this parameter is IPADDRESS
-
This is the network/netmask used for the interal private network.
Format of this parameter is IPADDRESS/NETMASK
-
This is the list of all nodes that belong to the same NATGW group
as this node. The default is /etc/ctdb/natgw_nodes.
-
+ When the NAT-GW functionality is used, one of the nodes is elected
to act as a NAT router for all the other nodes in the group when
they need to originate traffic to the external public network.
@@ -497,11 +512,11 @@ CTDB_CAPABILITY_RECMASTER=no
This is implemented in the 11.natgw eventscript. Please see the
eventscript for further information.
-
CTDB has support to manage the popular anti-virus daemon ClamAV.
This support is implemented through the
eventscript : /etc/ctdb/events.d/31.clamd.
-
+
Start by configuring CLAMAV normally and test that it works. Once this is
done, copy the configuration files over to all the nodes so that all nodes
share identical CLAMAV configurations.
@@ -530,10 +545,10 @@ Once you have restarted CTDBD, use
ctdb scriptstatus
and verify that the 31.clamd eventscript is listed and that it was executed successfully.
-
Copyright (C) Andrew Tridgell 2007
Copyright (C) Ronnie sahlberg 2007
diff --git a/ctdb/doc/ctdb.1.xml b/ctdb/doc/ctdb.1.xml
index b0661fd374f..b75f3d16011 100644
--- a/ctdb/doc/ctdb.1.xml
+++ b/ctdb/doc/ctdb.1.xml
@@ -160,6 +160,13 @@
Name
Synopsis
ctdbd ctdbd [-? --help] [-d --debug=<INTEGER>] {--dbdir=<directory>} {--dbdir-persistent=<directory>} [--event-script-dir=<directory>] [-i --interactive] [--listen=<address>] [--logfile=<filename>] [--lvs] {--nlist=<filename>} [--no-lmaster] [--no-recmaster] [--nosetsched] [--public-addresses=<filename>] [--public-interface=<interface>] {--reclock=<filename>} [--single-public-ip=<address>] [--socket=<filename>] [--start-as-disabled] [--syslog] [--torture] [--transport=<STRING>] [--usage]DESCRIPTION
Name
Synopsis
ctdbd ctdbd [-? --help] [-d --debug=<INTEGER>] {--dbdir=<directory>} {--dbdir-persistent=<directory>} [--event-script-dir=<directory>] [-i --interactive] [--listen=<address>] [--logfile=<filename>] [--lvs] {--nlist=<filename>} [--no-lmaster] [--no-recmaster] [--nosetsched] [--public-addresses=<filename>] [--public-interface=<interface>] {--reclock=<filename>} [--single-public-ip=<address>] [--socket=<filename>] [--start-as-disabled] [--start-as-stopped] [--syslog] [--torture] [--transport=<STRING>] [--usage]DESCRIPTION
OPTIONS
OPTIONS
Private vs Public addresses
Private address
Private address
Public address
Node status
PUBLIC TUNABLES
PUBLIC TUNABLES
KeepaliveInterval
KeepaliveLimit
MonitorInterval
TickleUpdateInterval
EventScriptTimeout
RecoveryBanPeriod
DatabaseHashSize
RerecoveryTimeout
EnableBans
DeterministicIPs
DisableWhenUnhealthy
NoIPFailback
LVS
Configuration
Configuration
REMOTE CLUSTER NODES
NAT-GW
NAT-GW
NAT-GW
Configuration
@@ -458,32 +473,32 @@ CTDB_CAPABILITY_RECMASTER=no
# CTDB_NATGW_DEFAULT_GATEWAY=10.0.0.1
# CTDB_NATGW_PRIVATE_NETWORK=10.1.1.0/24
# CTDB_NATGW_NODES=/etc/ctdb/natgw_nodes
-
CTDB_NATGW_PUBLIC_IP
CTDB_NATGW_PUBLIC_IFACE
CTDB_NATGW_DEFAULT_GATEWAY
CTDB_NATGW_PRIVATE_NETWORK
CTDB_NATGW_NODES
Operation
ClamAV Daemon
Configuration
Configuration
COPYRIGHT/LICENSE
+ COPYRIGHT/LICENSE
Copyright (C) Andrew Tridgell 2007
Copyright (C) Ronnie sahlberg 2007
diff --git a/ctdb/doc/ctdbd.1.xml b/ctdb/doc/ctdbd.1.xml
index 18db0986d8e..992500c54b4 100644
--- a/ctdb/doc/ctdbd.1.xml
+++ b/ctdb/doc/ctdbd.1.xml
@@ -39,6 +39,7 @@