Consul Agent: Skipping self join check since the cluster is too small
0
I am new using Consul and I am trying to start a Consul agent in dev mode using the following command:
consul agent -dev
Consul keeps on trying to do a self join check but complains about a small cluster. Im using the latest version of consul v1.4.0 on Windows 10. Any idea what the issue is since i couldn't find anything similar?
Here are the logs when the agent starts:
`
Version:'v1.4.0'
Node ID: '19e47b51-b90a-54ba-d2c7-af9b887bc3e6'
Node name: 'UNL-W-D-0060'
Datacenter: 'dc1' (Segment: '<all>')
Server: true (Bootstrap: false)
Client Addr: [127.0.0.1] (HTTP: 8500, HTTPS: -1, gRPC: 8502, DNS: 8600)
Cluster Addr: 127.0.0.1 (LAN: 8301, WAN: 8302)
Encrypt: Gossip: false, TLS-Outgoing: false, TLS-Incoming: false
2018/11/19 10:54:10 [DEBUG] agent: Using random ID "19e47b51-b90a-54ba-d2c7-af9b887bc3e6" as node ID
2018/11/19 10:54:10 [INFO] raft: Initial configuration (index=1): [{Suffrage:Voter ID:19e47b51-b90a-54ba-d2c7-af9b887bc3e6 Address:127.0.0.1:8300}]
2018/11/19 10:54:10 [INFO] raft: Node at 127.0.0.1:8300 [Follower] entering Follower state (Leader: "")
2018/11/19 10:54:10 [INFO] serf: EventMemberJoin: UNL-W-D-0060.dc1 127.0.0.1
2018/11/19 10:54:10 [INFO] serf: EventMemberJoin: UNL-W-D-0060 127.0.0.1
2018/11/19 10:54:10 [INFO] consul: Adding LAN server UNL-W-D-0060 (Addr: tcp/127.0.0.1:8300) (DC: dc1)
2018/11/19 10:54:10 [INFO] consul: Handled member-join event for server "UNL-W-D-0060.dc1" in area "wan"
2018/11/19 10:54:10 [DEBUG] agent/proxy: managed Connect proxy manager started
2018/11/19 10:54:10 [INFO] agent: Started DNS server 127.0.0.1:8600 (udp)
2018/11/19 10:54:10 [INFO] agent: Started DNS server 127.0.0.1:8600 (tcp)
2018/11/19 10:54:10 [INFO] agent: Started HTTP server on 127.0.0.1:8500 (tcp)
2018/11/19 10:54:10 [INFO] agent: started state syncer
2018/11/19 10:54:10 [INFO] agent: Started gRPC server on 127.0.0.1:8502 (tcp)
2018/11/19 10:54:10 [WARN] raft: Heartbeat timeout from "" reached, starting election
2018/11/19 10:54:10 [INFO] raft: Node at 127.0.0.1:8300 [Candidate] entering Candidate state in term 2
2018/11/19 10:54:10 [DEBUG] raft: Votes needed: 1
2018/11/19 10:54:10 [DEBUG] raft: Vote granted from 19e47b51-b90a-54ba-d2c7-af9b887bc3e6 in term 2. Tally: 1
2018/11/19 10:54:10 [INFO] raft: Election won. Tally: 1
2018/11/19 10:54:10 [INFO] raft: Node at 127.0.0.1:8300 [Leader] entering Leader state
2018/11/19 10:54:10 [INFO] consul: cluster leadership acquired
2018/11/19 10:54:10 [INFO] consul: New leader elected: UNL-W-D-0060
2018/11/19 10:54:10 [INFO] connect: initialized primary datacenter CA with provider "consul"
2018/11/19 10:54:10 [DEBUG] consul: Skipping self join check for "UNL-W-D-0060" since the cluster is too small
2018/11/19 10:54:10 [INFO] consul: member 'UNL-W-D-0060' joined, marking health alive
2018/11/19 10:54:11 [DEBUG] agent: Skipping remote check "serfHealth" since it is managed automatically
2018/11/19 10:54:11 [INFO] agent: Synced node info
2018/11/19 10:54:11 [DEBUG] agent: Node info in sync
2018/11/19 10:54:11 [DEBUG] agent: Skipping remote check "serfHealth" since it is managed automatically`
docker self-join agent consul
asked Nov 21 '18 at 8:32
Constantinos Evangelou
11
add a comment |
0
I am new using Consul and I am trying to start a Consul agent in dev mode using the following command:
consul agent -dev
Consul keeps on trying to do a self join check but complains about a small cluster. Im using the latest version of consul v1.4.0 on Windows 10. Any idea what the issue is since i couldn't find anything similar?
Here are the logs when the agent starts:
`
Version:'v1.4.0'
Node ID: '19e47b51-b90a-54ba-d2c7-af9b887bc3e6'
Node name: 'UNL-W-D-0060'
Datacenter: 'dc1' (Segment: '<all>')
Server: true (Bootstrap: false)
Client Addr: [127.0.0.1] (HTTP: 8500, HTTPS: -1, gRPC: 8502, DNS: 8600)
Cluster Addr: 127.0.0.1 (LAN: 8301, WAN: 8302)
Encrypt: Gossip: false, TLS-Outgoing: false, TLS-Incoming: false
2018/11/19 10:54:10 [DEBUG] agent: Using random ID "19e47b51-b90a-54ba-d2c7-af9b887bc3e6" as node ID
2018/11/19 10:54:10 [INFO] raft: Initial configuration (index=1): [{Suffrage:Voter ID:19e47b51-b90a-54ba-d2c7-af9b887bc3e6 Address:127.0.0.1:8300}]
2018/11/19 10:54:10 [INFO] raft: Node at 127.0.0.1:8300 [Follower] entering Follower state (Leader: "")
2018/11/19 10:54:10 [INFO] serf: EventMemberJoin: UNL-W-D-0060.dc1 127.0.0.1
2018/11/19 10:54:10 [INFO] serf: EventMemberJoin: UNL-W-D-0060 127.0.0.1
2018/11/19 10:54:10 [INFO] consul: Adding LAN server UNL-W-D-0060 (Addr: tcp/127.0.0.1:8300) (DC: dc1)
2018/11/19 10:54:10 [INFO] consul: Handled member-join event for server "UNL-W-D-0060.dc1" in area "wan"
2018/11/19 10:54:10 [DEBUG] agent/proxy: managed Connect proxy manager started
2018/11/19 10:54:10 [INFO] agent: Started DNS server 127.0.0.1:8600 (udp)
2018/11/19 10:54:10 [INFO] agent: Started DNS server 127.0.0.1:8600 (tcp)
2018/11/19 10:54:10 [INFO] agent: Started HTTP server on 127.0.0.1:8500 (tcp)
2018/11/19 10:54:10 [INFO] agent: started state syncer
2018/11/19 10:54:10 [INFO] agent: Started gRPC server on 127.0.0.1:8502 (tcp)
2018/11/19 10:54:10 [WARN] raft: Heartbeat timeout from "" reached, starting election
2018/11/19 10:54:10 [INFO] raft: Node at 127.0.0.1:8300 [Candidate] entering Candidate state in term 2
2018/11/19 10:54:10 [DEBUG] raft: Votes needed: 1
2018/11/19 10:54:10 [DEBUG] raft: Vote granted from 19e47b51-b90a-54ba-d2c7-af9b887bc3e6 in term 2. Tally: 1
2018/11/19 10:54:10 [INFO] raft: Election won. Tally: 1
2018/11/19 10:54:10 [INFO] raft: Node at 127.0.0.1:8300 [Leader] entering Leader state
2018/11/19 10:54:10 [INFO] consul: cluster leadership acquired
2018/11/19 10:54:10 [INFO] consul: New leader elected: UNL-W-D-0060
2018/11/19 10:54:10 [INFO] connect: initialized primary datacenter CA with provider "consul"
2018/11/19 10:54:10 [DEBUG] consul: Skipping self join check for "UNL-W-D-0060" since the cluster is too small
2018/11/19 10:54:10 [INFO] consul: member 'UNL-W-D-0060' joined, marking health alive
2018/11/19 10:54:11 [DEBUG] agent: Skipping remote check "serfHealth" since it is managed automatically
2018/11/19 10:54:11 [INFO] agent: Synced node info
2018/11/19 10:54:11 [DEBUG] agent: Node info in sync
2018/11/19 10:54:11 [DEBUG] agent: Skipping remote check "serfHealth" since it is managed automatically`
docker self-join agent consul
asked Nov 21 '18 at 8:32
Constantinos Evangelou
11
add a comment |
0
0
0
I am new using Consul and I am trying to start a Consul agent in dev mode using the following command:
consul agent -dev
Consul keeps on trying to do a self join check but complains about a small cluster. Im using the latest version of consul v1.4.0 on Windows 10. Any idea what the issue is since i couldn't find anything similar?
Here are the logs when the agent starts:
`
Version:'v1.4.0'
Node ID: '19e47b51-b90a-54ba-d2c7-af9b887bc3e6'
Node name: 'UNL-W-D-0060'
Datacenter: 'dc1' (Segment: '<all>')
Server: true (Bootstrap: false)
Client Addr: [127.0.0.1] (HTTP: 8500, HTTPS: -1, gRPC: 8502, DNS: 8600)
Cluster Addr: 127.0.0.1 (LAN: 8301, WAN: 8302)
Encrypt: Gossip: false, TLS-Outgoing: false, TLS-Incoming: false
2018/11/19 10:54:10 [DEBUG] agent: Using random ID "19e47b51-b90a-54ba-d2c7-af9b887bc3e6" as node ID
2018/11/19 10:54:10 [INFO] raft: Initial configuration (index=1): [{Suffrage:Voter ID:19e47b51-b90a-54ba-d2c7-af9b887bc3e6 Address:127.0.0.1:8300}]
2018/11/19 10:54:10 [INFO] raft: Node at 127.0.0.1:8300 [Follower] entering Follower state (Leader: "")
2018/11/19 10:54:10 [INFO] serf: EventMemberJoin: UNL-W-D-0060.dc1 127.0.0.1
2018/11/19 10:54:10 [INFO] serf: EventMemberJoin: UNL-W-D-0060 127.0.0.1
2018/11/19 10:54:10 [INFO] consul: Adding LAN server UNL-W-D-0060 (Addr: tcp/127.0.0.1:8300) (DC: dc1)
2018/11/19 10:54:10 [INFO] consul: Handled member-join event for server "UNL-W-D-0060.dc1" in area "wan"
2018/11/19 10:54:10 [DEBUG] agent/proxy: managed Connect proxy manager started
2018/11/19 10:54:10 [INFO] agent: Started DNS server 127.0.0.1:8600 (udp)
2018/11/19 10:54:10 [INFO] agent: Started DNS server 127.0.0.1:8600 (tcp)
2018/11/19 10:54:10 [INFO] agent: Started HTTP server on 127.0.0.1:8500 (tcp)
2018/11/19 10:54:10 [INFO] agent: started state syncer
2018/11/19 10:54:10 [INFO] agent: Started gRPC server on 127.0.0.1:8502 (tcp)
2018/11/19 10:54:10 [WARN] raft: Heartbeat timeout from "" reached, starting election
2018/11/19 10:54:10 [INFO] raft: Node at 127.0.0.1:8300 [Candidate] entering Candidate state in term 2
2018/11/19 10:54:10 [DEBUG] raft: Votes needed: 1
2018/11/19 10:54:10 [DEBUG] raft: Vote granted from 19e47b51-b90a-54ba-d2c7-af9b887bc3e6 in term 2. Tally: 1
2018/11/19 10:54:10 [INFO] raft: Election won. Tally: 1
2018/11/19 10:54:10 [INFO] raft: Node at 127.0.0.1:8300 [Leader] entering Leader state
2018/11/19 10:54:10 [INFO] consul: cluster leadership acquired
2018/11/19 10:54:10 [INFO] consul: New leader elected: UNL-W-D-0060
2018/11/19 10:54:10 [INFO] connect: initialized primary datacenter CA with provider "consul"
2018/11/19 10:54:10 [DEBUG] consul: Skipping self join check for "UNL-W-D-0060" since the cluster is too small
2018/11/19 10:54:10 [INFO] consul: member 'UNL-W-D-0060' joined, marking health alive
2018/11/19 10:54:11 [DEBUG] agent: Skipping remote check "serfHealth" since it is managed automatically
2018/11/19 10:54:11 [INFO] agent: Synced node info
2018/11/19 10:54:11 [DEBUG] agent: Node info in sync
2018/11/19 10:54:11 [DEBUG] agent: Skipping remote check "serfHealth" since it is managed automatically`
docker self-join agent consul
asked Nov 21 '18 at 8:32
Constantinos Evangelou
11
I am new using Consul and I am trying to start a Consul agent in dev mode using the following command:
consul agent -dev
Consul keeps on trying to do a self join check but complains about a small cluster. Im using the latest version of consul v1.4.0 on Windows 10. Any idea what the issue is since i couldn't find anything similar?
Here are the logs when the agent starts:
`
Version:'v1.4.0'
Node ID: '19e47b51-b90a-54ba-d2c7-af9b887bc3e6'
Node name: 'UNL-W-D-0060'
Datacenter: 'dc1' (Segment: '<all>')
Server: true (Bootstrap: false)
Client Addr: [127.0.0.1] (HTTP: 8500, HTTPS: -1, gRPC: 8502, DNS: 8600)
Cluster Addr: 127.0.0.1 (LAN: 8301, WAN: 8302)
Encrypt: Gossip: false, TLS-Outgoing: false, TLS-Incoming: false
2018/11/19 10:54:10 [DEBUG] agent: Using random ID "19e47b51-b90a-54ba-d2c7-af9b887bc3e6" as node ID
2018/11/19 10:54:10 [INFO] raft: Initial configuration (index=1): [{Suffrage:Voter ID:19e47b51-b90a-54ba-d2c7-af9b887bc3e6 Address:127.0.0.1:8300}]
2018/11/19 10:54:10 [INFO] raft: Node at 127.0.0.1:8300 [Follower] entering Follower state (Leader: "")
2018/11/19 10:54:10 [INFO] serf: EventMemberJoin: UNL-W-D-0060.dc1 127.0.0.1
2018/11/19 10:54:10 [INFO] serf: EventMemberJoin: UNL-W-D-0060 127.0.0.1
2018/11/19 10:54:10 [INFO] consul: Adding LAN server UNL-W-D-0060 (Addr: tcp/127.0.0.1:8300) (DC: dc1)
2018/11/19 10:54:10 [INFO] consul: Handled member-join event for server "UNL-W-D-0060.dc1" in area "wan"
2018/11/19 10:54:10 [DEBUG] agent/proxy: managed Connect proxy manager started
2018/11/19 10:54:10 [INFO] agent: Started DNS server 127.0.0.1:8600 (udp)
2018/11/19 10:54:10 [INFO] agent: Started DNS server 127.0.0.1:8600 (tcp)
2018/11/19 10:54:10 [INFO] agent: Started HTTP server on 127.0.0.1:8500 (tcp)
2018/11/19 10:54:10 [INFO] agent: started state syncer
2018/11/19 10:54:10 [INFO] agent: Started gRPC server on 127.0.0.1:8502 (tcp)
2018/11/19 10:54:10 [WARN] raft: Heartbeat timeout from "" reached, starting election
2018/11/19 10:54:10 [INFO] raft: Node at 127.0.0.1:8300 [Candidate] entering Candidate state in term 2
2018/11/19 10:54:10 [DEBUG] raft: Votes needed: 1
2018/11/19 10:54:10 [DEBUG] raft: Vote granted from 19e47b51-b90a-54ba-d2c7-af9b887bc3e6 in term 2. Tally: 1
2018/11/19 10:54:10 [INFO] raft: Election won. Tally: 1
2018/11/19 10:54:10 [INFO] raft: Node at 127.0.0.1:8300 [Leader] entering Leader state
2018/11/19 10:54:10 [INFO] consul: cluster leadership acquired
2018/11/19 10:54:10 [INFO] consul: New leader elected: UNL-W-D-0060
2018/11/19 10:54:10 [INFO] connect: initialized primary datacenter CA with provider "consul"
2018/11/19 10:54:10 [DEBUG] consul: Skipping self join check for "UNL-W-D-0060" since the cluster is too small
2018/11/19 10:54:10 [INFO] consul: member 'UNL-W-D-0060' joined, marking health alive
2018/11/19 10:54:11 [DEBUG] agent: Skipping remote check "serfHealth" since it is managed automatically
2018/11/19 10:54:11 [INFO] agent: Synced node info
2018/11/19 10:54:11 [DEBUG] agent: Node info in sync
2018/11/19 10:54:11 [DEBUG] agent: Skipping remote check "serfHealth" since it is managed automatically`
docker self-join agent consul
docker self-join agent consul
asked Nov 21 '18 at 8:32
Constantinos Evangelou
11
asked Nov 21 '18 at 8:32
Constantinos Evangelou
11
asked Nov 21 '18 at 8:32
Constantinos Evangelou
11
asked Nov 21 '18 at 8:32
Constantinos Evangelou
11
asked Nov 21 '18 at 8:32
Constantinos Evangelou
11
11
add a comment |
add a comment |
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
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53407983%2fconsul-agent-skipping-self-join-check-since-the-cluster-is-too-small%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
active
oldest
votes
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53407983%2fconsul-agent-skipping-self-join-check-since-the-cluster-is-too-small%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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
