From 8e64c1085d79c311d7eafc7c5f429a3ad9c05aca Mon Sep 17 00:00:00 2001 From: Andrew Tridgell Date: Fri, 8 Jun 2007 13:58:53 +1000 Subject: new web page layout (This used to be ctdb commit 2d863a9152fae3823dcf08268b9f10dc815e198b) --- ctdb/web/testing.html | 95 +++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 95 insertions(+) create mode 100644 ctdb/web/testing.html (limited to 'ctdb/web/testing.html') diff --git a/ctdb/web/testing.html b/ctdb/web/testing.html new file mode 100644 index 0000000000..10c34d8665 --- /dev/null +++ b/ctdb/web/testing.html @@ -0,0 +1,95 @@ + + + +Starting and testing CTDB + + + +

Starting and testing CTDB

+ + +

Starting and testing CTDB

+The CTDB log is in /var/log/log.ctdb so look in this file if something diud not start correctly.

+ +Log in to all of the nodes in the cluster and start the ctdb service using +

+  service ctdb start
+

+Verify that the CTDB daemon started properly. There should normally be at least 2 processes started for CTDB, one for the main daemon and one for the recovery daemon. +

+  pidof ctdbd
+

+ +Once all CTDB nodes have started, verify that they are correctly talking to eachothers.
+There should be one TCP connection from the private ip address on each node to TCP port 9001 on each of the other nodes in the cluster. +

+  netstat -a -n | grep 9001
+

+ + +

Automatically restarting CTDB

+If you wish to cope with software faults in ctdb, or want ctdb to automatically restart when an administration kills it, then you may wish to add a cron entry for root like this: + +

+ * * * * * /etc/init.d/ctdb cron > /dev/null 2>&1
+

+ + +

Testing CTDB

+ +Once your cluster is up and running, you may wish to know how to test that it is functioning correctly. The following tests may help with that + +

The ctdb tool

+ +The ctdb package comes with a utility called ctdb that can be used to view the behaviour of the ctdb cluster.
+If you run it with no options it will provide some terse usage information. The most commonly used commands are: +

+ ctdb status
+ ctdb ip
+ ctdb ping
+

+ +

ctdb status

+The status command provides basic information about the cluster and the status of the nodes. when you run it you will get some output like : +

+Number of nodes:4
+vnn:0 10.1.1.1       OK (THIS NODE)
+vnn:1 10.1.1.2       OK
+vnn:2 10.1.1.3       OK
+vnn:3 10.1.1.4       OK
+Generation:1362079228
+Size:4
+hash:0 lmaster:0
+hash:1 lmaster:1
+hash:2 lmaster:2
+hash:3 lmaster:3
+Recovery mode:NORMAL (0)
+Recovery master:0
+

+ +The important parts are in bold. This tells us that all 4 nodes are in a healthy state.
+It also tells us that recovery mode is normal, which means that the cluster has finished a recovery and is running in a normal fully operational state.
+Recovery state will briefly change to "RECOVERY" when there ahs been a node failure or something is wrong with the cluster.
+If the cluster remains in RECOVERY state for very long (many seconds) there might be something wrong with the configuration. See /var/log/log.ctdb + +

ctdb ip

+This command prints the current status of the public ip addresses and which physical node is currently serving that ip. +

+Number of nodes:4
+192.168.1.1         0
+192.168.1.2         1
+192.168.2.1         2
+192.168.2.1         3
+

+ +

ctdp ping

+this command tries to "ping" each of the CTDB daemons in the cluster. +

+response from 0 time=0.000050 sec  (13 clients)
+response from 1 time=0.000154 sec  (27 clients)
+response from 2 time=0.000114 sec  (17 clients)
+response from 3 time=0.000115 sec  (59 clients)
+

+ + + -- cgit From b925e9e6685a97f95c5069a5a02e15d2b9ce3bcb Mon Sep 17 00:00:00 2001 From: Andrew Tridgell Date: Fri, 8 Jun 2007 14:35:26 +1000 Subject: convert rest of pages to new format (This used to be ctdb commit c111fb4fdfbc657bc715337003febbd0313870d1) --- ctdb/web/testing.html | 11 ++++------- 1 file changed, 4 insertions(+), 7 deletions(-) (limited to 'ctdb/web/testing.html') diff --git a/ctdb/web/testing.html b/ctdb/web/testing.html index 10c34d8665..cf5f6a4bf4 100644 --- a/ctdb/web/testing.html +++ b/ctdb/web/testing.html @@ -1,14 +1,12 @@ -Starting and testing CTDB +CTDB - + -

