From b1e7724eb803044e7dab02ecc8a80dde6b4f3a69 Mon Sep 17 00:00:00 2001 From: root Date: Sat, 10 Mar 2007 13:45:38 +1100 Subject: check the static-routes file if it exists (This used to be ctdb commit 9ce84a7915abaa987160ecbcae63128a9ed0a741) --- ctdb/tools/ctdb_diagnostics | 30 +++++++++++++++++++++++++++--- 1 file changed, 27 insertions(+), 3 deletions(-) diff --git a/ctdb/tools/ctdb_diagnostics b/ctdb/tools/ctdb_diagnostics index 8304a68f5f..df5a799096 100755 --- a/ctdb/tools/ctdb_diagnostics +++ b/ctdb/tools/ctdb_diagnostics @@ -4,7 +4,13 @@ PATH="$PATH:/sbin:/usr/sbin:/usr/lpp/mmfs/bin" -CONFIG_FILES="/etc/krb5.conf /etc/hosts /etc/ctdb/nodes /etc/sysconfig/ctdb /etc/ctdb/public_addresses /etc/resolv.conf /etc/nsswitch.conf /etc/sysctl.conf /etc/samba/smb.conf /etc/fstab /etc/multipath.conf /etc/pam.d/system-auth /etc/sysconfig/nfs /etc/exports /etc/vsftpd/vsftpd.conf" +# list of config files that must exist and that we check are the same +# on all nodes +CONFIG_FILES_MUST="/etc/krb5.conf /etc/hosts /etc/ctdb/nodes /etc/sysconfig/ctdb /etc/resolv.conf /etc/nsswitch.conf /etc/sysctl.conf /etc/samba/smb.conf /etc/fstab /etc/multipath.conf /etc/pam.d/system-auth /etc/sysconfig/nfs /etc/exports /etc/vsftpd/vsftpd.conf" + +# list of config files that may exist and should be checked that they +# are the same on all nodes +CONFIG_FILES_MAY="/etc/ctdb/public_addresses /etc/ctdb/static-routes" 2>&1 @@ -54,9 +60,27 @@ cat < $tmpf 2>&1 + cmp $f $tmpf 2>&1 || { + error "File $f is different on node $i" + diff -u $f $tmpf + } + rm -f $tmpf + done +done + +for f in $CONFIG_FILES_MAY; do [ -r "$f" ] || { - error "$f is missing" + echo "Optional file $f is not present on local node" continue; } show_file $f -- cgit From 7a11082f0fa2c367e51ec7e887a8866242987694 Mon Sep 17 00:00:00 2001 From: root Date: Sat, 10 Mar 2007 14:10:21 +1100 Subject: collect net conf list in ctdb_diagnostics (This used to be ctdb commit 0bb130090b8dce5f85b0cb178a19f877759c0caa) --- ctdb/tools/ctdb_diagnostics | 1 + 1 file changed, 1 insertion(+) diff --git a/ctdb/tools/ctdb_diagnostics b/ctdb/tools/ctdb_diagnostics index df5a799096..bba71d6c3d 100755 --- a/ctdb/tools/ctdb_diagnostics +++ b/ctdb/tools/ctdb_diagnostics @@ -226,6 +226,7 @@ Showing Samba status EOF show_all "smbstatus -n -B" show_all "net ads testjoin" +show_all "net conf list" show_all "lsof -n | grep smbd" show_all "lsof -n | grep ctdbd" show_all "netstat -tan" -- cgit From 4088e0aceb6b31f5de6b3d10a63ae4cc22c3e867 Mon Sep 17 00:00:00 2001 From: root Date: Thu, 12 Mar 2009 12:33:19 +1100 Subject: make sure we can collect proper mmfs data (This used to be ctdb commit 76d655f9aa3ebd39e7a40d0bbd85e40d08f3e90b) --- ctdb/tools/ctdb_diagnostics | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/ctdb/tools/ctdb_diagnostics b/ctdb/tools/ctdb_diagnostics index bba71d6c3d..8cf1f9ab6e 100755 --- a/ctdb/tools/ctdb_diagnostics +++ b/ctdb/tools/ctdb_diagnostics @@ -206,11 +206,11 @@ EOF show_all "/usr/lpp/mmfs/bin/mmlsmgr" devlist=`mmlsfs all|grep ^File.system.attributes | cut -d/ -f3 | cut -d: -f1` for d in $devlist; do - show_all mmdf $d - show_all mmlsdisk $d - show_all mmlsfileset $d - show_all mmlspolicy $d - show_all mmlssnapshot $d + show_all "mmdf $d" + show_all "mmlsdisk $d" + show_all "mmlsfileset $d" + show_all "mmlspolicy $d" + show_all "mmlssnapshot $d" done fslist=`mount|grep type.gpfs|awk '{print $1}'` for fs in $fslist; do -- cgit From 869941c0cf6223107c83f2312729a542374e15c6 Mon Sep 17 00:00:00 2001 From: Ronnie Sahlberg Date: Mon, 16 Mar 2009 09:21:24 +1100 Subject: From C Cowan, AIX needs to set sockaddr.sa_len to a consistent value for the address type used or the connect() call will fail. (This used to be ctdb commit d416c0e1e57a42f7ab52de903dbd8b5e111decfe) --- ctdb/tcp/tcp_connect.c | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/ctdb/tcp/tcp_connect.c b/ctdb/tcp/tcp_connect.c index 8efb597443..ac443d1f8e 100644 --- a/ctdb/tcp/tcp_connect.c +++ b/ctdb/tcp/tcp_connect.c @@ -129,6 +129,7 @@ void ctdb_tcp_node_connect(struct event_context *ev, struct timed_event *te, struct ctdb_context *ctdb = node->ctdb; ctdb_sock_addr sock_in; int sockin_size; + int sockout_size; ctdb_sock_addr sock_out; ctdb_tcp_stop_connection(node); @@ -167,12 +168,20 @@ void ctdb_tcp_node_connect(struct event_context *ev, struct timed_event *te, if (ctdb_tcp_get_address(ctdb, ctdb->address.address, &sock_in) != 0) { return; } + + /* AIX libs check to see if the socket address and length + arguments are consistent with each other on calls like + connect(). Can not get by with just sizeof(sock_in), + need sizeof(sock_in.ip). + */ switch (sock_in.sa.sa_family) { case AF_INET: sockin_size = sizeof(sock_in.ip); + sockout_size = sizeof(sock_out.ip); break; case AF_INET6: sockin_size = sizeof(sock_in.ip6); + sockout_size = sizeof(sock_out.ip6); break; default: DEBUG(DEBUG_ERR, (__location__ " unknown family %u\n", @@ -181,10 +190,11 @@ void ctdb_tcp_node_connect(struct event_context *ev, struct timed_event *te, } #ifdef HAVE_SOCK_SIN_LEN sock_in.ip.sin_len = sockin_size; + sock_out.ip.sin_len = sockout_size; #endif bind(tnode->fd, (struct sockaddr *)&sock_in, sockin_size); - if (connect(tnode->fd, (struct sockaddr *)&sock_out, sizeof(sock_out)) != 0 && + if (connect(tnode->fd, (struct sockaddr *)&sock_out, sockout_size) != 0 && errno != EINPROGRESS) { ctdb_tcp_stop_connection(node); tnode->connect_te = event_add_timed(ctdb->ev, tnode, -- cgit From 5804af9a11ed93f6dc3096f8f41fc213e0427de7 Mon Sep 17 00:00:00 2001 From: Ronnie Sahlberg Date: Mon, 16 Mar 2009 09:27:56 +1100 Subject: new version 1.0.74 (This used to be ctdb commit 0772190203d501a39072f16948604742d7d59a5e) --- ctdb/packaging/RPM/ctdb.spec | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/ctdb/packaging/RPM/ctdb.spec b/ctdb/packaging/RPM/ctdb.spec index 66ca3301c9..1d83627c5a 100644 --- a/ctdb/packaging/RPM/ctdb.spec +++ b/ctdb/packaging/RPM/ctdb.spec @@ -4,7 +4,7 @@ Summary: Clustered TDB Vendor: Samba Team Packager: Samba Team Name: ctdb -Version: 1.0.73 +Version: 1.0.74 Release: 1 Epoch: 0 License: GNU GPL version 3 @@ -128,6 +128,11 @@ fi %{_includedir}/ctdb_private.h %changelog +* Mon Mar 16 2009 : Version 1.0.74 + - Fixes to AIX from C Cowan. + - Fixes to ctdb_diagnostics so we collect correct GPFS data + - Fixes to the net conf list command in ctdb_diagnostics + - Check the static-routes file IFF it exists in ctdb_diagnostics * Wed Mar 4 2009 : Version 1.0.73 - Add possibility to disable the check of shares for NFS and Samba - From Sumit Bose, fix dependencies so make -j works -- cgit From 32391ec844715fe888c71e93e4ae962d39db4af0 Mon Sep 17 00:00:00 2001 From: root Date: Tue, 17 Mar 2009 07:35:53 +1100 Subject: NAT-GW updates. Describe the functionality in the sysconfig file (This used to be ctdb commit 4c598ab6f8e9b826d437b9ab869c4490f7c4faba) --- ctdb/config/ctdb.sysconfig | 37 ++++++++++++++++++++ ctdb/config/events.d/11.natgw | 79 +++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 116 insertions(+) create mode 100644 ctdb/config/events.d/11.natgw diff --git a/ctdb/config/ctdb.sysconfig b/ctdb/config/ctdb.sysconfig index db5d16c3fe..bcc1184225 100644 --- a/ctdb/config/ctdb.sysconfig +++ b/ctdb/config/ctdb.sysconfig @@ -128,6 +128,43 @@ # CTDB_CAPABILITY_RECMASTER=yes # CTDB_CAPABILITY_LMASTER=yes +# 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 policy routing so that all traffic with +# a source address of the private network and a destination outside of +# the private network are instead routed through the NAT-GW node. +# +# The effect of this is that only when a node does not have a public address +# or a route to the external network will the node use the private address +# as the source address and only then will it use the policy routing +# through the NAT-GW. +# As long as a node has a public address and can route to the external network +# the node will always pick the public address as the source address and NAT-GW +# routing will not be used. +#NATGW_PUBLIC_IP=10.0.0.227/24 +#NATGW_PUBLIC_IFACE=eth0 +#NATGW_DEFAULT_GATEWAY=10.0.0.1 +#NATGW_PRIVATE_IFACE=eth0 +#NATGW_PRIVATE_NETWORK=10.0.0.0/24 + + # where to log messages # the default is /var/log/log.ctdb # CTDB_LOGFILE=/var/log/log.ctdb diff --git a/ctdb/config/events.d/11.natgw b/ctdb/config/events.d/11.natgw new file mode 100644 index 0000000000..23fe4ae32c --- /dev/null +++ b/ctdb/config/events.d/11.natgw @@ -0,0 +1,79 @@ +#!/bin/sh +# Script to set up one of the nodes as a NAT gateway for all other nodes. +# This is used to ensure that all nodes in the cluster can still originate +# traffic to the external network even if there are no public addresses +# available. +# + +. $CTDB_BASE/functions +loadconfig ctdb + +[ -z "$NATGW_PUBLIC_INTERFACE" ] && exit 0 + +cmd="$1" +shift +PATH=/usr/bin:/bin:/usr/sbin:/sbin:$PATH + +case $cmd in + recovered) + MYPNN=`ctdb pnn | cut -d: -f2` + + # Find the first connected node + FIRST=`ctdb status -Y | grep ":0:$" | head -1` + FIRSTNODE=`echo $FIRST | cut -d: -f2` + FIRSTIP=`echo $FIRST | cut -d: -f3` + + # Delete everything that might have been set in a previous iteration + # when we were not the NAT-GW + ip rule del fwmark 11 table 11 >/dev/null 2>/dev/null + iptables -D OUTPUT -t mangle -s $NATGW_PRIVATE_NETWORK -d ! $NATGW_PRIVATE_NETWORK -j MARK --set-mark 11 >/dev/null 2>/dev/null + iptables -D OUTPUT -t mangle -s $NATGW_PRIVATE_NETWORK -d ! $NATGW_PRIVATE_NETWORK -p tcp --sport 22 -j ACCEPT >/dev/null 2>/dev/null + ip route del $NATGW_PRIVATE_NETWORK dev $NATGW_PRIVATE_IFACE table 11 >/dev/null 2>/dev/null + ip route del 0.0.0.0/0 dev $NATGW_PRIVATE_IFACE table 11 >/dev/null 2>/dev/null + + # Delete the masquerading setup from a previous iteration where we + # was the NAT-GW + iptables -D POSTROUTING -t nat -s $NATGW_PRIVATE_NETWORK -d ! $NATGW_PRIVATE_NETWORK -j MASQUERADE >/dev/null 2>/dev/null + ip addr del $NATGW_PUBLIC_IP dev $NATGW_PUBLIC_IFACE >/dev/null 2>/dev/null + + if [ "$FIRSTNODE" == "$MYPNN" ]; then + # This is the first node, set it up as the NAT GW + echo 1 >/proc/sys/net/ipv4/ip_forward + iptables -A POSTROUTING -t nat -s $NATGW_PRIVATE_NETWORK -d ! $NATGW_PRIVATE_NETWORK -j MASQUERADE + ip addr add $NATGW_PUBLIC_IP dev $NATGW_PUBLIC_IFACE + ip route add 0.0.0.0/0 via $NATGW_DEFAULT_GATEWAY >/dev/null 2>/dev/null + else + # This is not the NAT-GW + # We now need to set up a separate routing table for + # all traffic we originate and with a destination that is + # outside of the local private network and route these + # packets via the NAT-GW + + + # Mark all outgoing packets that have the private address + # as source address with fwmarker 11 + # We expect that the only time the the source address will be + # selected as the private address would be when there are + # no static or public addresses assigned at all to the node. + # Othervise the routing would have picked a different address. + # + # Except for traffic to the ssh daemon, so that it is easier + # to test in the lab without disrupting the ssh sessions + iptables -A OUTPUT -t mangle -s $NATGW_PRIVATE_NETWORK -d ! $NATGW_PRIVATE_NETWORK -p tcp --sport 22 -j ACCEPT + iptables -A OUTPUT -t mangle -s $NATGW_PRIVATE_NETWORK -d ! $NATGW_PRIVATE_NETWORK -j MARK --set-mark 11 + + + # create a routing table for the natgw traffic and set it + # up with both an interface toute for the private network + # as well as a default route that goes via the NAT-GW + ip route add $NATGW_PRIVATE_NETWORK dev $NATGW_PRIVATE_IFACE table 11 + ip route add 0.0.0.0/0 via $FIRSTIP dev $NATGW_PRIVATE_IFACE table 11 >/dev/null 2>/dev/null + + # Create a rule to use routing table 11 for these packets + ip rule add fwmark 11 table 11 + fi + ;; + +esac + +exit 0 -- cgit From f037e881a228c4aaf9613f461cf5b7f21cf88d29 Mon Sep 17 00:00:00 2001 From: root Date: Wed, 18 Mar 2009 09:33:58 +1100 Subject: change the NATGW_ example in sysconfig to make it more realistic (This used to be ctdb commit 742283a8f8da7c614ee3a30d48c430e3a3bceeb9) --- ctdb/config/ctdb.sysconfig | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ctdb/config/ctdb.sysconfig b/ctdb/config/ctdb.sysconfig index bcc1184225..03b91b6088 100644 --- a/ctdb/config/ctdb.sysconfig +++ b/ctdb/config/ctdb.sysconfig @@ -161,8 +161,8 @@ #NATGW_PUBLIC_IP=10.0.0.227/24 #NATGW_PUBLIC_IFACE=eth0 #NATGW_DEFAULT_GATEWAY=10.0.0.1 -#NATGW_PRIVATE_IFACE=eth0 -#NATGW_PRIVATE_NETWORK=10.0.0.0/24 +#NATGW_PRIVATE_IFACE=eth1 +#NATGW_PRIVATE_NETWORK=10.1.1.0/24 # where to log messages -- cgit From c9d7c06b61809ab9a3ffecaa5d9493bd48d7cf39 Mon Sep 17 00:00:00 2001 From: Ronnie Sahlberg Date: Wed, 18 Mar 2009 10:05:00 +1100 Subject: add documentation for the NAT-GW feature (This used to be ctdb commit b6f7cddc68508e52bc65b357b0b77258ae96362a) --- ctdb/doc/ctdbd.1 | 654 ++++++++++++++++++-------------------------------- ctdb/doc/ctdbd.1.html | 117 ++++++++- ctdb/doc/ctdbd.1.xml | 164 +++++++++++++ 3 files changed, 509 insertions(+), 426 deletions(-) diff --git a/ctdb/doc/ctdbd.1 b/ctdb/doc/ctdbd.1 index 38ba41a517..c332beb9af 100644 --- a/ctdb/doc/ctdbd.1 +++ b/ctdb/doc/ctdbd.1 @@ -1,729 +1,535 @@ .\" Title: ctdbd -.\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] -.\" Generator: DocBook XSL Stylesheets v1.74.0 -.\" Date: 10/14/2008 -.\" Manual: [FIXME: manual] -.\" Source: [FIXME: source] -.\" Language: English +.\" Author: +.\" Generator: DocBook XSL Stylesheets v1.73.2 +.\" Date: 03/18/2009 +.\" Manual: +.\" Source: .\" -.TH "CTDBD" "1" "10/14/2008" "[FIXME: source]" "[FIXME: manual]" -.\" ----------------------------------------------------------------- -.\" * (re)Define some macros -.\" ----------------------------------------------------------------- -.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -.\" toupper - uppercase a string (locale-aware) -.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -.de toupper -.tr aAbBcCdDeEfFgGhHiIjJkKlLmMnNoOpPqQrRsStTuUvVwWxXyYzZ -\\$* -.tr aabbccddeeffgghhiijjkkllmmnnooppqqrrssttuuvvwwxxyyzz -.. -.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -.\" SH-xref - format a cross-reference to an SH section -.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -.de SH-xref -.ie n \{\ -.\} -.toupper \\$* -.el \{\ -\\$* -.\} -.. -.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -.\" SH - level-one heading that works better for non-TTY output -.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -.de1 SH -.\" put an extra blank line of space above the head in non-TTY output -.if t \{\ -.sp 1 -.\} -.sp \\n[PD]u -.nr an-level 1 -.set-an-margin -.nr an-prevailing-indent \\n[IN] -.fi -.in \\n[an-margin]u -.ti 0 -.HTML-TAG ".NH \\n[an-level]" -.it 1 an-trap -.nr an-no-space-flag 1 -.nr an-break-flag 1 -.\" make the size of the head bigger -.ps +3 -.ft B -.ne (2v + 1u) -.ie n \{\ -.\" if n (TTY output), use uppercase -.toupper \\$* -.\} -.el \{\ -.nr an-break-flag 0 -.\" if not n (not TTY), use normal case (not uppercase) -\\$1 -.in \\n[an-margin]u -.ti 0 -.\" if not n (not TTY), put a border/line under subheading -.sp -.6 -\l'\n(.lu' -.\} -.. -.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -.\" SS - level-two heading that works better for non-TTY output -.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -.de1 SS -.sp \\n[PD]u -.nr an-level 1 -.set-an-margin -.nr an-prevailing-indent \\n[IN] -.fi -.in \\n[IN]u -.ti \\n[SN]u -.it 1 an-trap -.nr an-no-space-flag 1 -.nr an-break-flag 1 -.ps \\n[PS-SS]u -.\" make the size of the head bigger -.ps +2 -.ft B -.ne (2v + 1u) -.if \\n[.$] \&\\$* -.. -.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -.\" BB/BE - put background/screen (filled box) around block of text -.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -.de BB -.if t \{\ -.sp -.5 -.br -.in +2n -.ll -2n -.gcolor red -.di BX -.\} -.. -.de EB -.if t \{\ -.if "\\$2"adjust-for-leading-newline" \{\ -.sp -1 -.\} -.br -.di -.in -.ll -.gcolor -.nr BW \\n(.lu-\\n(.i -.nr BH \\n(dn+.5v -.ne \\n(BHu+.5v -.ie "\\$2"adjust-for-leading-newline" \{\ -\M[\\$1]\h'1n'\v'+.5v'\D'P \\n(BWu 0 0 \\n(BHu -\\n(BWu 0 0 -\\n(BHu'\M[] -.\} -.el \{\ -\M[\\$1]\h'1n'\v'-.5v'\D'P \\n(BWu 0 0 \\n(BHu -\\n(BWu 0 0 -\\n(BHu'\M[] -.\} -.in 0 -.sp -.5v -.nf -.BX -.in -.sp .5v -.fi -.\} -.. -.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -.\" BM/EM - put colored marker in margin next to block of text -.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -.de BM -.if t \{\ -.br -.ll -2n -.gcolor red -.di BX -.\} -.. -.de EM -.if t \{\ -.br -.di -.ll -.gcolor -.nr BH \\n(dn -.ne \\n(BHu -\M[\\$1]\D'P -.75n 0 0 \\n(BHu -(\\n[.i]u - \\n(INu - .75n) 0 0 -\\n(BHu'\M[] -.in 0 -.nf -.BX -.in -.fi -.\} -.. -.\" ----------------------------------------------------------------- -.\" * set default formatting -.\" ----------------------------------------------------------------- +.TH "CTDBD" "1" "03/18/2009" "" "" .\" disable hyphenation .nh .\" disable justification (adjust text to left margin only) .ad l -.\" ----------------------------------------------------------------- -.\" * MAIN CONTENT STARTS HERE * -.\" ----------------------------------------------------------------- -.SH "Name" -ctdbd \- The CTDB cluster daemon -.SH "Synopsis" -.fam C -.HP \w'\fBctdbd\fR\ 'u +.SH "NAME" +ctdbd - The CTDB cluster daemon +.SH "SYNOPSIS" +.HP 6 \fBctdbd\fR -.fam -.fam C -.HP \w'\fBctdbd\fR\ 'u +.HP 6 \fBctdbd\fR [\-?\ \-\-help] [\-d\ \-\-debug=] {\-\-dbdir=} {\-\-dbdir\-persistent=} [\-\-event\-script\-dir=] [\-i\ \-\-interactive] [\-\-listen=
] [\-\-logfile=] [\-\-lvs] {\-\-nlist=} [\-\-no\-lmaster] [\-\-no\-recmaster] [\-\-nosetsched] [\-\-public\-addresses=] [\-\-public\-interface=] {\-\-reclock=} [\-\-single\-public\-ip=
] [\-\-socket=] [\-\-start\-as\-disabled] [\-\-syslog] [\-\-torture] [\-\-transport=] [\-\-usage] -.fam .SH "DESCRIPTION" .PP -ctdbd is the main ctdb daemon\&. +ctdbd is the main ctdb daemon\. .PP -ctdbd provides a clustered version of the TDB database with automatic rebuild/recovery of the databases upon nodefailures\&. +ctdbd provides a clustered version of the TDB database with automatic rebuild/recovery of the databases upon nodefailures\. .PP -Combined with a cluster filesystem ctdbd provides a full HA environment for services such as clustered Samba and NFS as well as other services\&. +Combined with a cluster filesystem ctdbd provides a full HA environment for services such as clustered Samba and NFS as well as other services\. .PP -ctdbd provides monitoring of all nodes in the cluster and automatically reconfigures the cluster and recovers upon node failures\&. +ctdbd provides monitoring of all nodes in the cluster and automatically reconfigures the cluster and recovers upon node failures\. .PP -ctdbd is the main component in clustered Samba that provides a high\-availability load\-sharing CIFS server cluster\&. +ctdbd is the main component in clustered Samba that provides a high\-availability load\-sharing CIFS server cluster\. .SH "OPTIONS" .PP \-? \-\-help .RS 4 -Print some help text to the screen\&. +Print some help text to the screen\. .RE .PP \-d \-\-debug= .RS 4 -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 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\. .RE .PP \-\-dbdir= .RS 4 -This is the directory on local storage where ctdbd keeps the local copy of the TDB databases\&. This directory is local for each node and should not be stored on the shared cluster filesystem\&. +This is the directory on local storage where ctdbd keeps the local copy of the TDB databases\. This directory is local for each node and should not be stored on the shared cluster filesystem\. .sp -This directory would usually be /var/ctdb \&. +This directory would usually be /var/ctdb \. .RE .PP \-\-dbdir\-persistent= .RS 4 -This is the directory on local storage where ctdbd keeps the local copy of the persistent TDB databases\&. This directory is local for each node and should not be stored on the shared cluster filesystem\&. +This is the directory on local storage where ctdbd keeps the local copy of the persistent TDB databases\. This directory is local for each node and should not be stored on the shared cluster filesystem\. .sp -This directory would usually be /etc/ctdb/persistent \&. +This directory would usually be /etc/ctdb/persistent \. .RE .PP \-\-event\-script\-dir= .RS 4 -This option is used to specify the directory where the CTDB event scripts are stored\&. +This option is used to specify the directory where the CTDB event scripts are stored\. .sp -This will normally be /etc/ctdb/events\&.d which is part of the ctdb distribution\&. +This will normally be /etc/ctdb/events\.d which is part of the ctdb distribution\. .RE .PP \-i \-\-interactive .RS 4 -By default ctdbd will detach itself from the shell and run in the background as a daemon\&. This option makes ctdbd to start in interactive mode\&. +By default ctdbd will detach itself from the shell and run in the background as a daemon\. This option makes ctdbd to start in interactive mode\. .RE .PP \-\-listen=
.RS 4 -This specifies which ip address ctdb will bind to\&. By default ctdbd will bind to the first address it finds in the /etc/ctdb/nodes file and which is also present on the local system in which case you do not need to provide this option\&. +This specifies which ip address ctdb will bind to\. By default ctdbd will bind to the first address it finds in the /etc/ctdb/nodes file and which is also present on the local system in which case you do not need to provide this option\. .sp -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\&. +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\. .RE .PP \-\-logfile= .RS 4 -This is the file where ctdbd will write its log\&. This is usually /var/log/log\&.ctdb \&. +This is the file where ctdbd will write its log\. This is usually /var/log/log\.ctdb \. .RE .PP \-\-lvs .RS 4 -This option is used to activate the LVS capability on a CTDB node\&. Please see the LVS section\&. +This option is used to activate the LVS capability on a CTDB node\. Please see the LVS section\. .RE .PP \-\-nlist= .RS 4 -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\&. +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\. .sp -This file is usually /etc/ctdb/nodes \&. +This file is usually /etc/ctdb/nodes \. .RE .PP \-\-no\-lmaster .RS 4 -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\&. +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\. .sp -Please see the "remote cluster nodes" section for more information\&. +Please see the "remote cluster nodes" section for more information\. .RE .PP \-\-no\-recmaster .RS 4 -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\&. +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\. .sp -Please see the "remote cluster nodes" section for more information\&. +Please see the "remote cluster nodes" section for more information\. .RE .PP \-\-nosetsched .RS 4 -This is a ctdbd debugging option\&. this option is only used when debugging ctdbd\&. +This is a ctdbd debugging option\. this option is only used when debugging ctdbd\. .sp -Normally ctdb will change its scheduler to run as a real\-time process\&. This is the default mode for a normal ctdbd operation to gurarantee that ctdbd always gets the cpu cycles that it needs\&. +Normally ctdb will change its scheduler to run as a real\-time process\. This is the default mode for a normal ctdbd operation to gurarantee that ctdbd always gets the cpu cycles that it needs\. .sp -This option is used to tell ctdbd to NOT run as a real\-time process and instead run ctdbd as a normal userspace process\&. 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\&.) +This option is used to tell ctdbd to NOT run as a real\-time process and instead run ctdbd as a normal userspace process\. 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\.) .RE .PP \-\-public_addresses= .RS 4 -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\&. +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\. .sp This is usually the file /etc/ctdb/public_addresses .RE .PP \-\-public\-interface= .RS 4 -This option tells ctdb which interface to attach public\-addresses to and also where to attach the single\-public\-ip when used\&. +This option tells ctdb which interface to attach public\-addresses to and also where to attach the single\-public\-ip when used\. .sp -This is only required when using public ip addresses and only when you dont specify the interface explicitly in /etc/ctdb/public_addresses or when you are using \-\-single\-public\-ip\&. +This is only required when using public ip addresses and only when you dont specify the interface explicitly in /etc/ctdb/public_addresses or when you are using \-\-single\-public\-ip\. .sp -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\&. +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\. .RE .PP \-\-reclock= .RS 4 -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 file must be stored on shared storage\&. +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 file must be stored on shared storage\. .RE .PP \-\-single\-public\-ip=
.RS 4 -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\&. +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\. .sp -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\&. +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\. .sp -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\&. +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\. .sp -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\&. +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\. .sp -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\&. +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\. .sp -Please note that ipmux is obsolete\&. Use LVS, not ipmux\&. Please see the LVS section in this manpage for instructions on how to configure and use CTDB with LVS\&. +Please note that ipmux is obsolete\. Use LVS, not ipmux\. Please see the LVS section in this manpage for instructions on how to configure and use CTDB with LVS\. .RE .PP \-\-socket= .RS 4 -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\&. +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\. .sp -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\&. +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\. .RE .PP \-\-start\-as\-disabled .RS 4 -This makes the ctdb daemon to be DISABLED when it starts up\&. +This makes the ctdb daemon to be DISABLED when it starts up\. .sp -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\&. +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\. .sp -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\&. +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\. .sp -A node that is DISABLED will not host any services and will not be reachable/used by any clients\&. +A node that is DISABLED will not host any services and will not be reachable/used by any clients\. .RE .PP \-\-syslog .RS 4 -Send all log messages to syslog instead of to the ctdb logfile\&. +Send all log messages to syslog instead of to the ctdb logfile\. .RE .PP \-\-torture .RS 4 -This option is only used for development and testing of ctdbd\&. It adds artificial errors and failures to the common codepaths in ctdbd to verify that ctdbd can recover correctly for failures\&. +This option is only used for development and testing of ctdbd\. It adds artificial errors and failures to the common codepaths in ctdbd to verify that ctdbd can recover correctly for failures\. .sp -You do NOT want to use this option unless you are developing and testing new functionality in ctdbd\&. +You do NOT want to use this option unless you are developing and testing new functionality in ctdbd\. .RE .PP \-\-transport= .RS 4 -This option specifies which transport to use for ctdbd internode communications\&. The default is "tcp"\&. +This option specifies which transport to use for ctdbd internode communications\. The default is "tcp"\. .sp -Currently only "tcp" is supported but "infiniband" might be implemented in the future\&. +Currently only "tcp" is supported but "infiniband" might be implemented in the future\. .RE .PP \-\-usage .RS 4 -Print useage information to the screen\&. +Print useage information to the screen\. .RE -.SH "Private vs Public addresses" +.SH "PRIVATE VS PUBLIC ADDRESSES" .PP -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\&. +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\. .SS "Private address" .PP -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 that ctdbd will use to communicate with the ctdbd daemons on the other nodes in the cluster\&. +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 that ctdbd will use to communicate with the ctdbd daemons on the other nodes in the cluster\. .PP -The private addresses are configured in /etc/ctdb/nodes (unless the \-\-nlist option is used) and contain one line for each node in the cluster\&. Each line contains the private ip address for one node in the cluster\&. This file must be the same on all nodes in the cluster\&. +The private addresses are configured in /etc/ctdb/nodes (unless the \-\-nlist option is used) and contain one line for each node in the cluster\. Each line contains the private ip address for one node in the cluster\. This file must be the same on all nodes in the cluster\. .PP -Since the private addresses are only available to the network when the corresponding node is up and running you should not use these addresses for clients to connect to services provided by the cluster\&. Instead client applications should only attach to the public addresses since these are guaranteed to always be available\&. +Since the private addresses are only available to the network when the corresponding node is up and running you should not use these addresses for clients to connect to services provided by the cluster\. Instead client applications should only attach to the public addresses since these are guaranteed to always be available\. .PP -When using ip takeover, it is strongly recommended that the private addresses are configured on a private network physically separated from the rest of the network and that this private network is dedicated to CTDB traffic\&. +When using ip takeover, it is strongly recommended that the private addresses are configured on a private network physically separated from the rest of the network and that this private network is dedicated to CTDB traffic\. Example /etc/ctdb/nodes for a four node cluster: .sp -.if n \{\ .RS 4 -.\} -.fam C -.ps -1 .nf -.if t \{\ -.sp -1 -.\} -.BB lightgray adjust-for-leading-newline -.sp -1 - - 10\&.1\&.1\&.1 - 10\&.1\&.1\&.2 - 10\&.1\&.1\&.3 - 10\&.1\&.1\&.4 + 10\.1\.1\.1 + 10\.1\.1\.2 + 10\.1\.1\.3 + 10\.1\.1\.4 -.EB lightgray adjust-for-leading-newline -.if t \{\ -.sp 1 -.\} .fi -.fam -.ps +1 -.if n \{\ .RE -.\} .SS "Public address" .PP -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\&. +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\. .PP -The ctdb cluster will assign/reassign these public addresses across the available healthy nodes in the cluster\&. When one node fails, its public address will be migrated to and taken over by a different node in the cluster to ensure that all public addresses are always available to clients as long as there are still nodes available capable of hosting this address\&. +The ctdb cluster will assign/reassign these public addresses across the available healthy nodes in the cluster\. When one node fails, its public address will be migrated to and taken over by a different node in the cluster to ensure that all public addresses are always available to clients as long as there are still nodes available capable of hosting this address\. .PP -These addresses are not physically attached to a specific node\&. The \'ctdb ip\' command can be used to view the current assignment of public addresses and which physical node is currently serving it\&. +These addresses are not physically attached to a specific node\. The \'ctdb ip\' command can be used to view the current assignment of public addresses and which physical node is currently serving it\. .PP -On each node this file contains a list of the public addresses that this node is capable of hosting\&. The list also contain the netmask and the interface where this address should be attached for the case where you may want to serve data out through multiple different interfaces\&. +On each node this file contains a list of the public addresses that this node is capable of hosting\. The list also contain the netmask and the interface where this address should be attached for the case where you may want to serve data out through multiple different interfaces\. Example /etc/ctdb/public_addresses for a node that can host 4 public addresses: .sp -.if n \{\ .RS 4 -.\} -.fam C -.ps -1 .nf -.if t \{\ -.sp -1 -.\} -.BB lightgray adjust-for-leading-newline -.sp -1 - - 11\&.1\&.1\&.1/24 eth0 - 11\&.1\&.1\&.2/24 eth0 - 11\&.1\&.2\&.1/24 eth1 - 11\&.1\&.2\&.2/24 eth1 + 11\.1\.1\.1/24 eth0 + 11\.1\.1\.2/24 eth0 + 11\.1\.2\.1/24 eth1 + 11\.1\.2\.2/24 eth1 -.EB lightgray adjust-for-leading-newline -.if t \{\ -.sp 1 -.\} .fi -.fam -.ps +1 -.if n \{\ .RE -.\} .PP -In most cases this file would be the same on all nodes in a cluster but there are exceptions when one may want to use different files on different nodes\&. +In most cases this file would be the same on all nodes in a cluster but there are exceptions when one may want to use different files on different nodes\. Example: 4 nodes partitioned into two subgroups : .sp -.if n \{\ .RS 4 -.\} -.fam C -.ps -1 .nf -.if t \{\ -.sp -1 -.\} -.BB lightgray adjust-for-leading-newline -.sp -1 - Node 0:/etc/ctdb/public_addresses - 10\&.1\&.1\&.1/24 eth0 - 10\&.1\&.1\&.2/24 eth0 + 10\.1\.1\.1/24 eth0 + 10\.1\.1\.2/24 eth0 Node 1:/etc/ctdb/public_addresses - 10\&.1\&.1\&.1/24 eth0 - 10\&.1\&.1\&.2/24 eth0 + 10\.1\.1\.1/24 eth0 + 10\.1\.1\.2/24 eth0 Node 2:/etc/ctdb/public_addresses - 10\&.2\&.1\&.1/24 eth0 - 10\&.2\&.1\&.2/24 eth0 + 10\.2\.1\.1/24 eth0 + 10\.2\.1\.2/24 eth0 Node 3:/etc/ctdb/public_addresses - 10\&.2\&.1\&.1/24 eth0 - 10\&.2\&.1\&.2/24 eth0 + 10\.2\.1\.1/24 eth0 + 10\.2\.1\.2/24 eth0 -.EB lightgray adjust-for-leading-newline -.if t \{\ -.sp 1 -.\} .fi -.fam -.ps +1 -.if n \{\ .RE -.\} .PP -In this example nodes 0 and 1 host two public addresses on the 10\&.1\&.1\&.x network while nodes 2 and 3 host two public addresses for the 10\&.2\&.1\&.x network\&. +In this example nodes 0 and 1 host two public addresses on the 10\.1\.1\.x network while nodes 2 and 3 host two public addresses for the 10\.2\.1\.x network\. .PP -Ip address 10\&.1\&.1\&.1 can be hosted by either of nodes 0 or 1 and will be available to clients as long as at least one of these two nodes are available\&. If both nodes 0 and node 1 become unavailable 10\&.1\&.1\&.1 also becomes 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\&. -.SH "Node status" +Ip address 10\.1\.1\.1 can be hosted by either of nodes 0 or 1 and will be available to clients as long as at least one of these two nodes are available\. If both nodes 0 and node 1 become unavailable 10\.1\.1\.1 also becomes 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\. +.SH "NODE STATUS" .PP -The current status of each node in the cluster can be viewed by the \'ctdb status\' command\&. +The current status of each node in the cluster can be viewed by the \'ctdb status\' command\. .PP -There are five possible states for a node\&. +There are five possible states for a node\. .PP -OK \- This node is fully functional\&. +OK \- This node is fully functional\. .PP -DISCONNECTED \- This node could not be connected through the network and is currently not particpating 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\&. +DISCONNECTED \- This node could not be connected through the network and is currently not particpating 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\. .PP -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\&. +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\. .PP -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 currently being hosted\&. All unhealthy nodes should be investigated and require an administrative action to rectify\&. +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 currently being hosted\. All unhealthy nodes should be investigated and require an administrative action to rectify\. .PP -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\&. +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\. .SH "PUBLIC TUNABLES" .PP -These are the public tuneables that can be used to control how ctdb behaves\&. +These are the public tuneables that can be used to control how ctdb behaves\. .SS "KeepaliveInterval" .PP Default: 1 .PP -How often should the nodes send keepalives to eachother\&. +How often should the nodes send keepalives to eachother\. .SS "KeepaliveLimit" .PP Default: 5 .PP -After how many keepalive intervals without any traffic should a node wait until marking the peer as DISCONNECTED\&. +After how many keepalive intervals without any traffic should a node wait until marking the peer as DISCONNECTED\. .SS "MonitorInterval" .PP Default: 15 .PP -How often should ctdb run the event scripts to check for a nodes health\&. +How often should ctdb run the event scripts to check for a nodes health\. .SS "TickleUpdateInterval" .PP Default: 20 .PP -How often will ctdb record and store the "tickle" information used to kickstart stalled tcp connections after a recovery\&. +How often will ctdb record and store the "tickle" information used to kickstart stalled tcp connections after a recovery\. .SS "EventScriptTimeout" .PP Default: 20 .PP -How long should ctdb let an event script run before aborting it and marking the node unhealthy\&. +How long should ctdb let an event script run before aborting it and marking the node unhealthy\. .SS "RecoveryBanPeriod" .PP Default: 300 .PP -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\&. +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\. .SS "DatabaseHashSize" .PP Default: 100000 .PP -Size of the hash chains for the local store of the tdbs that ctdb manages\&. +Size of the hash chains for the local store of the tdbs that ctdb manages\. .SS "RerecoveryTimeout" .PP Default: 10 .PP -Once a recovery has completed, no additional recoveries are permitted until this timeout has expired\&. +Once a recovery has completed, no additional recoveries are permitted until this timeout has expired\. .SS "EnableBans" .PP Default: 1 .PP -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\&. +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\. .SS "DeterministicIPs" .PP Default: 1 .PP -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\&. +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\. .PP -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\&. +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\. .SS "DisableWhenUnhealthy" .PP Default: 0 .PP -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\'\&. +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\'\. .PP -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\&. +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\. .SS "NoIPFailback" .PP Default: 0 .PP -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\&. +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\. .PP -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\&. +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\. .PP -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\&. +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\. .SH "LVS" .PP -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\&. +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\. .PP -This is similar to using a layer\-4 loadbalancing switch but with some restrictions\&. +This is similar to using a layer\-4 loadbalancing switch but with some restrictions\. .PP -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, DISABLED or DISCONNECTED\&. The "ctdb lvs" command is used to show which nodes are currently load\-balanced across\&. +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, DISABLED or DISCONNECTED\. The "ctdb lvs" command is used to show which nodes are currently load\-balanced across\. .PP -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\&. +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\. .PP The path used for a client i/o is thus : .sp -.if n \{\ .RS 4 -.\} -.fam C -.ps -1 .nf -.if t \{\ -.sp -1 -.\} -.BB lightgray adjust-for-leading-newline -.sp -1 - (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\&. + (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\. -.EB lightgray adjust-for-leading-newline -.if t \{\ -.sp 1 -.\} .fi -.fam -.ps +1 -.if n \{\ .RE -.\} .PP -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\&. +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\. .PP -Note: you can use LVS and public addresses at the same time\&. +Note: you can use LVS and public addresses at the same time\. .SS "Configuration" .PP -To activate LVS on a CTDB node you must specify CTDB_PUBLIC_INTERFACE and CTDB_LVS_PUBLIC_ADDRESS in /etc/sysconfig/ctdb\&. +To activate LVS on a CTDB node you must specify CTDB_PUBLIC_INTERFACE and CTDB_LVS_PUBLIC_ADDRESS in /etc/sysconfig/ctdb\. .PP -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\&. +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\. .PP Example: .sp -.if n \{\ .RS 4 -.\} -.fam C -.ps -1 .nf -.if t \{\ -.sp -1 -.\} -.BB lightgray adjust-for-leading-newline -.sp -1 - CTDB_PUBLIC_INTERFACE=eth0 - CTDB_LVS_PUBLIC_IP=10\&.0\&.0\&.237 + CTDB_LVS_PUBLIC_IP=10\.0\.0\.237 -.EB lightgray adjust-for-leading-newline -.if t \{\ -.sp 1 -.\} .fi -.fam -.ps +1 -.if n \{\ .RE -.\} .PP -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) +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) .PP -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\&. +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\. .SH "REMOTE CLUSTER NODES" .PP -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\&. +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\. .PP -See the cluster as one single multihomed samba server where one of the NICs (the remote node) is very far away\&. +See the cluster as one single multihomed samba server where one of the NICs (the remote node) is very far away\. .PP -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\&. +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\. .PP 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: .sp -.if n \{\ .RS 4 -.\} -.fam C -.ps -1 .nf -.if t \{\ -.sp -1 -.\} -.BB lightgray adjust-for-leading-newline -.sp -1 - CTDB_CAPABILITY_LMASTER=no CTDB_CAPABILITY_RECMASTER=no -.EB lightgray adjust-for-leading-newline -.if t \{\ -.sp 1 -.\} .fi -.fam -.ps +1 -.if n \{\ .RE -.\} .PP -Verify with the command "ctdb getcapabilities" that that node no longer has the recmaster or the lmaster capabilities\&. +Verify with the command "ctdb getcapabilities" that that node no longer has the recmaster or the lmaster capabilities\. +.SH "NAT-GW" +.PP +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\. +.PP +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\. +.PP +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\. +.PP +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\. +.SS "NAT\-GW" +.PP +A second way is to use the built in NAT\-GW feature in CTDB\. With NAT\-GW only one extra address is required for the entire cluster instead of one address per node\. +.PP +In NAT\-GW one of the nodes in the cluster is designated the NAT Gateway through which all traffic that is originated in the cluster will be routed through if the public addresses are not available\. +.SS "Configuration" +.PP +NAT\-GW is configured in /etc/sysconfig/ctdb by setting the following variables: +.sp +.RS 4 +.nf +# 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 policy routing so that all traffic with +# a source address of the private network and a destination outside of +# the private network are instead routed through the NAT\-GW node\. +# +# The effect of this is that only when a node does not have a public address +# or a route to the external network will the node use the private address +# as the source address and only then will it use the policy routing +# through the NAT\-GW\. +# As long as a node has a public address and can route to the external network +# the node will always pick the public address as the source address and NAT\-GW +# routing will not be used\. +#NATGW_PUBLIC_IP=10\.0\.0\.227/24 +#NATGW_PUBLIC_IFACE=eth0 +#NATGW_DEFAULT_GATEWAY=10\.0\.0\.1 +#NATGW_PRIVATE_IFACE=eth1 +#NATGW_PRIVATE_NETWORK=10\.1\.1\.0/24 + +.fi +.RE +.SS "NATGW_PUBLIC_IP" +.PP +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\. +.PP +Format of this parameter is IPADDRESS/NETMASK +.SS "NATGW_PUBLIC_IFACE" +.PP +This is the physical interface where the NATGW_PUBLIC_IP will be assigned to\. This should be an interface connected to the public network\. +.PP +Format of this parameter is INTERFACE +.SS "NATGW_DEFAULT_GATEWAY" +.PP +This is the default gateway to use on the node that is elected to host the NATGW_PUBLIC_IP\. This is the default gateway on the public network\. +.PP +Format of this parameter is IPADDRESS +.SS "NATGW_PRIVATE_IFACE" +.PP +This is the interface used for the interal private network\. +.PP +Format of this parameter is INTERFACE +.SS "NATGW_PRIVATE_NETWORK" +.PP +This is the network/netmask used for the interal private network\. +.PP +Format of this parameter is IPADDRESS/NETMASK +.SS "Operation" +.PP +When the NAT\-GW fiunctionality is used, one of the nodes is elected to act as a NAT router for all the other nodes in the cluster when they need to originate traffic to the external public network\. +.PP +The NAT\-GW node is assigned the 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)\. +.PP +All other nodes are configured with policy routing so that all outgoing packets that have a source ip address belonging to the private network (which means they are not routable from the public network) are instead sent on to the designated NAT\-GW host instead of using the normal routing table\. +.PP +This is implemented in the 11\.natgw eventscript\. Please see the eventscript for further information\. .SH "SEE ALSO" .PP ctdb(1), onnode(1) -\m[blue]\fB\%http://ctdb.samba.org/\fR\m[] +\fI\%http://ctdb.samba.org/\fR .SH "COPYRIGHT/LICENSE" .sp -.if n \{\ .RS 4 -.\} -.fam C -.ps -1 .nf -.if t \{\ -.sp -1 -.\} -.BB lightgray adjust-for-leading-newline -.sp -1 - Copyright (C) Andrew Tridgell 2007 Copyright (C) Ronnie sahlberg 2007 This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 3 of the License, or (at -your option) any later version\&. +your option) any later version\. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of -MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE\&. See the GNU -General Public License for more details\&. +MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE\. See the GNU +General Public License for more details\. You should have received a copy of the GNU General Public License -along with this program; if not, see http://www\&.gnu\&.org/licenses/\&. -.EB lightgray adjust-for-leading-newline -.if t \{\ -.sp 1 -.\} +along with this program; if not, see http://www\.gnu\.org/licenses/\. .fi -.fam -.ps +1 -.if n \{\ .RE -.\} diff --git a/ctdb/doc/ctdbd.1.html b/ctdb/doc/ctdbd.1.html index 874308e0f7..c1eb248da3 100644 --- a/ctdb/doc/ctdbd.1.html +++ b/ctdb/doc/ctdbd.1.html @@ -415,10 +415,123 @@ CTDB_CAPABILITY_RECMASTER=no

