Couchbase Cluster creation issue












0















I am have installed Couchbase on Docker using docker-compose file.



version: '2'
services:
couchbase-server:
container_name: project-couchbase
image: couchbase/server
ports:
- 4369:4369
- 8091:8091
- 8092:8092
- 8093:8093
- 8094:8094
- 11210:11210
- 11211:11211
volumes:
- $HOME/couchbasesql:/var/lib/couchbase/data


Installation went fine but while creating cluster when i give my machine ip, I am getting following error



enter image description here



I have used all solution on google but still i am stuck here, it is taking 127.0.0.1 but not my machine ip which is needed for Couchbase clustering.
Can somebody help me on this ?










share|improve this question

























  • If this is your first cluster setup then you should be able to use loopback ip 127.0.0.1

    – Nuwan Attanayake
    Nov 23 '18 at 7:40











  • @Nuwan,ok but when other node is joining my cluster how would he achieve this because couchbase asks for cluster ip there, which ip he should provide over there ?

    – lokendra lovely
    Nov 23 '18 at 8:14











  • Other nodes should be able to communicate with this node by its Docker assigned IP(172.31.195.103)

    – Nuwan Attanayake
    Nov 23 '18 at 8:16











  • If i give docker assigned ip, i am getting Attention: Failed to reach erlang port mapper. Timeout connecting to "72.31.195.103" on port "4369".

    – lokendra lovely
    Nov 23 '18 at 8:27






  • 1





    You should try direct couchbase docker container without docker-composer.just for test weather you getting the same behavior.I tried and works as expected. docker run -d --name db -p 8091-8094:8091-8094 -p 11210:11210 couchbase . more details here hub.docker.com/r/couchbase/server

    – Nuwan Attanayake
    Nov 23 '18 at 9:17
















0















I am have installed Couchbase on Docker using docker-compose file.



version: '2'
services:
couchbase-server:
container_name: project-couchbase
image: couchbase/server
ports:
- 4369:4369
- 8091:8091
- 8092:8092
- 8093:8093
- 8094:8094
- 11210:11210
- 11211:11211
volumes:
- $HOME/couchbasesql:/var/lib/couchbase/data


Installation went fine but while creating cluster when i give my machine ip, I am getting following error



enter image description here



I have used all solution on google but still i am stuck here, it is taking 127.0.0.1 but not my machine ip which is needed for Couchbase clustering.
Can somebody help me on this ?










share|improve this question

























  • If this is your first cluster setup then you should be able to use loopback ip 127.0.0.1

    – Nuwan Attanayake
    Nov 23 '18 at 7:40











  • @Nuwan,ok but when other node is joining my cluster how would he achieve this because couchbase asks for cluster ip there, which ip he should provide over there ?

    – lokendra lovely
    Nov 23 '18 at 8:14











  • Other nodes should be able to communicate with this node by its Docker assigned IP(172.31.195.103)

    – Nuwan Attanayake
    Nov 23 '18 at 8:16











  • If i give docker assigned ip, i am getting Attention: Failed to reach erlang port mapper. Timeout connecting to "72.31.195.103" on port "4369".

    – lokendra lovely
    Nov 23 '18 at 8:27






  • 1





    You should try direct couchbase docker container without docker-composer.just for test weather you getting the same behavior.I tried and works as expected. docker run -d --name db -p 8091-8094:8091-8094 -p 11210:11210 couchbase . more details here hub.docker.com/r/couchbase/server

    – Nuwan Attanayake
    Nov 23 '18 at 9:17














0












0








0








I am have installed Couchbase on Docker using docker-compose file.



version: '2'
services:
couchbase-server:
container_name: project-couchbase
image: couchbase/server
ports:
- 4369:4369
- 8091:8091
- 8092:8092
- 8093:8093
- 8094:8094
- 11210:11210
- 11211:11211
volumes:
- $HOME/couchbasesql:/var/lib/couchbase/data


Installation went fine but while creating cluster when i give my machine ip, I am getting following error



enter image description here



I have used all solution on google but still i am stuck here, it is taking 127.0.0.1 but not my machine ip which is needed for Couchbase clustering.
Can somebody help me on this ?










share|improve this question
















I am have installed Couchbase on Docker using docker-compose file.



version: '2'
services:
couchbase-server:
container_name: project-couchbase
image: couchbase/server
ports:
- 4369:4369
- 8091:8091
- 8092:8092
- 8093:8093
- 8094:8094
- 11210:11210
- 11211:11211
volumes:
- $HOME/couchbasesql:/var/lib/couchbase/data


Installation went fine but while creating cluster when i give my machine ip, I am getting following error



enter image description here