Starting and testing CTDB

- -

Starting and testing CTDB

The CTDB log is in /var/log/log.ctdb so look in this file if something diud not start correctly.

Log in to all of the nodes in the cluster and start the ctdb service using @@ -91,5 +89,4 @@ response from 2 time=0.000114 sec (17 clients) response from 3 time=0.000115 sec (59 clients) - - + -- cgit From 2c5d3b0456a7a9d7a1afae74167be445aeb36181 Mon Sep 17 00:00:00 2001 From: Ronnie Sahlberg Date: Sat, 9 Jun 2007 13:17:24 +1000 Subject: fix typo (This used to be ctdb commit de2413fa7d1d544cf76a05a65ce7b68977c845c6) --- ctdb/web/testing.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'ctdb/web/testing.html') diff --git a/ctdb/web/testing.html b/ctdb/web/testing.html index cf5f6a4bf4..8c7eb6ad55 100644 --- a/ctdb/web/testing.html +++ b/ctdb/web/testing.html @@ -80,7 +80,7 @@ Number of nodes:4 192.168.2.1 3 -

ctdp ping

ctdb ping

this command tries to "ping" each of the CTDB daemons in the cluster.

 response from 0 time=0.000050 sec  (13 clients)
-- 
cgit 


From 1bf776bb52d66b9243b6948ddb5930351663ea4b Mon Sep 17 00:00:00 2001
From: Andrew Tridgell 
Date: Tue, 12 Jun 2007 12:27:45 +1000
Subject: minor doc updates (This used to be ctdb commit
 20c824dbce877575c423cb08943c5b9ff6d0c4a1)

---
 ctdb/web/testing.html | 60 +++++++++++++++++++++++++++++++++++----------------
 1 file changed, 42 insertions(+), 18 deletions(-)

(limited to 'ctdb/web/testing.html')

diff --git a/ctdb/web/testing.html b/ctdb/web/testing.html
index 8c7eb6ad55..a766a6f9b5 100644
--- a/ctdb/web/testing.html
+++ b/ctdb/web/testing.html
@@ -7,26 +7,33 @@
 
 Starting and testing CTDB
 
-The CTDB log is in /var/log/log.ctdb so look in this file if something diud not start correctly.


+The CTDB log is in /var/log/log.ctdb so look in this file if something
+did not start correctly.
 
-Log in to all of the nodes in the cluster and start the ctdb service using
+You can ensure that ctdb is running on all nodes using
 
-  service ctdb start
+  onnode all service ctdb start
 
 Verify that the CTDB daemon started properly. There should normally be at least 2 processes started for CTDB, one for the main daemon and one for the recovery daemon.
 -  pidof ctdbd
+  onnode all pidof ctdbd
 
 
-Once all CTDB nodes have started, verify that they are correctly talking to eachothers.

-There should be one TCP connection from the private ip address on each node to TCP port 9001 on each of the other nodes in the cluster.
+Once all CTDB nodes have started, verify that they are correctly
+talking to each other.
+
+There should be one TCP connection from the private ip address on each
+node to TCP port 9001 on each of the other nodes in the cluster.
 
-  netstat -a -n | grep 9001
+  onnode all netstat -tn | grep 9001
 
 
 
 Automatically restarting CTDB
-If you wish to cope with software faults in ctdb, or want ctdb to automatically restart when an administration kills it, then you may wish to add a cron entry for root like this:
+
+If you wish to cope with software faults in ctdb, or want ctdb to
+automatically restart when an administration kills it, then you may
+wish to add a cron entry for root like this:
 
   * * * * * /etc/init.d/ctdb cron > /dev/null 2>&1
@@ -39,7 +46,9 @@ Once your cluster is up and running, you may wish to know how to test that it is
 
 The ctdb tool
 
-The ctdb package comes with a utility called ctdb that can be used to view the behaviour of the ctdb cluster.

+The ctdb package comes with a utility called ctdb that can be used to
+view the behaviour of the ctdb cluster.
+
 If you run it with no options it will provide some terse usage information. The most commonly used commands are:
 
  ctdb status
@@ -48,7 +57,9 @@ If you run it with no options it will provide some terse usage information. The
 
 
 ctdb status
-The status command provides basic information about the cluster and the status of the nodes. when you run it you will get some output like :
+
+The status command provides basic information about the cluster and the status of the nodes. when you run it you will get some output like:
+
  Number of nodes:4
 vnn:0 10.1.1.1       OK (THIS NODE)
@@ -65,13 +76,24 @@ hash:3 lmaster:3
 Recovery master:0
 

 