Verify with the command "ctdb getcapabilities" that that node no longer has the recmaster or the lmaster capabilities. -

SEE ALSO

+

NAT-GW

+ 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. +

+ 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. +

+ 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. +

+ 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. +

NAT-GW

+ A second way is to use the built in NAT-GW feature in CTDB. + With NAT-GW only one extra address is required for the entire cluster + instead of one address per node. +

+ In NAT-GW one of the nodes in the cluster is designated the NAT Gateway + through which all traffic that is originated in the cluster will be + routed through if the public addresses are not available. +

Configuration

+ NAT-GW is configured in /etc/sysconfig/ctdb by setting the following + variables: + 

+# 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 policy routing so that all traffic with
+# a source address of the private network and a destination outside of
+# the private network are instead routed through the NAT-GW node.
+# 
+# The effect of this is that only when a node does not have a public address
+# or a route to the external network will the node use the private address
+# as the source address and only then will it use the policy routing
+# through the NAT-GW.
+# As long as a node has a public address and can route to the external network
+# the node will always pick the public address as the source address and NAT-GW
+# routing will not be used.
+#NATGW_PUBLIC_IP=10.0.0.227/24
+#NATGW_PUBLIC_IFACE=eth0
+#NATGW_DEFAULT_GATEWAY=10.0.0.1
+#NATGW_PRIVATE_IFACE=eth1
+#NATGW_PRIVATE_NETWORK=10.1.1.0/24
+

