From 2da6d2105513613cdbb16c665692139f1b0f379a Mon Sep 17 00:00:00 2001 From: varac Date: Thu, 30 Jan 2014 17:47:29 +0100 Subject: added stunnel section for MX and couch nodes --- docs/platform/troubleshooting.md | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) diff --git a/docs/platform/troubleshooting.md b/docs/platform/troubleshooting.md index 1d1234b..6869a8e 100644 --- a/docs/platform/troubleshooting.md +++ b/docs/platform/troubleshooting.md @@ -126,6 +126,23 @@ Design Documents curl -s --netrc-file /etc/couchdb/couchdb.netrc -X GET "http://127.0.0.1:5984/users/_design/User" +Is couchdb cluster backend accessible through stunnel ? +------------------------------------------------------- + +* Find out how many connections are set up for the couchdb cluster backend: + +
+    grep "accept = 127.0.0.1" /etc/stunnel/*
+
+ + +* Now connect to all of those local endpoints to see if they up. All these tests should return "localhost [127.0.0.1] 4000 (?) open" + +
+    nc -v 127.0.0.1 4000
+    nc -v 127.0.0.1 4001
+    ...
+
MX @@ -138,6 +155,16 @@ Places to look for errors * `/var/log/leap_mx.log` * `/var/log/syslog` (watch out for stunnel issues) +Is couchdb accessible through stunnel ? +--------------------------------------- + +* Depending on how many couch nodes you have, increase the port for every test + (see /etc/haproxy/haproxy.cfg for the server/port mapping): + + + curl -s -X GET "http://127.0.0.1:4000" + curl -s -X GET "http://127.0.0.1:4001" + ... Query leap-mx ------------- -- cgit v1.2.3