CouchBase Issues / Errors - Over coming them..

ISSUE / ERROR # 1
Attention - Join completion call failed. Got HTTP status 500 from REST call post to http://hostname.domain.com:8091/completeJoin. Body was: "[\"Unexpected server error, request logged.\"]"

AIM : Adding Nodes to a Cluster
ERROR: Attention - Join completion call failed. Got HTTP status 500 from REST call post to http://hostname.domain.com:8091/completeJoin. Body was: "[\"Unexpected server error, request logged.\"]"
REASON (RCA): When you add a Node with already existing bucket to a cluster, You will face this issue. There can be other factors, but in my case, i found this as the issue.
How to over come this ? Follow the below steps: But please consult your team before that as some commands below are ab
solutely destructive if you are not paying attention.

1. stop the couchbase first
service couchbase status
service couchbase stop

2. Check that the ports are not being used by anybody, if they are, trace the program using it and kill it.
netstat -a |grep 8091
netstat -a |grep 8092
netstat -a |grep 11211
netstat -a |grep 11210

3. Move/Remove the data directories - your choice
cd /data/couchbase
mv data data.OLD
mv index index.OLD

4. Recreate them
mkdir data index

5. Assign them to the couchbase user

chown couchbase:couchbase data index

6. Once again check on the ports
netstat -a |grep 8091
netstat -a |grep 8092
netstat -a |grep 11211
netstat -a |grep 11210
Usually 11210 will be engaged by some program, hence
wait until 11210 disappears

7. If all good, go ahead and start the couchbase
service couchbase status
service couchbase start

8. Now you can go to the master node and add it to the Server Groups..


ISSUE / ERROR # 2 - Couchbase Server alert: auto_failover_node

Scenario 1a:
Port server memcached on node 'babysitter_of_ns_1@127.0.0.1' exited with status 0.
If the exit status is zero, mostly due to one of your DBAs is working not that instance and might have brought down the couch base gracefully.
Just Start the couch base and add it back in the server list and you should be good to go.

Scenario 1b:
Port server memcached on node 'babysitter_of_ns_1@127.0.0.1' exited with status 0.
There can be many reasons why a couch base server will be failed over and the exit status can be .
- Because of the network glitches and if you have the Auto-Failover time out set to a too low number such as 30, couch base server manager may think that the box is down when it is not reachable.

Scenario 2:
Port server moxi on node 'babysitter_of_ns_1@127.0.0.1' exited with status134
Explanation will be provided soon..