NATGW_PUBLIC_IP

+ 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 +

NATGW_PUBLIC_IFACE

+ This is the physical interface where the NATGW_PUBLIC_IP will be + assigned to. This should be an interface connected to the public network. +

+ Format of this parameter is INTERFACE +

NATGW_DEFAULT_GATEWAY

+ This is the default gateway to use on the node that is elected to host + the NATGW_PUBLIC_IP. This is the default gateway on the public network. +

+ Format of this parameter is IPADDRESS +

NATGW_PRIVATE_IFACE

+ This is the interface used for the interal private network. +

+ Format of this parameter is INTERFACE +

NATGW_PRIVATE_NETWORK

+ This is the network/netmask used for the interal private network. +

+ Format of this parameter is IPADDRESS/NETMASK +

Operation

+ When the NAT-GW fiunctionality is used, one of the nodes is elected + to act as a NAT router for all the other nodes in the cluster when + they need to originate traffic to the external public network. +

+ The NAT-GW node is assigned the 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). +

+ All other nodes are configured with policy routing so that all outgoing + packets that have a source ip address belonging to the private network + (which means they are not routable from the public network) are instead + sent on to the designated NAT-GW host instead of using the normal + routing table. +

+ This is implemented in the 11.natgw eventscript. Please see the + eventscript for further information. +