I have used all solution on google but still i am stuck here, it is taking 127.0.0.1 but not my machine ip which is needed for Couchbase clustering.
Can somebody help me on this ?







couchbase






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 23 '18 at 8:41







lokendra lovely

















asked Nov 23 '18 at 7:32









lokendra lovelylokendra lovely

14111




14111













  • If this is your first cluster setup then you should be able to use loopback ip 127.0.0.1

    – Nuwan Attanayake
    Nov 23 '18 at 7:40











  • @Nuwan,ok but when other node is joining my cluster how would he achieve this because couchbase asks for cluster ip there, which ip he should provide over there ?

    – lokendra lovely
    Nov 23 '18 at 8:14











  • Other nodes should be able to communicate with this node by its Docker assigned IP(172.31.195.103)

    – Nuwan Attanayake
    Nov 23 '18 at 8:16











  • If i give docker assigned ip, i am getting Attention: Failed to reach erlang port mapper. Timeout connecting to "72.31.195.103" on port "4369".

    – lokendra lovely
    Nov 23 '18 at 8:27






  • 1





    You should try direct couchbase docker container without docker-composer.just for test weather you getting the same behavior.I tried and works as expected. docker run -d --name db -p 8091-8094:8091-8094 -p 11210:11210 couchbase . more details here hub.docker.com/r/couchbase/server

    – Nuwan Attanayake
    Nov 23 '18 at 9:17



















  • If this is your first cluster setup then you should be able to use loopback ip 127.0.0.1

    – Nuwan Attanayake
    Nov 23 '18 at 7:40











  • @Nuwan,ok but when other node is joining my cluster how would he achieve this because couchbase asks for cluster ip there, which ip he should provide over there ?

    – lokendra lovely
    Nov 23 '18 at 8:14











  • Other nodes should be able to communicate with this node by its Docker assigned IP(172.31.195.103)

    – Nuwan Attanayake
    Nov 23 '18 at 8:16











  • If i give docker assigned ip, i am getting Attention: Failed to reach erlang port mapper. Timeout connecting to "72.31.195.103" on port "4369".

    – lokendra lovely
    Nov 23 '18 at 8:27






  • 1





    You should try direct couchbase docker container without docker-composer.just for test weather you getting the same behavior.I tried and works as expected. docker run -d --name db -p 8091-8094:8091-8094 -p 11210:11210 couchbase . more details here hub.docker.com/r/couchbase/server

    – Nuwan Attanayake
    Nov 23 '18 at 9:17

















If this is your first cluster setup then you should be able to use loopback ip 127.0.0.1

– Nuwan Attanayake
Nov 23 '18 at 7:40





If this is your first cluster setup then you should be able to use loopback ip 127.0.0.1

– Nuwan Attanayake
Nov 23 '18 at 7:40













@Nuwan,ok but when other node is joining my cluster how would he achieve this because couchbase asks for cluster ip there, which ip he should provide over there ?

– lokendra lovely
Nov 23 '18 at 8:14





@Nuwan,ok but when other node is joining my cluster how would he achieve this because couchbase asks for cluster ip there, which ip he should provide over there ?

– lokendra lovely
Nov 23 '18 at 8:14













Other nodes should be able to communicate with this node by its Docker assigned IP(172.31.195.103)

– Nuwan Attanayake
Nov 23 '18 at 8:16





Other nodes should be able to communicate with this node by its Docker assigned IP(172.31.195.103)

– Nuwan Attanayake
Nov 23 '18 at 8:16













If i give docker assigned ip, i am getting Attention: Failed to reach erlang port mapper. Timeout connecting to "72.31.195.103" on port "4369".

– lokendra lovely
Nov 23 '18 at 8:27





If i give docker assigned ip, i am getting Attention: Failed to reach erlang port mapper. Timeout connecting to "72.31.195.103" on port "4369".

– lokendra lovely
Nov 23 '18 at 8:27




1




1





You should try direct couchbase docker container without docker-composer.just for test weather you getting the same behavior.I tried and works as expected. docker run -d --name db -p 8091-8094:8091-8094 -p 11210:11210 couchbase . more details here hub.docker.com/r/couchbase/server

– Nuwan Attanayake
Nov 23 '18 at 9:17





You should try direct couchbase docker container without docker-composer.just for test weather you getting the same behavior.I tried and works as expected. docker run -d --name db -p 8091-8094:8091-8094 -p 11210:11210 couchbase . more details here hub.docker.com/r/couchbase/server

– Nuwan Attanayake
Nov 23 '18 at 9:17












0






active

oldest

votes











Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53442379%2fcouchbase-cluster-creation-issue%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53442379%2fcouchbase-cluster-creation-issue%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Ottavio Pratesi

Tricia Helfer

15 giugno