The branch, master has been updated
via b77e4698e7f83443243965f93b84237f2903cd46 (commit)
via b1fe04f2e9447f762a0b805763deb29296585ff8 (commit)
from fe26da7780545b1ecc0a7da5bc1cf8beaeea94cc (commit)
http://gitweb.samba.org/?p=sahlberg/ctdb.git;a=shortlog;h=master
- Log -----------------------------------------------------------------
commit b77e4698e7f83443243965f93b84237f2903cd46
Author: Ronnie Sahlberg <ronniesahlb...@gmail.com>
Date: Thu Oct 1 14:31:55 2009 +1000
document how to use the notification script
commit b1fe04f2e9447f762a0b805763deb29296585ff8
Author: Ronnie Sahlberg <ronniesahlb...@gmail.com>
Date: Thu Oct 1 14:05:30 2009 +1000
add a new notification to trigger on when ctdb has started
-----------------------------------------------------------------------
Summary of changes:
config/notify.sh | 4 ++
doc/ctdbd.1 | 37 ++++++++++++++++---
doc/ctdbd.1.html | 96 +++++++++++++++++++++++++++++++------------------
doc/ctdbd.1.xml | 58 ++++++++++++++++++++++++++++-
server/ctdb_monitor.c | 1 +
5 files changed, 154 insertions(+), 42 deletions(-)
Changeset truncated at 500 lines:
diff --git a/config/notify.sh b/config/notify.sh
index 9c97ab9..3a9c861 100755
--- a/config/notify.sh
+++ b/config/notify.sh
@@ -32,6 +32,10 @@ case $event in
#
# or do something else ...
;;
+ startup)
+# do some extra magic when ctdb has started?
+ ;;
+
esac
exit 0
diff --git a/doc/ctdbd.1 b/doc/ctdbd.1
index 242bd45..7c6e3aa 100644
--- a/doc/ctdbd.1
+++ b/doc/ctdbd.1
@@ -1,11 +1,11 @@
.\" Title: ctdbd
.\" Author:
.\" Generator: DocBook XSL Stylesheets v1.73.2 <http://docbook.sf.net/>
-.\" Date: 07/09/2009
+.\" Date: 10/01/2009
.\" Manual:
.\" Source:
.\"
-.TH "CTDBD" "1" "07/09/2009" "" ""
+.TH "CTDBD" "1" "10/01/2009" "" ""
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
@@ -16,7 +16,7 @@ ctdbd - The CTDB cluster daemon
.HP 6
\fBctdbd\fR
.HP 6
-\fBctdbd\fR [\-?\ \-\-help] [\-d\ \-\-debug=<INTEGER>] {\-\-dbdir=<directory>}
{\-\-dbdir\-persistent=<directory>} [\-\-event\-script\-dir=<directory>] [\-i\
\-\-interactive] [\-\-listen=<address>] [\-\-logfile=<filename>] [\-\-lvs]
{\-\-nlist=<filename>} [\-\-no\-lmaster] [\-\-no\-recmaster] [\-\-nosetsched]
[\-\-public\-addresses=<filename>] [\-\-public\-interface=<interface>]
{\-\-reclock=<filename>} [\-\-single\-public\-ip=<address>]
[\-\-socket=<filename>] [\-\-start\-as\-disabled] [\-\-start\-as\-stopped]
[\-\-syslog] [\-\-torture] [\-\-transport=<STRING>] [\-\-usage]
+\fBctdbd\fR [\-?\ \-\-help] [\-d\ \-\-debug=<INTEGER>] {\-\-dbdir=<directory>}
{\-\-dbdir\-persistent=<directory>} [\-\-event\-script\-dir=<directory>] [\-i\
\-\-interactive] [\-\-listen=<address>] [\-\-logfile=<filename>] [\-\-lvs]
{\-\-nlist=<filename>} [\-\-no\-lmaster] [\-\-no\-recmaster] [\-\-nosetsched]
{\-\-notification\-script=<filename>} [\-\-public\-addresses=<filename>]
[\-\-public\-interface=<interface>] {\-\-reclock=<filename>}
[\-\-single\-public\-ip=<address>] [\-\-socket=<filename>]
[\-\-start\-as\-disabled] [\-\-start\-as\-stopped] [\-\-syslog] [\-\-torture]
[\-\-transport=<STRING>] [\-\-usage]
.SH "DESCRIPTION"
.PP
ctdbd is the main ctdb daemon\.
@@ -113,6 +113,15 @@ Normally ctdb will change its scheduler to run as a
real\-time process\. This is
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
+\-\-notification\-script=<filename>
+.RS 4
+This specifies a script which will be invoked by ctdb when certain state
changes occur in ctdbd and when you may want to trigger this to run certain
scripts\.
+.sp
+This file is usually /etc/ctdb/notify\.sh \.
+.sp
+See the NOTIFICATION SCRIPT section below for more information\.
+.RE
+.PP
\-\-public_addresses=<filename>
.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\.
@@ -508,6 +517,24 @@ The NAT\-GW node is assigned the CTDB_NATGW_PUBLIC_IP to
the designated interfac
All other nodes in the group 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 "NOTIFICATION SCRIPT"
+.PP
+Notification scripts are used with ctdb to have a call\-out from ctdb to a
user\-specified script when certain state changes occur in ctdb\. This is
commonly to set up either sending SNMP traps or emails when a node becomes
unhealthy and similar\.
+.PP
+This is activated by setting CTDB_NOTIFY_SCRIPT=<your script> in the sysconfig
file, or by adding \-\-notification\-script=<your script>\.
+.PP
+See /etc/ctdb/notify\.sh for an example script\.
+.PP
+CTDB currently generates notifications on these state changes:
+.SS "unhealthy"
+.PP
+This call\-out is triggered when the node changes to UNHEALTHY state\.
+.SS "healthy"
+.PP
+This call\-out is triggered when the node changes to HEALTHY state\.
+.SS "startup"
+.PP
+This call\-out is triggered when ctdb has started up and all managed services
are up and running\.
.SH "CLAMAV DAEMON"
.PP
CTDB has support to manage the popular anti\-virus daemon ClamAV\. This
support is implemented through the eventscript : /etc/ctdb/events\.d/31\.clamd\.
@@ -524,11 +551,11 @@ CTDB_CLAMD_SOCKET="/path/to/clamd\.socket"
.fi
.RE
.PP
-Second, activate the eventscript by making it executable:
+Second, activate the eventscript
.sp
.RS 4
.nf
-chmod +x /etc/ctdb/events\.d/31\.clamd
+ctdb enablescript 31\.clamd
.fi
.RE
.PP
diff --git a/doc/ctdbd.1.html b/doc/ctdbd.1.html
index 3fa8d1a..dce57de 100644
--- a/doc/ctdbd.1.html
+++ b/doc/ctdbd.1.html
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1"><title>ctdbd</title><meta name="generator" content="DocBook
XSL Stylesheets V1.73.2"></head><body bgcolor="white" text="black"
link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry"
lang="en"><a name="ctdbd.1"></a><div class="titlepage"></div><div
class="refnamediv"><h2>Name</h2><p>ctdbd — The CTDB cluster
daemon</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div
class="cmdsynopsis"><p><code class="command">ctdbd</code> </p></div><div
class="cmdsynopsis"><p><code class="command">ctdbd</code> [-? --help] [-d
--debug=<INTEGER>] {--dbdir=<directory>}
{--dbdir-persistent=<directory>} [--event-script-dir=<directory>]
[-i --interactive] [--listen=<address>] [--logfile=<filename>]
[--lvs] {--nlist=<filename>} [--no-lmaster] [--no-recmaster]
[--nosetsched] [--public-addresses=<filename>]
[--public-interface=<interface>
] {--reclock=<filename>} [--single-public-ip=<address>]
[--socket=<filename>] [--start-as-disabled] [--start-as-stopped]
[--syslog] [--torture] [--transport=<STRING>]
[--usage]</p></div></div><div class="refsect1" lang="en"><a
name="id2479655"></a><h2>DESCRIPTION</h2><p>
+<html><head><meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1"><title>ctdbd</title><meta name="generator" content="DocBook
XSL Stylesheets V1.73.2"></head><body bgcolor="white" text="black"
link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry"
lang="en"><a name="ctdbd.1"></a><div class="titlepage"></div><div
class="refnamediv"><h2>Name</h2><p>ctdbd — The CTDB cluster
daemon</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div
class="cmdsynopsis"><p><code class="command">ctdbd</code> </p></div><div
class="cmdsynopsis"><p><code class="command">ctdbd</code> [-? --help] [-d
--debug=<INTEGER>] {--dbdir=<directory>}
{--dbdir-persistent=<directory>} [--event-script-dir=<directory>]
[-i --interactive] [--listen=<address>] [--logfile=<filename>]
[--lvs] {--nlist=<filename>} [--no-lmaster] [--no-recmaster]
[--nosetsched] {--notification-script=<filename>}
[--public-addresses=<filename&g
t;] [--public-interface=<interface>] {--reclock=<filename>}
[--single-public-ip=<address>] [--socket=<filename>]
[--start-as-disabled] [--start-as-stopped] [--syslog] [--torture]
[--transport=<STRING>] [--usage]</p></div></div><div class="refsect1"
lang="en"><a name="id2479664"></a><h2>DESCRIPTION</h2><p>
ctdbd is the main ctdb daemon.
</p><p>
ctdbd provides a clustered version of the TDB database with automatic
rebuild/recovery of the databases upon nodefailures.
@@ -8,7 +8,7 @@
ctdbd provides monitoring of all nodes in the cluster and automatically
reconfigures the cluster and recovers upon node failures.
</p><p>
ctdbd is the main component in clustered Samba that provides a
high-availability load-sharing CIFS server cluster.
- </p></div><div class="refsect1" lang="en"><a
name="id2479687"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span
class="term">-? --help</span></dt><dd><p>
+ </p></div><div class="refsect1" lang="en"><a
name="id2479695"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span
class="term">-? --help</span></dt><dd><p>
Print some help text to the screen.
</p></dd><dt><span class="term">-d
--debug=<DEBUGLEVEL></span></dt><dd><p>
This option sets the debuglevel on the ctdbd daemon which controls
what will be written to the logfile. The default is 0 which will only log
important events and errors. A larger number will provide additional logging.
@@ -69,6 +69,14 @@
This is useful for debugging and when you want to run ctdbd under
valgrind or gdb. (You dont want to attach valgrind or gdb to a
real-time process.)
+ </p></dd><dt><span
class="term">--notification-script=<filename></span></dt><dd><p>
+ This specifies a script which will be invoked by ctdb when certain
+ state changes occur in ctdbd and when you may want to trigger this
+ to run certain scripts.
+ </p><p>
+ This file is usually /etc/ctdb/notify.sh .
+ </p><p>
+ See the NOTIFICATION SCRIPT section below for more information.
</p></dd><dt><span
class="term">--public_addresses=<filename></span></dt><dd><p>
When used with IP takeover this specifies a file containing the
public ip addresses to use on the cluster. This file contains a list of ip
addresses netmasks and interfaces. When ctdb is operational it will distribute
these public ip addresses evenly across the available nodes.
</p><p>
@@ -129,10 +137,10 @@
implemented in the future.
</p></dd><dt><span class="term">--usage</span></dt><dd><p>
Print useage information to the screen.
- </p></dd></dl></div></div><div class="refsect1" lang="en"><a
name="id2528824"></a><h2>Private vs Public addresses</h2><p>
+ </p></dd></dl></div></div><div class="refsect1" lang="en"><a
name="id2528852"></a><h2>Private vs Public addresses</h2><p>
When used for ip takeover in a HA environment, each node in a ctdb
cluster has multiple ip addresses assigned to it. One private and one or
more public.
- </p><div class="refsect2" lang="en"><a name="id2528835"></a><h3>Private
address</h3><p>
+ </p><div class="refsect2" lang="en"><a name="id2528863"></a><h3>Private
address</h3><p>
This is the physical ip address of the node which is configured in
linux and attached to a physical interface. This address uniquely
identifies a physical node in the cluster and is the ip addresses
@@ -162,7 +170,7 @@
10.1.1.2
10.1.1.3
10.1.1.4
- </pre></div><div class="refsect2" lang="en"><a
name="id2528883"></a><h3>Public address</h3><p>
+ </pre></div><div class="refsect2" lang="en"><a
name="id2528911"></a><h3>Public address</h3><p>
A public address on the other hand is not attached to an interface.
This address is managed by ctdbd itself and is attached/detached to
a physical node at runtime.
@@ -223,7 +231,7 @@
unavailable. 10.1.1.1 can not be failed over to node 2 or node 3 since
these nodes do not have this ip address listed in their public
addresses file.
- </p></div></div><div class="refsect1" lang="en"><a
name="id2528965"></a><h2>Node status</h2><p>
+ </p></div></div><div class="refsect1" lang="en"><a
name="id2528993"></a><h2>Node status</h2><p>
The current status of each node in the cluster can be viewed by the
'ctdb status' command.
</p><p>
@@ -260,50 +268,50 @@
RECMASTER or NATGW.
This node does not perticipate in the CTDB cluster but can still be
communicated with. I.e. ctdb commands can be sent to it.
- </p></div><div class="refsect1" lang="en"><a
name="id2529031"></a><h2>PUBLIC TUNABLES</h2><p>
+ </p></div><div class="refsect1" lang="en"><a
name="id2529059"></a><h2>PUBLIC TUNABLES</h2><p>
These are the public tuneables that can be used to control how ctdb
behaves.
- </p><div class="refsect2" lang="en"><a
name="id2529041"></a><h3>KeepaliveInterval</h3><p>Default: 1</p><p>
+ </p><div class="refsect2" lang="en"><a
name="id2529070"></a><h3>KeepaliveInterval</h3><p>Default: 1</p><p>
How often should the nodes send keepalives to eachother.
- </p></div><div class="refsect2" lang="en"><a
name="id2529055"></a><h3>KeepaliveLimit</h3><p>Default: 5</p><p>
+ </p></div><div class="refsect2" lang="en"><a
name="id2529083"></a><h3>KeepaliveLimit</h3><p>Default: 5</p><p>
After how many keepalive intervals without any traffic should a node
wait until marking the peer as DISCONNECTED.
- </p></div><div class="refsect2" lang="en"><a
name="id2529070"></a><h3>MonitorInterval</h3><p>Default: 15</p><p>
+ </p></div><div class="refsect2" lang="en"><a
name="id2529098"></a><h3>MonitorInterval</h3><p>Default: 15</p><p>
How often should ctdb run the event scripts to check for a nodes health.
- </p></div><div class="refsect2" lang="en"><a
name="id2529084"></a><h3>TickleUpdateInterval</h3><p>Default: 20</p><p>
+ </p></div><div class="refsect2" lang="en"><a
name="id2529112"></a><h3>TickleUpdateInterval</h3><p>Default: 20</p><p>
How often will ctdb record and store the "tickle" information used to
kickstart stalled tcp connections after a recovery.
- </p></div><div class="refsect2" lang="en"><a
name="id2529098"></a><h3>EventScriptTimeout</h3><p>Default: 20</p><p>
+ </p></div><div class="refsect2" lang="en"><a
name="id2529126"></a><h3>EventScriptTimeout</h3><p>Default: 20</p><p>
How long should ctdb let an event script run before aborting it and
marking the node unhealthy.
- </p></div><div class="refsect2" lang="en"><a
name="id2529112"></a><h3>RecoveryBanPeriod</h3><p>Default: 300</p><p>
+ </p></div><div class="refsect2" lang="en"><a
name="id2529140"></a><h3>RecoveryBanPeriod</h3><p>Default: 300</p><p>
If a node becomes banned causing repetitive recovery failures. The node
will
eventually become banned from the cluster.
This controls how long the culprit node will be banned from the cluster
before it is allowed to try to join the cluster again.
Dont set to small. A node gets banned for a reason and it is usually due
to real problems with the node.
- </p></div><div class="refsect2" lang="en"><a
name="id2529131"></a><h3>DatabaseHashSize</h3><p>Default: 100000</p><p>
+ </p></div><div class="refsect2" lang="en"><a
name="id2529160"></a><h3>DatabaseHashSize</h3><p>Default: 100000</p><p>
Size of the hash chains for the local store of the tdbs that ctdb manages.
- </p></div><div class="refsect2" lang="en"><a
name="id2529146"></a><h3>RerecoveryTimeout</h3><p>Default: 10</p><p>
+ </p></div><div class="refsect2" lang="en"><a
name="id2529174"></a><h3>RerecoveryTimeout</h3><p>Default: 10</p><p>
Once a recovery has completed, no additional recoveries are permitted
until this timeout has expired.
- </p></div><div class="refsect2" lang="en"><a
name="id2529160"></a><h3>EnableBans</h3><p>Default: 1</p><p>
+ </p></div><div class="refsect2" lang="en"><a
name="id2529188"></a><h3>EnableBans</h3><p>Default: 1</p><p>
When set to 0, this disables BANNING completely in the cluster and thus
nodes can not get banned, even it they break. Dont set to 0.
- </p></div><div class="refsect2" lang="en"><a
name="id2529175"></a><h3>DeterministicIPs</h3><p>Default: 1</p><p>
+ </p></div><div class="refsect2" lang="en"><a
name="id2529203"></a><h3>DeterministicIPs</h3><p>Default: 1</p><p>
When enabled, this tunable makes ctdb try to keep public IP addresses
locked to specific nodes as far as possible. This makes it easier for debugging
since you can know that as long as all nodes are healthy public IP X will
always be hosted by node Y.
</p><p>
The cost of using deterministic IP address assignment is that it disables
part of the logic where ctdb tries to reduce the number of public IP assignment
changes in the cluster. This tunable may increase the number of IP
failover/failbacks that are performed on the cluster by a small margin.
- </p></div><div class="refsect2" lang="en"><a
name="id2529200"></a><h3>DisableWhenUnhealthy</h3><p>Default: 0</p><p>
+ </p></div><div class="refsect2" lang="en"><a
name="id2529228"></a><h3>DisableWhenUnhealthy</h3><p>Default: 0</p><p>
When set, As soon as a node becomes unhealthy, that node will also
automatically become permanently DISABLED. Once a node is DISABLED, the only
way to make it participate in the cluster again and host services is by
manually enabling the node again using 'ctdb enable'.
</p><p>
This disables parts of the resilience and robustness of the cluster and
should ONLY be used when the system administrator is actively monitoring the
cluster, so that nodes can be enabled again.
- </p></div><div class="refsect2" lang="en"><a
name="id2529224"></a><h3>NoIPFailback</h3><p>Default: 0</p><p>
+ </p></div><div class="refsect2" lang="en"><a
name="id2529252"></a><h3>NoIPFailback</h3><p>Default: 0</p><p>
When set to 1, ctdb will not perform failback of IP addresses when a node
becomes healthy. Ctdb WILL perform failover of public IP addresses when a node
becomes UNHEALTHY, but when the node becomes HEALTHY again, ctdb will not fail
the addresses back.
</p><p>
Use with caution! Normally when a node becomes available to the cluster
ctdb will try to reassign public IP addresses onto the new node as a way to
distribute the workload evenly across the clusternode. Ctdb tries to make sure
that all running nodes have approximately the same number of public addresses
it hosts.
</p><p>
When you enable this tunable, CTDB will no longer attempt to rebalance the
cluster by failing IP addresses back to the new nodes. An unbalanced cluster
will therefore remain unbalanced until there is manual intervention from the
administrator. When this parameter is set, you can manually fail public IP
addresses over to the new node(s) using the 'ctdb moveip' command.
- </p></div></div><div class="refsect1" lang="en"><a
name="id2529260"></a><h2>LVS</h2><p>
+ </p></div></div><div class="refsect1" lang="en"><a
name="id2529288"></a><h2>LVS</h2><p>
LVS is a mode where CTDB presents one single IP address for the entire
cluster. This is an alternative to using public IP addresses and
round-robin
DNS to loadbalance clients across the cluster.
@@ -344,7 +352,7 @@ ctdb will try to reassign public IP addresses onto the new
node as a way to dist
the processing node back to the clients. For read-intensive i/o patterns
you can acheive very high throughput rates in this mode.
</p><p>
Note: you can use LVS and public addresses at the same time.
- </p><div class="refsect2" lang="en"><a
name="id2529332"></a><h3>Configuration</h3><p>
+ </p><div class="refsect2" lang="en"><a
name="id2529360"></a><h3>Configuration</h3><p>
To activate LVS on a CTDB node you must specify CTDB_PUBLIC_INTERFACE and
CTDB_LVS_PUBLIC_ADDRESS in /etc/sysconfig/ctdb.
</p><p>
@@ -367,7 +375,7 @@ You must also specify the "--lvs" command line argument to
ctdbd to activete LVS
all of the clients from the node BEFORE you enable LVS. Also make sure
that when you ping these hosts that the traffic is routed out through the
eth0 interface.
- </p></div><div class="refsect1" lang="en"><a
name="id2529380"></a><h2>REMOTE CLUSTER NODES</h2><p>
+ </p></div><div class="refsect1" lang="en"><a
name="id2529408"></a><h2>REMOTE CLUSTER NODES</h2><p>
It is possible to have a CTDB cluster that spans across a WAN link.
For example where you have a CTDB cluster in your datacentre but you also
want to have one additional CTDB node located at a remote branch site.
@@ -396,7 +404,7 @@ CTDB_CAPABILITY_RECMASTER=no
</p><p>
Verify with the command "ctdb getcapabilities" that that node no longer
has the recmaster or the lmaster capabilities.
- </p></div><div class="refsect1" lang="en"><a
name="id2529431"></a><h2>NAT-GW</h2><p>
+ </p></div><div class="refsect1" lang="en"><a
name="id2529459"></a><h2>NAT-GW</h2><p>
Sometimes it is desireable to run services on the CTDB node which will
need to originate outgoing traffic to external servers. This might
be contacting NIS servers, LDAP servers etc. etc.
@@ -419,7 +427,7 @@ CTDB_CAPABILITY_RECMASTER=no
if there are no public addresses assigned to the node.
This is the simplest way but it uses up a lot of ip addresses since you
have to assign both static and also public addresses to each node.
- </p><div class="refsect2" lang="en"><a
name="id2529471"></a><h3>NAT-GW</h3><p>
+ </p><div class="refsect2" lang="en"><a
name="id2529499"></a><h3>NAT-GW</h3><p>
A second way is to use the built in NAT-GW feature in CTDB.
With NAT-GW you assign one public NATGW address for each natgw group.
Each NATGW group is a set of nodes in the cluster that shares the same
@@ -434,7 +442,7 @@ CTDB_CAPABILITY_RECMASTER=no
In each NATGW group, one of the nodes is designated the NAT Gateway
through which all traffic that is originated by nodes in this group
will be routed through if a public addresses are not available.
- </p></div><div class="refsect2" lang="en"><a
name="id2529501"></a><h3>Configuration</h3><p>
+ </p></div><div class="refsect2" lang="en"><a
name="id2529529"></a><h3>Configuration</h3><p>
NAT-GW is configured in /etc/sysconfigctdb by setting the following
variables:
</p><pre class="screen">
@@ -485,19 +493,19 @@ CTDB_CAPABILITY_RECMASTER=no
assigned to. This should be an interface connected to the public network.
</p><p>
Format of this parameter is INTERFACE
- </p></div><div class="refsect2" lang="en"><a
name="id2476134"></a><h3>CTDB_NATGW_DEFAULT_GATEWAY</h3><p>
+ </p></div><div class="refsect2" lang="en"><a
name="id2475745"></a><h3>CTDB_NATGW_DEFAULT_GATEWAY</h3><p>
This is the default gateway to use on the node that is elected to host
the CTDB_NATGW_PUBLIC_IP. This is the default gateway on the public
network.
</p><p>
Format of this parameter is IPADDRESS
- </p></div><div class="refsect2" lang="en"><a
name="id2476150"></a><h3>CTDB_NATGW_PRIVATE_NETWORK</h3><p>
+ </p></div><div class="refsect2" lang="en"><a
name="id2475761"></a><h3>CTDB_NATGW_PRIVATE_NETWORK</h3><p>
This is the network/netmask used for the interal private network.
</p><p>
Format of this parameter is IPADDRESS/NETMASK
- </p></div><div class="refsect2" lang="en"><a
name="id2476164"></a><h3>CTDB_NATGW_NODES</h3><p>
+ </p></div><div class="refsect2" lang="en"><a
name="id2475775"></a><h3>CTDB_NATGW_NODES</h3><p>
This is the list of all nodes that belong to the same NATGW group
as this node. The default is /etc/ctdb/natgw_nodes.
- </p></div><div class="refsect2" lang="en"><a
name="id2476176"></a><h3>Operation</h3><p>
+ </p></div><div class="refsect2" lang="en"><a
name="id2475786"></a><h3>Operation</h3><p>
When the NAT-GW functionality is used, one of the nodes is elected
to act as a NAT router for all the other nodes in the group when
they need to originate traffic to the external public network.
@@ -512,11 +520,29 @@ CTDB_CAPABILITY_RECMASTER=no
</p><p>
This is implemented in the 11.natgw eventscript. Please see the
eventscript for further information.
- </p></div></div><div class="refsect1" lang="en"><a
name="id2476209"></a><h2>ClamAV Daemon</h2><p>
+ </p></div></div><div class="refsect1" lang="en"><a
name="id2475819"></a><h2>NOTIFICATION SCRIPT</h2><p>
+ Notification scripts are used with ctdb to have a call-out from ctdb
+ to a user-specified script when certain state changes occur in ctdb.
+ This is commonly to set up either sending SNMP traps or emails
+ when a node becomes unhealthy and similar.
+ </p><p>
+ This is activated by setting CTDB_NOTIFY_SCRIPT=<your script> in
the
+ sysconfig file, or by adding --notification-script=<your script>.
+ </p><p>
+ See /etc/ctdb/notify.sh for an example script.
+ </p><p>
+ CTDB currently generates notifications on these state changes:
+ </p><div class="refsect2" lang="en"><a
name="id2475850"></a><h3>unhealthy</h3><p>
+ This call-out is triggered when the node changes to UNHEALTHY state.
+ </p></div><div class="refsect2" lang="en"><a
name="id2475860"></a><h3>healthy</h3><p>
+ This call-out is triggered when the node changes to HEALTHY state.
+ </p></div><div class="refsect2" lang="en"><a
name="id2475870"></a><h3>startup</h3><p>
+ This call-out is triggered when ctdb has started up and all managed
services are up and running.
+ </p></div></div><div class="refsect1" lang="en"><a
name="id2475882"></a><h2>ClamAV Daemon</h2><p>
CTDB has support to manage the popular anti-virus daemon ClamAV.
This support is implemented through the
eventscript : /etc/ctdb/events.d/31.clamd.
-</p><div class="refsect2" lang="en"><a
name="id2476220"></a><h3>Configuration</h3><p>
+</p><div class="refsect2" lang="en"><a
name="id2475893"></a><h3>Configuration</h3><p>
Start by configuring CLAMAV normally and test that it works. Once this is
done, copy the configuration files over to all the nodes so that all nodes
share identical CLAMAV configurations.
@@ -528,9 +554,9 @@ First, to activate CLAMAV support in CTDB, edit
/etc/sysconfig/ctdb and add the
CTDB_MANAGES_CLAMD=yes
CTDB_CLAMD_SOCKET="/path/to/clamd.socket"
</pre><p>
-Second, activate the eventscript by making it executable:
+Second, activate the eventscript
</p><pre class="screen">
-chmod +x /etc/ctdb/events.d/31.clamd
+ctdb enablescript 31.clamd
</pre><p>
Third, CTDB will now be starting and stopping this service accordingly,
so make sure that the system is not configured to start/stop this service
@@ -545,10 +571,10 @@ Once you have restarted CTDBD, use
ctdb scriptstatus
</pre><p>
and verify that the 31.clamd eventscript is listed and that it was executed
successfully.
-</p></div></div><div class="refsect1" lang="en"><a
name="id2476280"></a><h2>SEE ALSO</h2><p>
+</p></div></div><div class="refsect1" lang="en"><a
name="id2475952"></a><h2>SEE ALSO</h2><p>
ctdb(1), onnode(1)
<a class="ulink" href="http://ctdb.samba.org/";
target="_top">http://ctdb.samba.org/</a>
- </p></div><div class="refsect1" lang="en"><a
name="id2476293"></a><h2>COPYRIGHT/LICENSE</h2><div
class="literallayout"><p><br>
+ </p></div><div class="refsect1" lang="en"><a
name="id2475965"></a><h2>COPYRIGHT/LICENSE</h2><div
class="literallayout"><p><br>
Copyright (C) Andrew Tridgell 2007<br>
Copyright (C) Ronnie sahlberg 2007<br>
<br>
diff --git a/doc/ctdbd.1.xml b/doc/ctdbd.1.xml
index 992500c..032a8c2 100644
--- a/doc/ctdbd.1.xml
+++ b/doc/ctdbd.1.xml
@@ -33,6 +33,7 @@
<arg choice="opt">--no-lmaster</arg>
<arg choice="opt">--no-recmaster</arg>
<arg choice="opt">--nosetsched</arg>
+ <arg choice="req">--notification-script=<filename></arg>
<arg choice="opt">--public-addresses=<filename></arg>
<arg choice="opt">--public-interface=<interface></arg>
<arg choice="req">--reclock=<filename></arg>
@@ -219,6 +220,22 @@
</listitem>
</varlistentry>
+ <varlistentry><term>--notification-script=<filename></term>
+ <listitem>
+ <para>
+ This specifies a script which will be invoked by ctdb when certain
+ state changes occur in ctdbd and when you may want to trigger this
+ to run certain scripts.
+ </para>
+ <para>
+ This file is usually /etc/ctdb/notify.sh .
+ </para>
+ <para>
+ See the NOTIFICATION SCRIPT section below for more information.
+ </para>
+ </listitem>
+ </varlistentry>
+
<varlistentry><term>--public_addresses=<filename></term>
<listitem>
<para>
@@ -929,6 +946,43 @@ CTDB_CAPABILITY_RECMASTER=no
</refsect1>
+ <refsect1><title>NOTIFICATION SCRIPT</title>
+ <para>
+ Notification scripts are used with ctdb to have a call-out from ctdb
+ to a user-specified script when certain state changes occur in ctdb.
+ This is commonly to set up either sending SNMP traps or emails
+ when a node becomes unhealthy and similar.
+ </para>
+ <para>
+ This is activated by setting CTDB_NOTIFY_SCRIPT=<your script> in
the
+ sysconfig file, or by adding --notification-script=<your script>.
+ </para>
+ <para>
+ See /etc/ctdb/notify.sh for an example script.
+ </para>
+ <para>
+ CTDB currently generates notifications on these state changes:
+ </para>
+
+ <refsect2><title>unhealthy</title>
+ <para>
+ This call-out is triggered when the node changes to UNHEALTHY state.
+ </para>
+ </refsect2>
+
+ <refsect2><title>healthy</title>
+ <para>
+ This call-out is triggered when the node changes to HEALTHY state.
+ </para>
+ </refsect2>
+
+ <refsect2><title>startup</title>
+ <para>
+ This call-out is triggered when ctdb has started up and all managed
services are up and running.
+ </para>
+ </refsect2>
+
+ </refsect1>
<refsect1><title>ClamAV Daemon</title>
@@ -956,10 +1010,10 @@ CTDB_CLAMD_SOCKET="/path/to/clamd.socket"
</screen>
<para>
-Second, activate the eventscript by making it executable:
+Second, activate the eventscript
</para>
<screen format="linespecific">
-chmod +x /etc/ctdb/events.d/31.clamd
+ctdb enablescript 31.clamd
</screen>
<para>
diff --git a/server/ctdb_monitor.c b/server/ctdb_monitor.c
index 1e8f8c8..c230c0c 100644
--- a/server/ctdb_monitor.c
+++ b/server/ctdb_monitor.c
@@ -170,6 +170,7 @@ static void ctdb_startup_callback(struct ctdb_context
*ctdb, int status, void *p
DEBUG(DEBUG_NOTICE,("startup event OK - enabling
monitoring\n"));
ctdb->done_startup = true;
ctdb->monitor->next_interval = 1;
+ ctdb_run_notification_script(ctdb, "startup");
}
event_add_timed(ctdb->ev, ctdb->monitor->monitor_context,
--
CTDB repository