SEE ALSO

ctdb(1), onnode(1) http://ctdb.samba.org/ -

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 d69d3dcbc8..48dc0e2b9c 100644 --- a/ctdb/doc/ctdbd.1.xml +++ b/ctdb/doc/ctdbd.1.xml @@ -780,6 +780,170 @@ CTDB_CAPABILITY_RECMASTER=no + NAT-GW + + 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. + + + 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. + + + 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. + + + 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. + + NAT-GW + + A second way is to use the built in NAT-GW feature in CTDB. + With NAT-GW only one extra address is required for the entire cluster + instead of one address per node. + + + In NAT-GW one of the nodes in the cluster is designated the NAT Gateway + through which all traffic that is originated in the cluster will be + routed through if the public addresses are not available. + + + + Configuration + + NAT-GW is configured in /etc/sysconfig/ctdb by setting the following + variables: + + +# 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 policy routing so that all traffic with +# a source address of the private network and a destination outside of +# the private network are instead routed through the NAT-GW node. +# +# The effect of this is that only when a node does not have a public address +# or a route to the external network will the node use the private address +# as the source address and only then will it use the policy routing +# through the NAT-GW. +# As long as a node has a public address and can route to the external network +# the node will always pick the public address as the source address and NAT-GW +# routing will not be used. +#NATGW_PUBLIC_IP=10.0.0.227/24 +#NATGW_PUBLIC_IFACE=eth0 +#NATGW_DEFAULT_GATEWAY=10.0.0.1 +#NATGW_PRIVATE_IFACE=eth1 +#NATGW_PRIVATE_NETWORK=10.1.1.0/24 + + + + NATGW_PUBLIC_IP + + 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 + + + + NATGW_PUBLIC_IFACE + + This is the physical interface where the NATGW_PUBLIC_IP will be + assigned to. This should be an interface connected to the public network. + + + Format of this parameter is INTERFACE + + + + NATGW_DEFAULT_GATEWAY + + This is the default gateway to use on the node that is elected to host + the NATGW_PUBLIC_IP. This is the default gateway on the public network. + + + Format of this parameter is IPADDRESS + + + + NATGW_PRIVATE_IFACE + + This is the interface used for the interal private network. + + + Format of this parameter is INTERFACE + + + + NATGW_PRIVATE_NETWORK + + This is the network/netmask used for the interal private network. + + + Format of this parameter is IPADDRESS/NETMASK + + + + Operation + + When the NAT-GW fiunctionality is used, one of the nodes is elected + to act as a NAT router for all the other nodes in the cluster when + they need to originate traffic to the external public network. + + + The NAT-GW node is assigned the 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). + + + All other nodes are configured with policy routing so that all outgoing + packets that have a source ip address belonging to the private network + (which means they are not routable from the public network) are instead + sent on to the designated NAT-GW host instead of using the normal + routing table. + + + This is implemented in the 11.natgw eventscript. Please see the + eventscript for further information. + + + + + + + SEE ALSO -- cgit From 9bf792d70449717b7241c41d3d18d6da008b3490 Mon Sep 17 00:00:00 2001 From: root Date: Wed, 18 Mar 2009 19:19:49 +1100 Subject: redo how the natgw is done. just use a default route with a high metric instead of fancy policyrouting (This used to be ctdb commit f03bd2b3d906dac9fb876dca54535d22e9cf1b9e) --- ctdb/config/ctdb.sysconfig | 25 +++++++--------- ctdb/config/events.d/11.natgw | 66 +++++++++++++++++-------------------------- 2 files changed, 36 insertions(+), 55 deletions(-) diff --git a/ctdb/config/ctdb.sysconfig b/ctdb/config/ctdb.sysconfig index 03b91b6088..abb9ea775b 100644 --- a/ctdb/config/ctdb.sysconfig +++ b/ctdb/config/ctdb.sysconfig @@ -147,23 +147,18 @@ # 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 policy routing so that all traffic with -# a source address of the private network and a destination outside of -# the private network are instead routed through 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 -# or a route to the external network will the node use the private address -# as the source address and only then will it use the policy routing -# through the NAT-GW. -# As long as a node has a public address and can route to the external network -# the node will always pick the public address as the source address and NAT-GW -# routing will not be used. -#NATGW_PUBLIC_IP=10.0.0.227/24 -#NATGW_PUBLIC_IFACE=eth0 -#NATGW_DEFAULT_GATEWAY=10.0.0.1 -#NATGW_PRIVATE_IFACE=eth1 -#NATGW_PRIVATE_NETWORK=10.1.1.0/24 - +# and thus no proper routes to the external world it will instead +# route all packets through the nat-gw node. +# +# NATGW_PUBLIC_IP=10.0.0.227/24 +# NATGW_PUBLIC_IFACE=eth0 +# NATGW_DEFAULT_GATEWAY=10.0.0.1 +# NATGW_PRIVATE_IFACE=eth1 +# NATGW_PRIVATE_NETWORK=10.1.1.0/24 # where to log messages # the default is /var/log/log.ctdb diff --git a/ctdb/config/events.d/11.natgw b/ctdb/config/events.d/11.natgw index 23fe4ae32c..3f2c2c2958 100644 --- a/ctdb/config/events.d/11.natgw +++ b/ctdb/config/events.d/11.natgw @@ -8,12 +8,24 @@ . $CTDB_BASE/functions loadconfig ctdb -[ -z "$NATGW_PUBLIC_INTERFACE" ] && exit 0 +[ -z "$NATGW_PUBLIC_IFACE" ] && exit 0 cmd="$1" shift PATH=/usr/bin:/bin:/usr/sbin:/sbin:$PATH +delete_all() { + ip addr add $NATGW_PUBLIC_IP dev $NATGW_PUBLIC_IFACE >/dev/null 2>/dev/null + ip addr del $NATGW_PUBLIC_IP_HOST dev $NATGW_PRIVATE_IFACE >/dev/null 2>/dev/null + ip route del 0.0.0.0/0 metric 10 >/dev/null 2>/dev/null + + # Delete the masquerading setup from a previous iteration where we + # were the NAT-GW + iptables -D POSTROUTING -t nat -s $NATGW_PRIVATE_NETWORK -d ! $NATGW_PRIVATE_NETWORK -j MASQUERADE >/dev/null 2>/dev/null + + ip addr del $NATGW_PUBLIC_IP dev $NATGW_PUBLIC_IFACE >/dev/null 2>/dev/null +} + case $cmd in recovered) MYPNN=`ctdb pnn | cut -d: -f2` @@ -22,19 +34,9 @@ case $cmd in FIRST=`ctdb status -Y | grep ":0:$" | head -1` FIRSTNODE=`echo $FIRST | cut -d: -f2` FIRSTIP=`echo $FIRST | cut -d: -f3` + NATGW_PUBLIC_IP_HOST=`echo $NATGW_PUBLIC_IP | sed -e "s/\/.*/\/32/"` - # Delete everything that might have been set in a previous iteration - # when we were not the NAT-GW - ip rule del fwmark 11 table 11 >/dev/null 2>/dev/null - iptables -D OUTPUT -t mangle -s $NATGW_PRIVATE_NETWORK -d ! $NATGW_PRIVATE_NETWORK -j MARK --set-mark 11 >/dev/null 2>/dev/null - iptables -D OUTPUT -t mangle -s $NATGW_PRIVATE_NETWORK -d ! $NATGW_PRIVATE_NETWORK -p tcp --sport 22 -j ACCEPT >/dev/null 2>/dev/null - ip route del $NATGW_PRIVATE_NETWORK dev $NATGW_PRIVATE_IFACE table 11 >/dev/null 2>/dev/null - ip route del 0.0.0.0/0 dev $NATGW_PRIVATE_IFACE table 11 >/dev/null 2>/dev/null - - # Delete the masquerading setup from a previous iteration where we - # was the NAT-GW - iptables -D POSTROUTING -t nat -s $NATGW_PRIVATE_NETWORK -d ! $NATGW_PRIVATE_NETWORK -j MASQUERADE >/dev/null 2>/dev/null - ip addr del $NATGW_PUBLIC_IP dev $NATGW_PUBLIC_IFACE >/dev/null 2>/dev/null + delete_all if [ "$FIRSTNODE" == "$MYPNN" ]; then # This is the first node, set it up as the NAT GW @@ -44,36 +46,20 @@ case $cmd in ip route add 0.0.0.0/0 via $NATGW_DEFAULT_GATEWAY >/dev/null 2>/dev/null else # This is not the NAT-GW - # We now need to set up a separate routing table for - # all traffic we originate and with a destination that is - # outside of the local private network and route these - # packets via the NAT-GW - - - # Mark all outgoing packets that have the private address - # as source address with fwmarker 11 - # We expect that the only time the the source address will be - # selected as the private address would be when there are - # no static or public addresses assigned at all to the node. - # Othervise the routing would have picked a different address. - # - # Except for traffic to the ssh daemon, so that it is easier - # to test in the lab without disrupting the ssh sessions - iptables -A OUTPUT -t mangle -s $NATGW_PRIVATE_NETWORK -d ! $NATGW_PRIVATE_NETWORK -p tcp --sport 22 -j ACCEPT - iptables -A OUTPUT -t mangle -s $NATGW_PRIVATE_NETWORK -d ! $NATGW_PRIVATE_NETWORK -j MARK --set-mark 11 - - - # create a routing table for the natgw traffic and set it - # up with both an interface toute for the private network - # as well as a default route that goes via the NAT-GW - ip route add $NATGW_PRIVATE_NETWORK dev $NATGW_PRIVATE_IFACE table 11 - ip route add 0.0.0.0/0 via $FIRSTIP dev $NATGW_PRIVATE_IFACE table 11 >/dev/null 2>/dev/null - - # Create a rule to use routing table 11 for these packets - ip rule add fwmark 11 table 11 + # Assign the public ip to the private interface and make + # sure we dont respond to ARPs. + # We do this so that the ip address will exist on a + # non-loopback interface so that samba may send it along in the + # KDC requests. + ip addr add $NATGW_PUBLIC_IP_HOST dev $NATGW_PRIVATE_IFACE + ip route add 0.0.0.0/0 via $FIRSTIP metric 10 fi ;; + shutdown) + delete_all + ;; + esac exit 0 -- cgit From 293a3f115829f79a9c7a88a062698cdd0cadcc09 Mon Sep 17 00:00:00 2001 From: Ronnie Sahlberg Date: Thu, 19 Mar 2009 10:17:44 +1100 Subject: update the natgw eventscript and documentation (This used to be ctdb commit 95d8ddbc2dd0b159e8df003502c3c336668d2c41) --- ctdb/config/events.d/11.natgw | 7 +++++- ctdb/doc/ctdbd.1 | 32 +++++++++++-------------- ctdb/doc/ctdbd.1.html | 55 ++++++++++++++++++++----------------------- ctdb/doc/ctdbd.1.xml | 37 +++++++++++++---------------- 4 files changed, 61 insertions(+), 70 deletions(-) diff --git a/ctdb/config/events.d/11.natgw b/ctdb/config/events.d/11.natgw index 3f2c2c2958..254a8c1e87 100644 --- a/ctdb/config/events.d/11.natgw +++ b/ctdb/config/events.d/11.natgw @@ -51,7 +51,12 @@ case $cmd in # We do this so that the ip address will exist on a # non-loopback interface so that samba may send it along in the # KDC requests. - ip addr add $NATGW_PUBLIC_IP_HOST dev $NATGW_PRIVATE_IFACE + + # Set the scope up as host and make sure we dont respond to ARP + # for this ip + echo 3 > /proc/sys/net/ipv4/conf/all/arp_ignore + ip addr add $NATGW_PUBLIC_IP_HOST dev $NATGW_PRIVATE_IFACE scope host + ip route add 0.0.0.0/0 via $FIRSTIP metric 10 fi ;; diff --git a/ctdb/doc/ctdbd.1 b/ctdb/doc/ctdbd.1 index c332beb9af..e37912878c 100644 --- a/ctdb/doc/ctdbd.1 +++ b/ctdb/doc/ctdbd.1 @@ -1,11 +1,11 @@ .\" Title: ctdbd .\" Author: .\" Generator: DocBook XSL Stylesheets v1.73.2 -.\" Date: 03/18/2009 +.\" Date: 03/19/2009 .\" Manual: .\" Source: .\" -.TH "CTDBD" "1" "03/18/2009" "" "" +.TH "CTDBD" "1" "03/19/2009" "" "" .\" disable hyphenation .nh .\" disable justification (adjust text to left margin only) @@ -427,7 +427,7 @@ If then the service status of CTDB depends on such services being able to always 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\. .SS "NAT\-GW" .PP -A second way is to use the built in NAT\-GW feature in CTDB\. With NAT\-GW only one extra address is required for the entire cluster instead of one address per node\. +A second way is to use the built in NAT\-GW feature in CTDB\. With NAT\-GW only one extra address is required for the entire cluster instead of one address per node\. This extra address is dedicated to traffic that originates from the cluster and is destined for the external network\. .PP In NAT\-GW one of the nodes in the cluster is designated the NAT Gateway through which all traffic that is originated in the cluster will be routed through if the public addresses are not available\. .SS "Configuration" @@ -455,22 +455,18 @@ NAT\-GW is configured in /etc/sysconfig/ctdb by setting the following variables: # 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 policy routing so that all traffic with -# a source address of the private network and a destination outside of -# the private network are instead routed through 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 -# or a route to the external network will the node use the private address -# as the source address and only then will it use the policy routing -# through the NAT\-GW\. -# As long as a node has a public address and can route to the external network -# the node will always pick the public address as the source address and NAT\-GW -# routing will not be used\. -#NATGW_PUBLIC_IP=10\.0\.0\.227/24 -#NATGW_PUBLIC_IFACE=eth0 -#NATGW_DEFAULT_GATEWAY=10\.0\.0\.1 -#NATGW_PRIVATE_IFACE=eth1 -#NATGW_PRIVATE_NETWORK=10\.1\.1\.0/24 +# and thus no proper routes to the external world it will instead +# route all packets through the nat\-gw node\. +# +# NATGW_PUBLIC_IP=10\.0\.0\.227/24 +# NATGW_PUBLIC_IFACE=eth0 +# NATGW_DEFAULT_GATEWAY=10\.0\.0\.1 +# NATGW_PRIVATE_IFACE=eth1 +# NATGW_PRIVATE_NETWORK=10\.1\.1\.0/24 .fi .RE @@ -505,7 +501,7 @@ When the NAT\-GW fiunctionality is used, one of the nodes is elected to act as a .PP The NAT\-GW node is assigned the 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)\. .PP -All other nodes are configured with policy routing so that all outgoing packets that have a source ip address belonging to the private network (which means they are not routable from the public network) are instead sent on to the designated NAT\-GW host instead of using the normal routing table\. +All other nodes are configured with a default route of metric 10 pointing to the designated NAT GW node\. .PP This is implemented in the 11\.natgw eventscript\. Please see the eventscript for further information\. .SH "SEE ALSO" diff --git a/ctdb/doc/ctdbd.1.html b/ctdb/doc/ctdbd.1.html index c1eb248da3..61d3d93195 100644 --- a/ctdb/doc/ctdbd.1.html +++ b/ctdb/doc/ctdbd.1.html @@ -441,12 +441,14 @@ CTDB_CAPABILITY_RECMASTER=no

