Closed jvabob closed 7 years ago
Can you confirm that DNS works correctly on both nodes? For instance, on couchdb-2-1
are you able to ping couchdb-2-2.qa.aws.net
and vice-versa?
Can you provide the specific commands you are using to connect the nodes? Are you using the /_cluster_setup
endpoint with curl
?
yes dns works fine and I can telnet from one system to the other on the ports 5984, 5986, 4369 using the dns names
I used the cluster setup wizard on couchdb-2-1 to add couchdb-2-2 as a node
I used the fully qualified domain name when I added the node and in the -name attribute in the vm.args file
Please share your full etc/
directory contents from both boxes (with any [admins]
sections removed!) for us to look at this further.
please reopen with requested info
have 2 couchdb 2.0 systems setup couchdb-2-1 and couchdb-2-2
have firewall configured to allow access between the systems on 5984, 5986, 4369, and 9100-9200
I can telnet between the boxes to 5984, 5986, 4369
I can connect the 2 servers with erlang as described in the Clustering setup firewall guide and ping between them.
However, when I add couchdb-2-2 as a node on couchdb-2-1 I never see couchdb-2-1 as a node on couchdb-2-2.
I have set the name in vm.args like this
sys.config looks like this
I am seeing these entries repeating on couchdb-2-1 in couchdb.stderr
seems related but I don't know where to go from here.