-The important parts are in bold. This tells us that all 4 nodes are in a healthy state.

-It also tells us that recovery mode is normal, which means that the cluster has finished a recovery and is running in a normal fully operational state.

-Recovery state will briefly change to "RECOVERY" when there ahs been a node failure or something is wrong with the cluster.

-If the cluster remains in RECOVERY state for very long (many seconds) there might be something wrong with the configuration. See /var/log/log.ctdb
+The important parts are in bold. This tells us that all 4 nodes are in
+a healthy state.
+
+It also tells us that recovery mode is normal, which means that the
+cluster has finished a recovery and is running in a normal fully
+operational state.

+
+Recovery state will briefly change to "RECOVERY" when there ahs been a
+node failure or something is wrong with the cluster.

+
+If the cluster remains in RECOVERY state for very long (many seconds)
+there might be something wrong with the configuration. See
+/var/log/log.ctdb.
 
 
ctdb ip
+
 This command prints the current status of the public ip addresses and which physical node is currently serving that ip.
+
  Number of nodes:4
 192.168.1.1         0
@@ -83,10 +105,12 @@ Number of nodes:4
 ctdb ping
 this command tries to "ping" each of the CTDB daemons in the cluster.
 -response from 0 time=0.000050 sec  (13 clients)
-response from 1 time=0.000154 sec  (27 clients)
-response from 2 time=0.000114 sec  (17 clients)
-response from 3 time=0.000115 sec  (59 clients)
+  ctdb ping -n all
+
+  response from 0 time=0.000050 sec  (13 clients)
+  response from 1 time=0.000154 sec  (27 clients)
+  response from 2 time=0.000114 sec  (17 clients)
+  response from 3 time=0.000115 sec  (59 clients)
 
 
 
-- 
cgit 


From 10fc2684cc4f9b61477571a60f495e9f91cc07af Mon Sep 17 00:00:00 2001
From: Andrew Tridgell 
Date: Tue, 12 Jun 2007 13:04:52 +1000
Subject: make the web site pass the w3c validator (This used to be ctdb commit
 08aa5455f6cfcca2877c8da948cf1900fd09c9da)

---
 ctdb/web/testing.html | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

(limited to 'ctdb/web/testing.html')

diff --git a/ctdb/web/testing.html b/ctdb/web/testing.html
index a766a6f9b5..40a7f2f0ff 100644
--- a/ctdb/web/testing.html
+++ b/ctdb/web/testing.html
@@ -1,8 +1,6 @@
 
 
-
-CTDB
-
+
 
 
 Starting and testing CTDB
-- 
cgit 


From 4911a82791deb2f39805865a60e19139ac8af04b Mon Sep 17 00:00:00 2001
From: Andrew Tridgell 
Date: Tue, 12 Jun 2007 14:43:26 +1000
Subject: move all the headers into header.html (This used to be ctdb commit
 1da7a171a54b3561b76a8dfc0e362bef3c04f189)

---
 ctdb/web/testing.html | 2 --
 1 file changed, 2 deletions(-)

(limited to 'ctdb/web/testing.html')

diff --git a/ctdb/web/testing.html b/ctdb/web/testing.html
index 40a7f2f0ff..130b9bbb94 100644
--- a/ctdb/web/testing.html
+++ b/ctdb/web/testing.html
@@ -1,5 +1,3 @@
-
-
 
 
 
-- 
cgit 


From e1f774a95b2887b19376539354654c31667c0c98 Mon Sep 17 00:00:00 2001
From: Ronnie Sahlberg 
Date: Fri, 6 Jul 2007 15:29:03 +1000
Subject: use the official iana number for ctdb and not 9001

(This used to be ctdb commit f72aeb5eadb0bda97d882b5a27562bfa1bb5f5a2)
---
 ctdb/web/testing.html | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

(limited to 'ctdb/web/testing.html')

diff --git a/ctdb/web/testing.html b/ctdb/web/testing.html
index 130b9bbb94..d0d39a35f8 100644
--- a/ctdb/web/testing.html
+++ b/ctdb/web/testing.html
@@ -19,9 +19,9 @@ Once all CTDB nodes have started, verify that they are correctly
 talking to each other.
 
 There should be one TCP connection from the private ip address on each
-node to TCP port 9001 on each of the other nodes in the cluster.
+node to TCP port 4379 on each of the other nodes in the cluster.
 
-  onnode all netstat -tn | grep 9001
+  onnode all netstat -tn | grep 4379
 
 
 
-- 
cgit