NAT-GW

A second way is to use the built in NAT-GW feature in CTDB. With NAT-GW only one extra address is required for the entire cluster - instead of one address per node. + instead of one address per node. This extra address is dedicated + to traffic that originates from the cluster and is destined for the + external network.

In NAT-GW one of the nodes in the cluster is designated the NAT Gateway through which all traffic that is originated in the cluster will be - routed through if the public addresses are not available. -

Configuration

+ routed through if the public addresses are not available. +

Configuration

NAT-GW is configured in /etc/sysconfig/ctdb by setting the following variables: 

@@ -469,48 +471,44 @@ CTDB_CAPABILITY_RECMASTER=no
 # 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 policy routing so that all traffic with
-# a source address of the private network and a destination outside of
-# the private network are instead routed through 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
-# or a route to the external network will the node use the private address
-# as the source address and only then will it use the policy routing
-# through the NAT-GW.
-# As long as a node has a public address and can route to the external network
-# the node will always pick the public address as the source address and NAT-GW
-# routing will not be used.
-#NATGW_PUBLIC_IP=10.0.0.227/24
-#NATGW_PUBLIC_IFACE=eth0
-#NATGW_DEFAULT_GATEWAY=10.0.0.1
-#NATGW_PRIVATE_IFACE=eth1
-#NATGW_PRIVATE_NETWORK=10.1.1.0/24
-

