-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>ctdbd</title><meta name="generator" content="DocBook XSL Stylesheets V1.7
1.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="ctdbd.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>ctdbd — The CTDB cluster daemon</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="command">ctdbd</code> </p></div><div class="cmdsynopsis"><p><code class="command">ctdbd</code> [-? --help] [-d --debug=<INTEGER>] {--dbdir=<directory>} {--dbdir-persistent=<directory>} [--event-script-dir=<directory>] [-i --interactive] [--listen=<address>] [--logfile=<filename>] {--nlist=<filename>} [--nosetsched] [--public-addresses=<filename>] [--public-interface=<interface>] {--reclock=<filename>} [--single-public-ip=<address>] [--socket=<filename>] [--syslog] [--torture] [--transport=<STRING>] [--usage]</p></div></div><div class="refsect1" lang="en"><a name="id2481142"></a><h2>DESCRIPTION</h2><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>ctdbd</title><meta name="generator" content="DocBook XSL Stylesheets V1.7
3.2"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="ctdbd.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>ctdbd — The CTDB cluster daemon</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="command">ctdbd</code> </p></div><div class="cmdsynopsis"><p><code class="command">ctdbd</code> [-? --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] {--notification-script=<filename>} [--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]</p></div></div><div class="refsect1" lang="en"><a name="id2479664"></a><h2>DESCRIPTION</h2><p>
ctdbd is the main ctdb daemon.
</p><p>
ctdbd provides a clustered version of the TDB database with automatic rebuild/recovery of the databases upon nodefailures.
</p><p>
ctdbd provides monitoring of all nodes in the cluster and automatically reconfigures the cluster and recovers upon node failures.
</p><p>
- ctdbd is the main component in clustered Samba that provides a high-awailability load-sharing CIFS server cluster.
- </p></div><div class="refsect1" lang="en"><a name="id24
81175"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-? --help</span></dt><dd><p>
+ ctdbd is the main component in clustered Samba that provides a high-availability load-sharing CIFS server cluster.
+ </p></div><div class="refsect1" lang="en"><a name="id24
79695"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-? --help</span></dt><dd><p>
Print some help text to the screen.
</p></dd><dt><span class="term">-d --debug=<DEBUGLEVEL></span></dt><dd><p>
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.
This option is only required when you want to run multiple ctdbd daemons/nodes on the same physical host in which case there would be multiple entries in /etc/ctdb/nodes what would match a local interface.
</p></dd><dt><span class="term">--logfile=<filename></span></dt><dd><p>
This is the file where ctdbd will write its log. This is usually /var/log/log.ctdb .
+ </p></dd><dt><span class="term">--lvs</span></dt><dd><p>
+ This option is used to activate the LVS capability on a CTDB node.
+ Please see the LVS section.
</p></dd><dt><span class="term">--nlist=<filename></span></dt><dd><p>
This file contains a list of the private ip addresses of every node in the cluster. There is one line/ip address for each node. This file must be the same for all nodes in the cluster.
</p><p>
This file is usually /etc/ctdb/nodes .
+ </p></dd><dt><span class="term">--no-lmaster</span></dt><dd><p>
+ This argument specifies that this node can NOT become an lmaster
+ for records in the database. This means that it will never show up
+ in the vnnmap. This feature is primarily used for making a cluster
+ span across a WAN link and use CTDB as a WAN-accelerator.
+ </p><p>
+ Please see the "remote cluster nodes" section for more information.
+ </p></dd><dt><span class="term">--no-recmaster</span></dt><dd><p>
+ This argument specifies that this node can NOT become a recmaster
+ for the database. This feature is primarily used for making a cluster
+ span across a WAN link and use CTDB as a WAN-accelerator.
+ </p><p>
+ Please see the "remote cluster nodes" section for more information.
</p></dd><dt><span class="term">--nosetsched</span></dt><dd><p>
This is a ctdbd debugging option. this option is only used when
debugging ctdbd.
This is useful for debugging and when you want to run ctdbd under
valgrind or gdb. (You dont want to attach valgrind or gdb to a
real-time process.)
+ </p></dd><dt><span class="term">--notification-script=<filename></span></dt><dd><p>
+ This specifies a script which will be invoked by ctdb when certain
+ state changes occur in ctdbd and when you may want to trigger this
+ to run certain scripts.
+ </p><p>
+ This file is usually /etc/ctdb/notify.sh .
+ </p><p>
+ See the NOTIFICATION SCRIPT section below for more information.
</p></dd><dt><span class="term">--public_addresses=<filename></span></dt><dd><p>
When used with IP takeover this specifies a file containing the public ip addresses to use on the cluster. This file contains a list of ip addresses netmasks and interfaces. When ctdb is operational it will distribute these public ip addresses evenly across the available nodes.
</p><p>
to and also where to attach the single-public-ip when used.
</p><p>
This is only required when using public ip addresses and only when
- you dont specify the interface explicitely on in /etc/ctdb/public_addresses or when you are using --single-public-ip.
+ you dont specify the interface explicitly in /etc/ctdb/public_addresses or when you are using --single-public-ip.
</p><p>
If you omit this argument when using public addresses or single public ip, ctdb will not be able to send out Gratious ARPs correctly or be able to kill tcp connections correctly which will lead to application failures.
</p></dd><dt><span class="term">--reclock=<filename></span></dt><dd><p>
- This is the name of the lock file stored of the shared cluster filesystem that ctdbd uses to arbitrate which node has the role of recovery-master.
+ This is the name of the lock file stored of the shared cluster filesystem that ctdbd uses to prevent split brains from occuring.
This file must be stored on shared storage.
- </p></dd><dt><span class="term">--single-public-ip=<address></span></dt><dd><p>
- This option is used to activate the "ipmux" or the "lvs"
- functionality of ctdb where the cluster provides a single
- public ip address for the entire cluster. When using this option
- you must also use the --public-interface option.
- </p><p>
- In this mode, all nodes of the cluster will expose a single
- ip address from all nodes with all incoming traffic to the cluster
- being passed through the current recmaster. This functionality
- is similar to using a load-balancing switch.
- </p><p>
- All incoming packets are sent to the recmaster which will multiplex
- the clients across all available nodes and pass the packets on to
- a different node in the cluster to manage the connection based
- on the clients ip address. Outgoing packets however are sent
- directly from the node that was choosen back to the client.
- Since all incoming packets are sent through the recmaster this will
- have a throughput and performance impact when used. This impact
- in performance primarily affects write-performance while
- read-performance should be mainly unaffected.
- Only use this feature if your environment is mostly-read
- (i.e. most traffic is from the nodes back to the clients) or
- if it is not important to get maximum write-performance to the
- cluster.
</p><p>
- This feature is completely controlled from the eventscripts and
- does not require any CTDBD involvement. However, the CTDBD daemon
- does need to know that the "single public ip" exists so that the
- CTDBD daemon will allow clients to set up killtcp to work on this
- ip address.
- </p><p>
- CTDBD only allows clients to use killtcp to kill off (RST) tcp
- connections to/from an ip address that is either a normal public
- address or to/from the ip address specified by --single-public-ip.
- No other tcp connections are allowed to be specified with killtcp.
- </p></dd><dt><span class="term">--socket=<filename></span></dt><dd><p>
+ It is possible to run CTDB without a reclock file, but then there
+ will be no protection against split brain if the network becomes
+ partitioned. Using CTDB without a reclock file is strongly
+ discouraged.
+ </p></dd><dt><span class="term">--socket=<filename></span></dt><dd><p>
This specifies the name of the domain socket that ctdbd will create. This socket is used for local clients to attach to and communicate with the ctdbd daemon.
</p><p>
The default is /tmp/ctdb.socket . You only need to use this option if you plan to run multiple ctdbd daemons on the same physical host.
+ </p></dd><dt><span class="term">--start-as-disabled</span></dt><dd><p>
+ This makes the ctdb daemon to be DISABLED when it starts up.
+ </p><p>
+ As it is DISABLED it will not get any of the public ip addresses
+ allocated to it, and thus this allow you to start ctdb on a node
+ without causing any ip address to failover from other nodes onto
+ the new node.
+ </p><p>
+ When used, the administrator must keep track of when nodes start and
+ manually enable them again using the "ctdb enable" command, or else
+ the node will not host any services.
+ </p><p>
+ A node that is DISABLED will not host any services and will not be
+ reachable/used by any clients.
+ </p></dd><dt><span class="term">--start-as-stopped</span></dt><dd><p>
+ This makes the ctdb daemon to be STOPPED when it starts up.
+ </p><p>
+ 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.
+ </p><p>
+ To restart and activate a STOPPED node, the command "ctdb continue" is used.
+ </p><p>
+ A node that is STOPPED will not host any services and will not be
+ reachable/used by any clients.
</p></dd><dt><span class="term">--syslog</span></dt><dd><p>
Send all log messages to syslog instead of to the ctdb logfile.
</p></dd><dt><span class="term">--torture</span></dt><dd><p>
</p></dd><dt><span class="term">--transport=<STRING></span></dt><dd><p>
This option specifies which transport to use for ctdbd internode communications. The default is "tcp".
</p><p>
- Suported transports are "tcp" and "infiniband".
+ Currently only "tcp" is supported but "infiniband" might be
+ implemented in the future.
</p></dd><dt><span class="term">--usage</span></dt><dd><p>
Print useage information to the screen.
- </p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2528
652"></a><h2>Private vs Public addresses</h2><p>
+ </p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2528
852"></a><h2>Private vs Public addresses</h2><p>
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.
- </p><div class="refsect2" lang="en"><a name="id2528
662"></a><h3>Private address</h3><p>
+ </p><div class="refsect2" lang="en"><a name="id2528
863"></a><h3>Private address</h3><p>
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
10.1.1.2
10.1.1.3
10.1.1.4
- </pre></div><div class="refsect2" lang="en"><a name="id2528
711"></a><h3>Public address</h3><p>
+ </pre></div><div class="refsect2" lang="en"><a name="id2528
911"></a><h3>Public address</h3><p>
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.
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.
- </p></div></div><div class="refsect1" lang="en"><a name="id2528
793"></a><h2>Node status</h2><p>
+ </p></div></div><div class="refsect1" lang="en"><a name="id2528
993"></a><h2>Node status</h2><p>
The current status of each node in the cluster can be viewed by the
'ctdb status' command.
</p><p>
- There are five possible for a node.
+ There are five possible states for a node.
</p><p>
OK - This node is fully functional.
</p><p>
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.
- </p></div><div class="refsect1" lang="en"><a name="id2528850"></a><h2>SEE ALSO</h2><p>
+ </p><p>
+ 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.
+ </p></div><div class="refsect1" lang="en"><a name="id2529059"></a><h2>PUBLIC TUNABLES</h2><p>
+ These are the public tuneables that can be used to control how ctdb behaves.
+ </p><div class="refsect2" lang="en"><a name="id2529070"></a><h3>KeepaliveInterval</h3><p>Default: 1</p><p>
+ How often should the nodes send keepalives to eachother.
+ </p></div><div class="refsect2" lang="en"><a name="id2529083"></a><h3>KeepaliveLimit</h3><p>Default: 5</p><p>
+ After how many keepalive intervals without any traffic should a node
+ wait until marking the peer as DISCONNECTED.
+ </p></div><div class="refsect2" lang="en"><a name="id2529098"></a><h3>MonitorInterval</h3><p>Default: 15</p><p>
+ How often should ctdb run the event scripts to check for a nodes health.
+ </p></div><div class="refsect2" lang="en"><a name="id2529112"></a><h3>TickleUpdateInterval</h3><p>Default: 20</p><p>
+ How often will ctdb record and store the "tickle" information used to
+ kickstart stalled tcp connections after a recovery.
+ </p></div><div class="refsect2" lang="en"><a name="id2529126"></a><h3>EventScriptTimeout</h3><p>Default: 20</p><p>
+ How long should ctdb let an event script run before aborting it and
+ marking the node unhealthy.
+ </p></div><div class="refsect2" lang="en"><a name="id2529140"></a><h3>RecoveryBanPeriod</h3><p>Default: 300</p><p>
+ 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.
+ </p></div><div class="refsect2" lang="en"><a name="id2529160"></a><h3>DatabaseHashSize</h3><p>Default: 100000</p><p>
+ Size of the hash chains for the local store of the tdbs that ctdb manages.
+ </p></div><div class="refsect2" lang="en"><a name="id2529174"></a><h3>RerecoveryTimeout</h3><p>Default: 10</p><p>
+ Once a recovery has completed, no additional recoveries are permitted until this timeout has expired.
+ </p></div><div class="refsect2" lang="en"><a name="id2529188"></a><h3>EnableBans</h3><p>Default: 1</p><p>
+ 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.
+ </p></div><div class="refsect2" lang="en"><a name="id2529203"></a><h3>DeterministicIPs</h3><p>Default: 1</p><p>
+ 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.
+ </p><p>
+ 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.
+ </p></div><div class="refsect2" lang="en"><a name="id2529228"></a><h3>DisableWhenUnhealthy</h3><p>Default: 0</p><p>
+ 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'.
+ </p><p>
+ 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.
+ </p></div><div class="refsect2" lang="en"><a name="id2529252"></a><h3>NoIPFailback</h3><p>Default: 0</p><p>
+ 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.
+ </p><p>
+ 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.
+ </p><p>
+ 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.
+ </p></div></div><div class="refsect1" lang="en"><a name="id2529288"></a><h2>LVS</h2><p>
+ 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.
+ </p><p>
+ This is similar to using a layer-4 loadbalancing switch but with some restrictions.
+ </p><p>
+ In this mode the cluster select a set of nodes in the cluster and loadbalance
+ 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,
+ STOPPED, DISABLED or DISCONNECTED. The "ctdb lvs" command is used to show
+ which nodes are currently load-balanced across.
+ </p><p>
+ One of the these nodes are elected as the LVSMASTER. This node receives all
+ traffic from clients coming in to the LVS address and multiplexes it
+ across the internal network to one of the nodes that LVS is using.
+ When responding to the client, that node will send the data back
+ directly to the client, bypassing the LVSMASTER node.
+ The command "ctdb lvsmaster" will show which node is the current
+ LVSMASTER.
+ </p><p>
+ The path used for a client i/o is thus :
+ </p><pre class="screen">
+ (1) Client sends request packet to LVSMASTER
+ (2) LVSMASTER passes the request on to one node across the internal network.
+ (3) Selected node processes the request.
+ (4) Node responds back to client.
+ </pre><p>
+ </p><p>
+ This means that all incoming traffic to the cluster will pass through
+ one physical node, which limits scalability. You can send more data to the
+ LVS address that one physical node can multiplex. This means that you
+ should not use LVS if your I/O pattern is write-intensive since you will be
+ limited in the available network bandwidth that node can handle.
+ LVS does work wery well for read-intensive workloads where only smallish
+ READ requests are going through the LVSMASTER bottleneck and the majority
+ of the traffic volume (the data in the read replies) goes straight from
+ the processing node back to the clients. For read-intensive i/o patterns you can acheive very high throughput rates in this mode.
+ </p><p>
+ Note: you can use LVS and public addresses at the same time.
+ </p><div class="refsect2" lang="en"><a name="id2529360"></a><h3>Configuration</h3><p>
+ To activate LVS on a CTDB node you must specify CTDB_PUBLIC_INTERFACE and
+ CTDB_LVS_PUBLIC_ADDRESS in /etc/sysconfig/ctdb.
+ </p><p>
+You must also specify the "--lvs" command line argument to ctdbd to activete LVS as a capability of the node. This should be done automatically for you by the /etc/init.d/ctdb script.
+ </p><p>
+ Example:
+ </p><pre class="screen">
+ CTDB_PUBLIC_INTERFACE=eth0
+ CTDB_LVS_PUBLIC_IP=10.0.0.237
+ </pre><p>
+ </p></div><p>
+ If you use LVS, you must still have a real/permanent address configured
+ for the public interface on each node. This address must be routable
+ and the cluster nodes must be configured so that all traffic back to client
+ hosts are routed through this interface. This is also required in order
+ to allow samba/winbind on the node to talk to the domain controller.
+ (we can not use the lvs IP address to initiate outgoing traffic)
+ </p><p>
+ I.e. make sure that you can "ping" both the domain controller and also
+ 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.
+ </p></div><div class="refsect1" lang="en"><a name="id2529408"></a><h2>REMOTE CLUSTER NODES</h2><p>
+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.
+This is similar to how a WAN accelerator works but with the difference
+that while a WAN-accelerator often acts as a Proxy or a MitM, in
+the ctdb remote cluster node configuration the Samba instance at the remote site
+IS the genuine server, not a proxy and not a MitM, and thus provides 100%
+correct CIFS semantics to clients.
+ </p><p>
+ See the cluster as one single multihomed samba server where one of
+ the NICs (the remote node) is very far away.
+ </p><p>
+ NOTE: This does require that the cluster filesystem you use can cope
+ with WAN-link latencies. Not all cluster filesystems can handle
+ WAN-link latencies! Whether this will provide very good WAN-accelerator
+ performance or it will perform very poorly depends entirely
+ on how optimized your cluster filesystem is in handling high latency
+ for data and metadata operations.
+ </p><p>
+ To activate a node as being a remote cluster node you need to set
+ the following two parameters in /etc/sysconfig/ctdb for the remote node:
+ </p><pre class="screen">
+CTDB_CAPABILITY_LMASTER=no
+CTDB_CAPABILITY_RECMASTER=no
+ </pre><p>
+ </p><p>
+ Verify with the command "ctdb getcapabilities" that that node no longer
+ has the recmaster or the lmaster capabilities.
+ </p></div><div class="refsect1" lang="en"><a name="id2529459"></a><h2>NAT-GW</h2><p>
+ 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.
+ </p><p>
+ This can sometimes be problematic since there are situations when a
+ node does not have any public ip addresses assigned. This could
+ be due to the nobe just being started up and no addresses have been
+ assigned yet or it could be that the node is UNHEALTHY in which
+ case all public addresses have been migrated off.
+ </p><p>
+ If then the service status of CTDB depends on such services being
+ able to always being able to originate traffic to external resources
+ this becomes extra troublesome. The node might be UNHEALTHY because
+ the service can not be reached, and the service can not be reached
+ because the node is UNHEALTHY.
+ </p><p>
+ There are two ways to solve this problem. The first is by assigning a
+ static ip address for one public interface on every node which will allow
+ every node to be able to route traffic to the public network even
+ 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.
+ </p><div class="refsect2" lang="en"><a name="id2529499"></a><h3>NAT-GW</h3><p>
+ 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
+ NATGW address to talk to the outside world. Normally there would only be
+ one NATGW group spanning the entire cluster, but in situations where one
+ ctdb cluster spans multiple physical sites it is useful to have one
+ NATGW group for each of the two sites.
+ </p><p>
+ There can be multiple NATGW groups in one cluster but each node can only
+ be member of one NATGW group.
+ </p><p>
+ 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.
+ </p></div><div class="refsect2" lang="en"><a name="id2529529"></a><h3>Configuration</h3><p>
+ NAT-GW is configured in /etc/sysconfigctdb by setting the following
+ variables:
+ </p><pre class="screen">
+# NAT-GW configuration
+# Some services running on nthe CTDB node may need to originate traffic to
+# remote servers before the node is assigned any IP addresses,
+# This is problematic since before the node has public addresses the node might
+# not be able to route traffic to the public networks.
+# One solution is to have static public addresses assigned with routing
+# in addition to the public address interfaces, thus guaranteeing that
+# a node always can route traffic to the external network.
+# This is the most simple solution but it uses up a large number of
+# additional ip addresses.
+#
+# A more complex solution is NAT-GW.
+# In this mode we only need one additional ip address for the cluster from
+# the exsternal public network.
+# One of the nodes in the cluster is elected to be hosting this ip address
+# so it can reach the external services. This node is also configured
+# to use NAT MASQUERADING for all traffic from the internal private network
+# to the external network. This node is the NAT-GW node.
+#
+# All other nodes are set up with a default rote with a metric of 10 to point
+# to the nat-gw node.
+#
+# The effect of this is that only when a node does not have a public address
+# and thus no proper routes to the external world it will instead
+# route all packets through the nat-gw node.
+#
+# CTDB_NATGW_NODES is the list of nodes that belong to this natgw group.
+# You can have multiple natgw groups in one cluster but each node
+# can only belong to one single natgw group.
+#
+# CTDB_NATGW_PUBLIC_IP=10.0.0.227/24
+# CTDB_NATGW_PUBLIC_IFACE=eth0
+# CTDB_NATGW_DEFAULT_GATEWAY=10.0.0.1
+# CTDB_NATGW_PRIVATE_NETWORK=10.1.1.0/24
+# CTDB_NATGW_NODES=/etc/ctdb/natgw_nodes
+ </pre></div><div class="refsect2" lang="en"><a name="id2529545"></a><h3>CTDB_NATGW_PUBLIC_IP</h3><p>
+ 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.
+ </p><p>
+ Format of this parameter is IPADDRESS/NETMASK
+ </p></div><div class="refsect2" lang="en"><a name="id2529563"></a><h3>CTDB_NATGW_PUBLIC_IFACE</h3><p>
+ 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.
+ </p><p>
+ Format of this parameter is INTERFACE
+ </p></div><div class="refsect2" lang="en"><a name="id2475745"></a><h3>CTDB_NATGW_DEFAULT_GATEWAY</h3><p>
+ 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.
+ </p><p>
+ Format of this parameter is IPADDRESS
+ </p></div><div class="refsect2" lang="en"><a name="id2475761"></a><h3>CTDB_NATGW_PRIVATE_NETWORK</h3><p>
+ This is the network/netmask used for the interal private network.
+ </p><p>
+ Format of this parameter is IPADDRESS/NETMASK
+ </p></div><div class="refsect2" lang="en"><a name="id2475775"></a><h3>CTDB_NATGW_NODES</h3><p>
+ This is the list of all nodes that belong to the same NATGW group
+ as this node. The default is /etc/ctdb/natgw_nodes.
+ </p></div><div class="refsect2" lang="en"><a name="id2475786"></a><h3>Operation</h3><p>
+ 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.
+ </p><p>
+ The NAT-GW node is assigned the CTDB_NATGW_PUBLIC_IP to the designated
+ interface and the provided default route. The NAT-GW is configured
+ to act as a router and to masquerade all traffic it receives from the
+ internal private network and which is destined to the external network(s).
+ </p><p>
+ All other nodes in the group are configured with a default route of
+ metric 10 pointing to the designated NAT GW node.
+ </p><p>
+ This is implemented in the 11.natgw eventscript. Please see the
+ eventscript for further information.
+ </p></div><div class="refsect2" lang="en"><a name="id2475818"></a><h3>Removing/Changing NATGW at runtime</h3><p>
+ The following are the procedures to change/remove a NATGW configuration
+ at runtime, without having to restart ctdbd.
+ </p><p>
+ If you want to remove NATGW completely from a node, use these steps:
+ </p><pre class="screen">
+1, Run 'CTDB_BASE=/etc/ctdb /etc/ctdb/events.d/11.natgw removenatgw'
+2, Then remove the configuration from /etc/sysconfig/ctdb
+ </pre><p>
+ If you want to change the NATGW configuration on a node :
+ </p><pre class="screen">
+1, Run 'CTDB_BASE=/etc/ctdb /etc/ctdb/events.d/11.natgw removenatgw'
+2, Then change the configuration in /etc/sysconfig/ctdb
+3, Run 'CTDB_BASE=/etc/ctdb /etc/ctdb/events.d/11.natgw updatenatgw'
+ </pre></div></div><div class="refsect1" lang="en"><a name="id2475856"></a><h2>NOTIFICATION SCRIPT</h2><p>
+ Notification scripts are used with ctdb to have a call-out from ctdb
+ to a user-specified script when certain state changes occur in ctdb.
+ This is commonly to set up either sending SNMP traps or emails
+ when a node becomes unhealthy and similar.
+ </p><p>
+ This is activated by setting CTDB_NOTIFY_SCRIPT=<your script> in the
+ sysconfig file, or by adding --notification-script=<your script>.
+ </p><p>
+ See /etc/ctdb/notify.sh for an example script.
+ </p><p>
+ CTDB currently generates notifications on these state changes:
+ </p><div class="refsect2" lang="en"><a name="id2475887"></a><h3>unhealthy</h3><p>
+ This call-out is triggered when the node changes to UNHEALTHY state.
+ </p></div><div class="refsect2" lang="en"><a name="id2475897"></a><h3>healthy</h3><p>
+ This call-out is triggered when the node changes to HEALTHY state.
+ </p></div><div class="refsect2" lang="en"><a name="id2475907"></a><h3>startup</h3><p>
+ This call-out is triggered when ctdb has started up and all managed services are up and running.
+ </p></div></div><div class="refsect1" lang="en"><a name="id2475919"></a><h2>ClamAV Daemon</h2><p>
+CTDB has support to manage the popular anti-virus daemon ClamAV.
+This support is implemented through the
+eventscript : /etc/ctdb/events.d/31.clamd.
+</p><div class="refsect2" lang="en"><a name="id2475930"></a><h3>Configuration</h3><p>
+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.
+Once this is done you can proceed with the intructions below to activate
+CTDB support for CLAMAV.
+</p><p>
+First, to activate CLAMAV support in CTDB, edit /etc/sysconfig/ctdb and add the two lines :
+</p><pre class="screen">
+CTDB_MANAGES_CLAMD=yes
+CTDB_CLAMD_SOCKET="/path/to/clamd.socket"
+</pre><p>
+Second, activate the eventscript
+</p><pre class="screen">
+ctdb enablescript 31.clamd
+</pre><p>
+Third, CTDB will now be starting and stopping this service accordingly,
+so make sure that the system is not configured to start/stop this service
+automatically.
+On RedHat systems you can disable the system starting/stopping CLAMAV automatically by running :
+</p><pre class="screen">
+chkconfig clamd off
+</pre><p>
+</p><p>
+Once you have restarted CTDBD, use
+</p><pre class="screen">
+ctdb scriptstatus
+</pre><p>
+and verify that the 31.clamd eventscript is listed and that it was executed successfully.
+</p></div></div><div class="refsect1" lang="en"><a name="id2475990"></a><h2>SEE ALSO</h2><p>
ctdb(1), onnode(1)
- <a href="http://ctdb.samba.org/" target="_top">http://ctdb.samba.org/</a>
- </p></div><div class="refsect1" lang="en"><a name="id2
528863"></a><h2>COPYRIGHT/LICENSE</h2><div class="literallayout"><p><br>
+ <a class="ulink" href="http://ctdb.samba.org/" target="_top">http://ctdb.samba.org/</a>
+ </p></div><div class="refsect1" lang="en"><a name="id2
476003"></a><h2>COPYRIGHT/LICENSE</h2><div class="literallayout"><p><br>
Copyright (C) Andrew Tridgell 2007<br>
Copyright (C) Ronnie sahlberg 2007<br>
<br>
git.samba.org / metze / ctdb / wip.git / blobdiff