Консул Агент: Пропуск самостоятельной проверки соединения, так как кластер слишком мал - PullRequest
0 голосов
/ 21 ноября 2018

Я новичок в Консуле и пытаюсь запустить агента Консула в режиме разработки с помощью следующей команды:

consul agent -dev

Консул продолжает пытаться выполнить проверку самостоятельного соединенияно жалуется на небольшой кластер.Я использую последнюю версию consul v1.4.0 для Windows 10. Есть идеи, в чем проблема, поскольку я не могу найти ничего подобного?

Вот журналы, когда агент запускается:

`

     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`
Добро пожаловать на сайт PullRequest, где вы можете задавать вопросы и получать ответы от других членов сообщества.
...