NATGW_PUBLIC_IP

+# and thus no proper routes to the external world it will instead +# route all packets through the nat-gw node. +# +# NATGW_PUBLIC_IP=10.0.0.227/24 +# NATGW_PUBLIC_IFACE=eth0 +# NATGW_DEFAULT_GATEWAY=10.0.0.1 +# NATGW_PRIVATE_IFACE=eth1 +# NATGW_PRIVATE_NETWORK=10.1.1.0/24 +

NATGW_PUBLIC_IP

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 -

NATGW_PUBLIC_IFACE

+

NATGW_PUBLIC_IFACE

This is the physical interface where the NATGW_PUBLIC_IP will be assigned to. This should be an interface connected to the public network.

Format of this parameter is INTERFACE -

NATGW_DEFAULT_GATEWAY

+

NATGW_DEFAULT_GATEWAY

This is the default gateway to use on the node that is elected to host the NATGW_PUBLIC_IP. This is the default gateway on the public network.

Format of this parameter is IPADDRESS -

NATGW_PRIVATE_IFACE

+

NATGW_PRIVATE_IFACE

This is the interface used for the interal private network.

Format of this parameter is INTERFACE -

NATGW_PRIVATE_NETWORK

+

NATGW_PRIVATE_NETWORK

This is the network/netmask used for the interal private network.

Format of this parameter is IPADDRESS/NETMASK -

Operation

+

Operation

When the NAT-GW fiunctionality is used, one of the nodes is elected to act as a NAT router for all the other nodes in the cluster when they need to originate traffic to the external public network. @@ -520,18 +518,15 @@ CTDB_CAPABILITY_RECMASTER=no 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).

- All other nodes are configured with policy routing so that all outgoing - packets that have a source ip address belonging to the private network - (which means they are not routable from the public network) are instead - sent on to the designated NAT-GW host instead of using the normal - routing table. + All other nodes are configured with a default route of metric 10 pointing + to the designated NAT GW node.

This is implemented in the 11.natgw eventscript. Please see the eventscript for further information. -

SEE ALSO

+

SEE ALSO

ctdb(1), onnode(1) http://ctdb.samba.org/ -

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 48dc0e2b9c..d5e3824b21 100644 --- a/ctdb/doc/ctdbd.1.xml +++ b/ctdb/doc/ctdbd.1.xml @@ -812,12 +812,14 @@ CTDB_CAPABILITY_RECMASTER=no A second way is to use the built in NAT-GW feature in CTDB. With NAT-GW only one extra address is required for the entire cluster - instead of one address per node. + instead of one address per node. This extra address is dedicated + to traffic that originates from the cluster and is destined for the + external network. In NAT-GW one of the nodes in the cluster is designated the NAT Gateway through which all traffic that is originated in the cluster will be - routed through if the public addresses are not available. + routed through if the public addresses are not available. @@ -846,22 +848,18 @@ CTDB_CAPABILITY_RECMASTER=no # 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 policy routing so that all traffic with -# a source address of the private network and a destination outside of -# the private network are instead routed through 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 -# or a route to the external network will the node use the private address -# as the source address and only then will it use the policy routing -# through the NAT-GW. -# As long as a node has a public address and can route to the external network -# the node will always pick the public address as the source address and NAT-GW -# routing will not be used. -#NATGW_PUBLIC_IP=10.0.0.227/24 -#NATGW_PUBLIC_IFACE=eth0 -#NATGW_DEFAULT_GATEWAY=10.0.0.1 -#NATGW_PRIVATE_IFACE=eth1 -#NATGW_PRIVATE_NETWORK=10.1.1.0/24 +# and thus no proper routes to the external world it will instead +# route all packets through the nat-gw node. +# +# NATGW_PUBLIC_IP=10.0.0.227/24 +# NATGW_PUBLIC_IFACE=eth0 +# NATGW_DEFAULT_GATEWAY=10.0.0.1 +# NATGW_PRIVATE_IFACE=eth1 +# NATGW_PRIVATE_NETWORK=10.1.1.0/24 @@ -928,11 +926,8 @@ CTDB_CAPABILITY_RECMASTER=no internal private network and which is destined to the external network(s). - All other nodes are configured with policy routing so that all outgoing - packets that have a source ip address belonging to the private network - (which means they are not routable from the public network) are instead - sent on to the designated NAT-GW host instead of using the normal - routing table. + All other nodes are configured with a default route of metric 10 pointing + to the designated NAT GW node. This is implemented in the 11.natgw eventscript. Please see the -- cgit From 4d2195c503c3e47107138bcd02b0222d89312a85 Mon Sep 17 00:00:00 2001 From: Ronnie Sahlberg Date: Thu, 19 Mar 2009 10:43:57 +1100 Subject: The wbinfo --sequence command has been depreciated in favor of the new --online-status command (This used to be ctdb commit b6e34503ac094a274a569a69e3d93d92ad911f4d) --- ctdb/tools/ctdb_diagnostics | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ctdb/tools/ctdb_diagnostics b/ctdb/tools/ctdb_diagnostics index 8cf1f9ab6e..a9531d646c 100755 --- a/ctdb/tools/ctdb_diagnostics +++ b/ctdb/tools/ctdb_diagnostics @@ -236,7 +236,7 @@ show_all "smbclient -U% -L 127.0.0.1" WORKGROUP=`testparm -s --parameter-name=WORKGROUP 2> /dev/null` show_all id "$WORKGROUP/Administrator" show_all "wbinfo -p" -show_all "wbinfo --sequence" +show_all "wbinfo --online-status" show_all "smbd -b" date -- cgit From dc05c1b80cad4597c8a900d5cce41c5e7731937e Mon Sep 17 00:00:00 2001 From: root Date: Mon, 23 Mar 2009 12:37:30 +1100 Subject: create a helper function that converts a ctdb instance in daemon mode to become a ctdb client instance. use this from the recovery daemon child process to switch to client mode and connect back to the main daemon (This used to be ctdb commit 16f31786a031255ab5b3099a0a3c745de973347a) --- ctdb/client/ctdb_client.c | 36 ++++++++++++++++++++++++++++++++++++ ctdb/include/ctdb.h | 2 ++ ctdb/server/ctdb_recoverd.c | 30 +++++------------------------- 3 files changed, 43 insertions(+), 25 deletions(-) diff --git a/ctdb/client/ctdb_client.c b/ctdb/client/ctdb_client.c index 16fc03b48a..1f68c242a1 100644 --- a/ctdb/client/ctdb_client.c +++ b/ctdb/client/ctdb_client.c @@ -3472,3 +3472,39 @@ int ctdb_ctrl_recd_ping(struct ctdb_context *ctdb) return 0; } + +/* when forking the main daemon and the child process needs to connect back + * to the daemon as a client process, this function can be used to change + * the ctdb context from daemon into client mode + */ +int switch_from_server_to_client(struct ctdb_context *ctdb) +{ + int ret; + + /* shutdown the transport */ + if (ctdb->methods) { + ctdb->methods->shutdown(ctdb); + } + + /* get a new event context */ + talloc_free(ctdb->ev); + ctdb->ev = event_context_init(ctdb); + + close(ctdb->daemon.sd); + ctdb->daemon.sd = -1; + + /* the client does not need to be realtime */ + if (ctdb->do_setsched) { + ctdb_restore_scheduler(ctdb); + } + + /* initialise ctdb */ + ret = ctdb_socket_connect(ctdb); + if (ret != 0) { + DEBUG(DEBUG_ALERT, (__location__ " Failed to init ctdb client\n")); + return -1; + } + + return 0; +} + diff --git a/ctdb/include/ctdb.h b/ctdb/include/ctdb.h index 2ec477f608..f0f510abd3 100644 --- a/ctdb/include/ctdb.h +++ b/ctdb/include/ctdb.h @@ -610,4 +610,6 @@ int ctdb_transaction_commit(struct ctdb_transaction_handle *h); int ctdb_ctrl_recd_ping(struct ctdb_context *ctdb); +int switch_from_server_to_client(struct ctdb_context *ctdb); + #endif diff --git a/ctdb/server/ctdb_recoverd.c b/ctdb/server/ctdb_recoverd.c index 540749d12f..28be460c98 100644 --- a/ctdb/server/ctdb_recoverd.c +++ b/ctdb/server/ctdb_recoverd.c @@ -2906,7 +2906,6 @@ static void recd_sig_child_handler(struct event_context *ev, */ int ctdb_start_recoverd(struct ctdb_context *ctdb) { - int ret; int fd[2]; struct signal_event *se; @@ -2931,35 +2930,16 @@ int ctdb_start_recoverd(struct ctdb_context *ctdb) close(fd[1]); - /* shutdown the transport */ - if (ctdb->methods) { - ctdb->methods->shutdown(ctdb); - } - - /* get a new event context */ - talloc_free(ctdb->ev); - ctdb->ev = event_context_init(ctdb); - - event_add_fd(ctdb->ev, ctdb, fd[0], EVENT_FD_READ|EVENT_FD_AUTOCLOSE, - ctdb_recoverd_parent, &fd[0]); - - close(ctdb->daemon.sd); - ctdb->daemon.sd = -1; - srandom(getpid() ^ time(NULL)); - /* the recovery daemon does not need to be realtime */ - if (ctdb->do_setsched) { - ctdb_restore_scheduler(ctdb); - } - - /* initialise ctdb */ - ret = ctdb_socket_connect(ctdb); - if (ret != 0) { - DEBUG(DEBUG_ALERT, (__location__ " Failed to init ctdb\n")); + if (switch_from_server_to_client(ctdb) != 0) { + DEBUG(DEBUG_CRIT, (__location__ "ERROR: failed to switch recovery daemon into client mode. shutting down.\n")); exit(1); } + event_add_fd(ctdb->ev, ctdb, fd[0], EVENT_FD_READ|EVENT_FD_AUTOCLOSE, + ctdb_recoverd_parent, &fd[0]); + /* set up a handler to pick up sigchld */ se = event_add_signal(ctdb->ev, ctdb, SIGCHLD, 0, -- cgit From 629d5ee1fa9b84150c25c151b3bf0690cb787a90 Mon Sep 17 00:00:00 2001 From: root Date: Mon, 23 Mar 2009 19:07:45 +1100 Subject: add a new command "ctdb scriptstatus" this command shows which eventscripts were executed during the last monitoring cycle and the status from each eventscript. If an eventscript timedout or returned an error we also show the output from the eventscript. Example : [root@rcn1 ctdb-git]# ./bin/ctdb scriptstatus 6 scripts were executed last monitoring cycle 00.ctdb Status:OK Duration:0.021 Mon Mar 23 19:04:32 2009 10.interface Status:OK Duration:0.048 Mon Mar 23 19:04:32 2009 20.multipathd Status:OK Duration:0.011 Mon Mar 23 19:04:33 2009 40.vsftpd Status:OK Duration:0.011 Mon Mar 23 19:04:33 2009 41.httpd Status:OK Duration:0.011 Mon Mar 23 19:04:33 2009 50.samba Status:ERROR Duration:0.057 Mon Mar 23 19:04:33 2009 OUTPUT:ERROR: Samba tcp port 445 is not responding Add a new helper function "switch_from_server_to_client()" which both the recovery daemon can use as well as in the child process we start for running the actual eventscripts. Create several new controls, both for the eventscript child process to inform the master daemon of the current status of the scripts as well as for the ctdb tool to extract this information from the runninc daemon. (This used to be ctdb commit c98f90ad61c9b1e679116fbed948ddca4111968d) --- ctdb/client/ctdb_client.c | 107 ++++++++++++++++ ctdb/include/ctdb.h | 24 ++++ ctdb/include/ctdb_private.h | 22 ++++ ctdb/server/ctdb_control.c | 19 +++ ctdb/server/ctdb_logging.c | 4 + ctdb/server/eventscript.c | 305 +++++++++++++++++++++++++++++++++++++++++++- ctdb/tools/ctdb.c | 39 ++++++ 7 files changed, 517 insertions(+), 3 deletions(-) diff --git a/ctdb/client/ctdb_client.c b/ctdb/client/ctdb_client.c index 1f68c242a1..3bdb4b2617 100644 --- a/ctdb/client/ctdb_client.c +++ b/ctdb/client/ctdb_client.c @@ -3508,3 +3508,110 @@ int switch_from_server_to_client(struct ctdb_context *ctdb) return 0; } +/* + tell the main daemon we are starting a new monitor event script + */ +int ctdb_ctrl_event_script_init(struct ctdb_context *ctdb) +{ + int ret; + int32_t res; + + ret = ctdb_control(ctdb, CTDB_CURRENT_NODE, 0, CTDB_CONTROL_EVENT_SCRIPT_INIT, 0, tdb_null, + ctdb, NULL, &res, NULL, NULL); + if (ret != 0 || res != 0) { + DEBUG(DEBUG_ERR,("Failed to send event_script_init\n")); + return -1; + } + + return 0; +} + +/* + tell the main daemon we are starting a new monitor event script + */ +int ctdb_ctrl_event_script_finished(struct ctdb_context *ctdb) +{ + int ret; + int32_t res; + + ret = ctdb_control(ctdb, CTDB_CURRENT_NODE, 0, CTDB_CONTROL_EVENT_SCRIPT_FINISHED, 0, tdb_null, + ctdb, NULL, &res, NULL, NULL); + if (ret != 0 || res != 0) { + DEBUG(DEBUG_ERR,("Failed to send event_script_init\n")); + return -1; + } + + return 0; +} + +/* + tell the main daemon we are starting to run an eventscript + */ +int ctdb_ctrl_event_script_start(struct ctdb_context *ctdb, const char *name) +{ + int ret; + int32_t res; + TDB_DATA data; + + data.dptr = discard_const(name); + data.dsize = strlen(name)+1; + + ret = ctdb_control(ctdb, CTDB_CURRENT_NODE, 0, CTDB_CONTROL_EVENT_SCRIPT_START, 0, data, + ctdb, NULL, &res, NULL, NULL); + if (ret != 0 || res != 0) { + DEBUG(DEBUG_ERR,("Failed to send event_script_start\n")); + return -1; + } + + return 0; +} + +/* + tell the main daemon the status of the script we ran + */ +int ctdb_ctrl_event_script_stop(struct ctdb_context *ctdb, int32_t result) +{ + int ret; + int32_t res; + TDB_DATA data; + + data.dptr = (uint8_t *)&result; + data.dsize = sizeof(result); + + ret = ctdb_control(ctdb, CTDB_CURRENT_NODE, 0, CTDB_CONTROL_EVENT_SCRIPT_STOP, 0, data, + ctdb, NULL, &res, NULL, NULL); + if (ret != 0 || res != 0) { + DEBUG(DEBUG_ERR,("Failed to send event_script_stop\n")); + return -1; + } + + return 0; +} + + +/* + get the status of running the monitor eventscripts + */ +int ctdb_ctrl_getscriptstatus(struct ctdb_context *ctdb, + struct timeval timeout, uint32_t destnode, + TALLOC_CTX *mem_ctx, + struct ctdb_monitoring_wire **script_status) +{ + int ret; + TDB_DATA outdata; + int32_t res; + + ret = ctdb_control(ctdb, destnode, 0, + CTDB_CONTROL_GET_EVENT_SCRIPT_STATUS, 0, tdb_null, + mem_ctx, &outdata, &res, &timeout, NULL); + if (ret != 0 || res != 0 || outdata.dsize == 0) { + DEBUG(DEBUG_ERR,(__location__ " ctdb_control for getscriptstatus failed ret:%d res:%d\n", ret, res)); + return -1; + } + + *script_status = (struct ctdb_monitoring_wire *)talloc_memdup(mem_ctx, outdata.dptr, outdata.dsize); + talloc_free(outdata.dptr); + + return 0; +} + diff --git a/ctdb/include/ctdb.h b/ctdb/include/ctdb.h index f0f510abd3..866ba76e2a 100644 --- a/ctdb/include/ctdb.h +++ b/ctdb/include/ctdb.h @@ -612,4 +612,28 @@ int ctdb_ctrl_recd_ping(struct ctdb_context *ctdb); int switch_from_server_to_client(struct ctdb_context *ctdb); +#define MONITOR_SCRIPT_OK 0 +#define MONITOR_SCRIPT_TIMEOUT 1 + +#define MAX_SCRIPT_NAME 31 +#define MAX_SCRIPT_OUTPUT 511 +struct ctdb_monitoring_script_wire { + char name[MAX_SCRIPT_NAME+1]; + struct timeval start; + struct timeval finished; + int32_t status; + int32_t timedout; + char output[MAX_SCRIPT_OUTPUT+1]; +}; + +struct ctdb_monitoring_wire { + uint32_t num_scripts; + struct ctdb_monitoring_script_wire scripts[1]; +}; + +int ctdb_ctrl_getscriptstatus(struct ctdb_context *ctdb, + struct timeval timeout, uint32_t destnode, + TALLOC_CTX *mem_ctx, struct ctdb_monitoring_wire **script_status); + + #endif diff --git a/ctdb/include/ctdb_private.h b/ctdb/include/ctdb_private.h index ceac3842bd..988b6d94bb 100644 --- a/ctdb/include/ctdb_private.h +++ b/ctdb/include/ctdb_private.h @@ -412,6 +412,8 @@ struct ctdb_context { TALLOC_CTX *eventscripts_ctx; /* a context to hold data for the RUN_EVENTSCRIPTS control */ uint32_t *recd_ping_count; TALLOC_CTX *release_ips_ctx; /* a context used to automatically drop all IPs if we fail to recover the node */ + TALLOC_CTX *script_monitoring_ctx; /* a context where we store results while running the monitor event */ + TALLOC_CTX *last_monitoring_ctx; }; struct ctdb_db_context { @@ -550,6 +552,11 @@ enum ctdb_controls {CTDB_CONTROL_PROCESS_EXISTS = 0, CTDB_CONTROL_TAKEOVER_IP = 89, CTDB_CONTROL_GET_PUBLIC_IPS = 90, CTDB_CONTROL_GET_NODEMAP = 91, + CTDB_CONTROL_EVENT_SCRIPT_INIT = 92, + CTDB_CONTROL_EVENT_SCRIPT_START = 93, + CTDB_CONTROL_EVENT_SCRIPT_STOP = 94, + CTDB_CONTROL_EVENT_SCRIPT_FINISHED = 95, + CTDB_CONTROL_GET_EVENT_SCRIPT_STATUS = 96, }; /* @@ -1401,4 +1408,19 @@ int32_t ctdb_control_set_recmaster(struct ctdb_context *ctdb, uint32_t opcode, T extern int script_log_level; +int ctdb_ctrl_event_script_init(struct ctdb_context *ctdb); +int ctdb_ctrl_event_script_start(struct ctdb_context *ctdb, const char *name); +int ctdb_ctrl_event_script_stop(struct ctdb_context *ctdb, int32_t res); +int ctdb_ctrl_event_script_finished(struct ctdb_context *ctdb); + +int32_t ctdb_control_event_script_init(struct ctdb_context *ctdb); +int32_t ctdb_control_event_script_start(struct ctdb_context *ctdb, TDB_DATA indata); +int32_t ctdb_control_event_script_stop(struct ctdb_context *ctdb, TDB_DATA indata); +int32_t ctdb_control_event_script_finished(struct ctdb_context *ctdb); + + +int32_t ctdb_control_get_event_script_status(struct ctdb_context *ctdb, TDB_DATA *outdata); + +int ctdb_log_event_script_output(struct ctdb_context *ctdb, char *str, uint16_t len); + #endif diff --git a/ctdb/server/ctdb_control.c b/ctdb/server/ctdb_control.c index b8b31c9b51..ac77696a4b 100644 --- a/ctdb/server/ctdb_control.c +++ b/ctdb/server/ctdb_control.c @@ -418,6 +418,25 @@ static int32_t ctdb_control_dispatch(struct ctdb_context *ctdb, CHECK_CONTROL_DATA_SIZE(0); return ctdb_control_recd_ping(ctdb); + case CTDB_CONTROL_EVENT_SCRIPT_INIT: + CHECK_CONTROL_DATA_SIZE(0); + return ctdb_control_event_script_init(ctdb); + + case CTDB_CONTROL_EVENT_SCRIPT_START: + return ctdb_control_event_script_start(ctdb, indata); + + case CTDB_CONTROL_EVENT_SCRIPT_STOP: + CHECK_CONTROL_DATA_SIZE(sizeof(int32_t)); + return ctdb_control_event_script_stop(ctdb, indata); + + case CTDB_CONTROL_EVENT_SCRIPT_FINISHED: + CHECK_CONTROL_DATA_SIZE(0); + return ctdb_control_event_script_finished(ctdb); + + case CTDB_CONTROL_GET_EVENT_SCRIPT_STATUS: + CHECK_CONTROL_DATA_SIZE(0); + return ctdb_control_get_event_script_status(ctdb, outdata); + default: DEBUG(DEBUG_CRIT,(__location__ " Unknown CTDB control opcode %u\n", opcode)); return -1; diff --git a/ctdb/server/ctdb_logging.c b/ctdb/server/ctdb_logging.c index 06c7eb8b69..45a9f7410e 100644 --- a/ctdb/server/ctdb_logging.c +++ b/ctdb/server/ctdb_logging.c @@ -163,6 +163,8 @@ static void ctdb_log_handler(struct event_context *ev, struct fd_event *fde, } if (script_log_level <= LogLevel) { do_debug("%*.*s\n", n2, n2, ctdb->log->buf); + /* log it in the eventsystem as well */ + ctdb_log_event_script_output(ctdb, ctdb->log->buf, n2); } memmove(ctdb->log->buf, p+1, sizeof(ctdb->log->buf) - n1); ctdb->log->buf_used -= n1; @@ -174,6 +176,8 @@ static void ctdb_log_handler(struct event_context *ev, struct fd_event *fde, if (script_log_level <= LogLevel) { do_debug("%*.*s\n", (int)ctdb->log->buf_used, (int)ctdb->log->buf_used, ctdb->log->buf); + /* log it in the eventsystem as well */ + ctdb_log_event_script_output(ctdb, ctdb->log->buf, ctdb->log->buf_used); } ctdb->log->buf_used = 0; } diff --git a/ctdb/server/eventscript.c b/ctdb/server/eventscript.c index 6edd1a4dc6..2d0ac40861 100644 --- a/ctdb/server/eventscript.c +++ b/ctdb/server/eventscript.c @@ -52,6 +52,235 @@ struct ctdb_event_script_state { const char *options; }; + +struct ctdb_monitor_script_status { + struct ctdb_monitor_script_status *next; + const char *name; + struct timeval start; + struct timeval finished; + int32_t status; + int32_t timedout; + char *output; +}; + +struct ctdb_monitoring_status { + struct timeval start; + struct timeval finished; + int32_t status; + struct ctdb_monitor_script_status *scripts; +}; + + +/* called from ctdb_logging when we have received output on STDERR from + * one of the eventscripts + */ +int ctdb_log_event_script_output(struct ctdb_context *ctdb, char *str, uint16_t len) +{ + struct ctdb_monitoring_status *monitoring_status = + talloc_get_type(ctdb->script_monitoring_ctx, + struct ctdb_monitoring_status); + struct ctdb_monitor_script_status *script; + + if (monitoring_status == NULL) { + return -1; + } + + script = monitoring_status->scripts; + if (script == NULL) { + return -1; + } + + if (script->output == NULL) { + script->output = talloc_asprintf(script, "%*.*s", len, len, str); + } else { + script->output = talloc_asprintf_append(script->output, "%*.*s", len, len, str); + } + + return 0; +} + +/* called from the event script child process when we are starting a new + * monitor event + */ +int32_t ctdb_control_event_script_init(struct ctdb_context *ctdb) +{ + struct ctdb_monitoring_status *monitoring_status; + + DEBUG(DEBUG_INFO, ("event script init called\n")); + if (ctdb->script_monitoring_ctx != NULL) { + talloc_free(ctdb->script_monitoring_ctx); + ctdb->script_monitoring_ctx = NULL; + } + + monitoring_status = talloc_zero(ctdb, struct ctdb_monitoring_status); + if (monitoring_status == NULL) { + DEBUG(DEBUG_ERR, (__location__ " ERROR: Failed to talloc script_monitoring context\n")); + return -1; + } + + ctdb->script_monitoring_ctx = monitoring_status; + monitoring_status->start = timeval_current(); + + return 0; +} + + +/* called from the event script child process when we are star running + * an eventscript + */ +int32_t ctdb_control_event_script_start(struct ctdb_context *ctdb, TDB_DATA indata) +{ + const char *name = (const char *)indata.dptr; + struct ctdb_monitoring_status *monitoring_status = + talloc_get_type(ctdb->script_monitoring_ctx, + struct ctdb_monitoring_status); + struct ctdb_monitor_script_status *script; + + DEBUG(DEBUG_INFO, ("event script start called : %s\n", name)); + + if (monitoring_status == NULL) { + DEBUG(DEBUG_ERR,(__location__ " script_status is NULL when starting to run script %s\n", name)); + return -1; + } + + script = talloc_zero(monitoring_status, struct ctdb_monitor_script_status); + if (script == NULL) { + DEBUG(DEBUG_ERR,(__location__ " Failed to talloc ctdb_monitor_script_status for script %s\n", name)); + return -1; + } + + script->next = monitoring_status->scripts; + script->name = talloc_strdup(script, name); + script->start = timeval_current(); + monitoring_status->scripts = script; + + return 0; +} + +/* called from the event script child process when we have finished running + * an eventscript + */ +int32_t ctdb_control_event_script_stop(struct ctdb_context *ctdb, TDB_DATA indata) +{ + int32_t res = *((int32_t *)indata.dptr); + struct ctdb_monitoring_status *monitoring_status = + talloc_get_type(ctdb->script_monitoring_ctx, + struct ctdb_monitoring_status); + struct ctdb_monitor_script_status *script; + + DEBUG(DEBUG_INFO, ("event script stop called : %d\n", (int)res)); + + if (monitoring_status == NULL) { + DEBUG(DEBUG_ERR,(__location__ " script_status is NULL when script finished.\n")); + return -1; + } + + script = monitoring_status->scripts; + if (script == NULL) { + DEBUG(DEBUG_ERR,(__location__ " script is NULL when the script had finished\n")); + return -1; + } + + script->finished = timeval_current(); + script->status = res; + + return 0; +} + +/* called from the event script child process when we have completed a + * monitor event + */ +int32_t ctdb_control_event_script_finished(struct ctdb_context *ctdb) +{ + struct ctdb_monitoring_status *monitoring_status = + talloc_get_type(ctdb->script_monitoring_ctx, + struct ctdb_monitoring_status); + + DEBUG(DEBUG_INFO, ("event script finished called\n")); + + if (monitoring_status == NULL) { + DEBUG(DEBUG_ERR,(__location__ " script_status is NULL when monitoring event finished\n")); + return -1; + } + + monitoring_status->finished = timeval_current(); + monitoring_status->status = MONITOR_SCRIPT_OK; + if (ctdb->last_monitoring_ctx) { + talloc_free(ctdb->last_monitoring_ctx); + } + ctdb->last_monitoring_ctx = ctdb->script_monitoring_ctx; + ctdb->script_monitoring_ctx = NULL; + + return 0; +} + +static struct ctdb_monitoring_wire *marshall_monitoring_scripts(TALLOC_CTX *mem_ctx, struct ctdb_monitoring_wire *monitoring_scripts, struct ctdb_monitor_script_status *script) +{ + struct ctdb_monitoring_script_wire script_wire; + size_t size; + + if (script == NULL) { + return monitoring_scripts; + } + monitoring_scripts = marshall_monitoring_scripts(mem_ctx, monitoring_scripts, script->next); + if (monitoring_scripts == NULL) { + return NULL; + } + + bzero(&script_wire, sizeof(struct ctdb_monitoring_script_wire)); + strncpy(script_wire.name, script->name, MAX_SCRIPT_NAME); + script_wire.start = script->start; + script_wire.finished = script->finished; + script_wire.status = script->status; + script_wire.timedout = script->timedout; + if (script->output != NULL) { + strncpy(script_wire.output, script->output, MAX_SCRIPT_OUTPUT); + } + + size = talloc_get_size(monitoring_scripts); + monitoring_scripts = talloc_realloc_size(mem_ctx, monitoring_scripts, size + sizeof(struct ctdb_monitoring_script_wire)); + if (monitoring_scripts == NULL) { + DEBUG(DEBUG_ERR,(__location__ " Failed to talloc_resize monitoring_scripts blob\n")); + return NULL; + } + + memcpy(&monitoring_scripts->scripts[monitoring_scripts->num_scripts], &script_wire, sizeof(script_wire)); + monitoring_scripts->num_scripts++; + + return monitoring_scripts; +} + +int32_t ctdb_control_get_event_script_status(struct ctdb_context *ctdb, TDB_DATA *outdata) +{ + struct ctdb_monitoring_status *monitoring_status = + talloc_get_type(ctdb->last_monitoring_ctx, + struct ctdb_monitoring_status); + struct ctdb_monitoring_wire *monitoring_scripts; + + if (monitoring_status == NULL) { + DEBUG(DEBUG_ERR,(__location__ " last_monitor_ctx is NULL when reading status\n")); + return -1; + } + + monitoring_scripts = talloc_size(outdata, offsetof(struct ctdb_monitoring_wire, scripts)); + if (monitoring_scripts == NULL) { + DEBUG(DEBUG_ERR,(__location__ " failed to talloc monitoring_scripts structure\n")); + return -1; + } + + monitoring_scripts->num_scripts = 0; + monitoring_scripts = marshall_monitoring_scripts(outdata, monitoring_scripts, monitoring_status->scripts); + if (monitoring_scripts == NULL) { + DEBUG(DEBUG_ERR,(__location__ " Monitoring scritps is NULL. can not return data to client\n")); + return -1; + } + + outdata->dsize = talloc_get_size(monitoring_scripts); + outdata->dptr = (uint8_t *)monitoring_scripts; + + return 0; +} + /* run the event script - varargs version this function is called and run in the context of a forked child @@ -68,6 +297,27 @@ static int ctdb_event_script_v(struct ctdb_context *ctdb, const char *options) struct dirent *de; char *script; int count; + int is_monitor = 0; + + /* This is running in the forked child process. At this stage + * we want to switch from being a ctdb daemon into being a client + * and connect to the local daemon. + */ + if (switch_from_server_to_client(ctdb) != 0) { + DEBUG(DEBUG_CRIT, (__location__ "ERROR: failed to switch eventscript child into client mode. shutting down.\n")); + exit(1); + } + + if (!strcmp(options, "monitor")) { + is_monitor = 1; + } + if (is_monitor == 1) { + if (ctdb_ctrl_event_script_init(ctdb) != 0) { + DEBUG(DEBUG_ERR,(__location__ " Failed to init event script monitoring\n")); + talloc_free(tmp_ctx); + return -1; + } + } if (ctdb->recovery_mode != CTDB_RECOVERY_NORMAL) { /* we guarantee that only some specifically allowed event scripts are run @@ -80,6 +330,7 @@ static int ctdb_event_script_v(struct ctdb_context *ctdb, const char *options) if (i == ARRAY_SIZE(allowed_scripts)) { DEBUG(DEBUG_ERR,("Refusing to run event scripts with option '%s' while in recovery\n", options)); + talloc_free(tmp_ctx); return -1; } } @@ -175,6 +426,14 @@ static int ctdb_event_script_v(struct ctdb_context *ctdb, const char *options) child_state.start = timeval_current(); child_state.script_running = cmdstr; + if (is_monitor == 1) { + if (ctdb_ctrl_event_script_start(ctdb, script) != 0) { + DEBUG(DEBUG_ERR,(__location__ " Failed to start event script monitoring\n")); + talloc_free(tmp_ctx); + return -1; + } + } + ret = system(cmdstr); /* if the system() call was successful, translate ret into the return code from the command @@ -182,9 +441,25 @@ static int ctdb_event_script_v(struct ctdb_context *ctdb, const char *options) if (ret != -1) { ret = WEXITSTATUS(ret); } + if (is_monitor == 1) { + if (ctdb_ctrl_event_script_stop(ctdb, ret) != 0) { + DEBUG(DEBUG_ERR,(__location__ " Failed to stop event script monitoring\n")); + talloc_free(tmp_ctx); + return -1; + } + } + /* return an error if the script failed */ if (ret != 0) { DEBUG(DEBUG_ERR,("Event script %s failed with error %d\n", cmdstr, ret)); + if (is_monitor == 1) { + if (ctdb_ctrl_event_script_finished(ctdb) != 0) { + DEBUG(DEBUG_ERR,(__location__ " Failed to finish event script monitoring\n")); + talloc_free(tmp_ctx); + return -1; + } + } + talloc_free(tmp_ctx); return ret; } @@ -196,6 +471,14 @@ static int ctdb_event_script_v(struct ctdb_context *ctdb, const char *options) child_state.start = timeval_current(); child_state.script_running = "finished"; + if (is_monitor == 1) { + if (ctdb_ctrl_event_script_finished(ctdb) != 0) { + DEBUG(DEBUG_ERR,(__location__ " Failed to finish event script monitoring\n")); + talloc_free(tmp_ctx); + return -1; + } + } + talloc_free(tmp_ctx); return 0; } @@ -249,6 +532,9 @@ static void ctdb_event_script_timeout(struct event_context *ev, struct timed_eve void *private_data = state->private_data; struct ctdb_context *ctdb = state->ctdb; char *options; + struct ctdb_monitoring_status *monitoring_status = + talloc_get_type(ctdb->script_monitoring_ctx, + struct ctdb_monitoring_status); DEBUG(DEBUG_ERR,("Event script timed out : %s count : %u\n", state->options, ctdb->event_script_timeouts)); @@ -282,6 +568,21 @@ static void ctdb_event_script_timeout(struct event_context *ev, struct timed_eve callback(ctdb, -1, private_data); } + if (monitoring_status != NULL) { + struct ctdb_monitor_script_status *script; + + script = monitoring_status->scripts; + if (script != NULL) { + script->timedout = 1; + } + monitoring_status->status = MONITOR_SCRIPT_TIMEOUT; + if (ctdb->last_monitoring_ctx) { + talloc_free(ctdb->last_monitoring_ctx); + ctdb->last_monitoring_ctx = ctdb->script_monitoring_ctx; + ctdb->script_monitoring_ctx = NULL; + } + } + talloc_free(options); } @@ -337,10 +638,8 @@ static int ctdb_event_script_callback_v(struct ctdb_context *ctdb, signed char rt; close(state->fd[0]); - if (ctdb->do_setsched) { - ctdb_restore_scheduler(ctdb); - } set_close_on_exec(state->fd[1]); + rt = ctdb_event_script_v(ctdb, state->options); while ((ret = write(state->fd[1], &rt, sizeof(rt))) != sizeof(rt)) { sleep(1); diff --git a/ctdb/tools/ctdb.c b/ctdb/tools/ctdb.c index b2014f0eb6..c48d587095 100644 --- a/ctdb/tools/ctdb.c +++ b/ctdb/tools/ctdb.c @@ -471,6 +471,44 @@ static int control_status(struct ctdb_context *ctdb, int argc, const char **argv return 0; } + +/* + display the status of the monitoring scripts + */ +static int control_scriptstatus(struct ctdb_context *ctdb, int argc, const char **argv) +{ + int i, ret; + struct ctdb_monitoring_wire *script_status; + + ret = ctdb_ctrl_getscriptstatus(ctdb, TIMELIMIT(), options.pnn, ctdb, &script_status); + if (ret != 0) { + DEBUG(DEBUG_ERR, ("Unable to get script status from node %u\n", options.pnn)); + return ret; + } + + printf("%d scripts were executed last monitoring cycle\n", script_status->num_scripts); + for (i=0; inum_scripts; i++) { + printf("%-20s Status:%s ", + script_status->scripts[i].name, + script_status->scripts[i].timedout?"TIMEDOUT":script_status->scripts[i].status==0?"OK":"ERROR"); + if (script_status->scripts[i].timedout == 0) { + printf("Duration:%.3lf ", + timeval_delta(&script_status->scripts[i].finished, + &script_status->scripts[i].start)); + } + printf("%s", + ctime(&script_status->scripts[i].start.tv_sec)); + if ((script_status->scripts[i].timedout != 0) + || (script_status->scripts[i].status != 0) ) { + printf(" OUTPUT:%s\n", + script_status->scripts[i].output); + } + } + + return 0; +} + + /* display the pnn of the recovery master */ @@ -2647,6 +2685,7 @@ static const struct { { "restoredb", control_restoredb, false, "restore the database from a file.", ""}, { "recmaster", control_recmaster, false, "show the pnn for the recovery master."}, { "setflags", control_setflags, false, "set flags for a node in the nodemap.", " "}, + { "scriptstatus", control_scriptstatus, false, "show the status of the monitoring scripts"}, }; /* -- cgit