-
Notifications
You must be signed in to change notification settings - Fork 13
Consul doesn't start #5
Copy link
Copy link
Open
Description
Hi,
I have downloaded the code and followed the instructions in the README. Changed few binaries to reflect the latest version and changed the config job to comply with the newer version. When I run vagrant up its all success and I can browse the nomad ui which listed the consul job with status starting. Logged into vagrant box and ran nomad status
ID Type Priority Status Submit Date
consul system 50 running 01/09/18 14:07:30 UTC
and looked at the nomad log only to find out that consul is not starting on port 8500. Please see the log below.
` Loaded configuration from /vagrant/nomad/config/nomad.hcl
==> Starting Nomad agent...
==> Nomad agent configuration:
Client: true
Log Level: DEBUG
Region: global (DC: dc1)
Server: true
Version: 0.7.1
==> Nomad agent started! Log data will stream in below:
2018/01/09 11:51:24 [INFO] raft: Initial configuration (index=1): [{Suffrage:Voter ID:192.168.10.10:4647 Address:192.168.10.10:4647}]
2018/01/09 11:51:24 [INFO] raft: Node at 192.168.10.10:4647 [Follower] entering Follower state (Leader: "")
2018/01/09 11:51:24 [INFO] serf: EventMemberJoin: vagrant-ubuntu-trusty-64.global 192.168.10.10
2018/01/09 11:51:24.063061 [INFO] nomad: starting 2 scheduling worker(s) for [service batch system _core]
2018/01/09 11:51:24.063383 [INFO] nomad: adding server vagrant-ubuntu-trusty-64.global (Addr: 192.168.10.10:4647) (DC: dc1)
2018/01/09 11:51:24.064736 [WARN] consul.sync: failed to update services in Consul: error querying Consul services: Get http://192.168.10.10:8500/v1/agent/services: dial tcp 192.168.10.10:8500: getsockopt: connection refused
2018/01/09 11:51:24.064882 [INFO] client: using state directory /tmp/NomadClient338545135
2018/01/09 11:51:24.065352 [DEBUG] server.nomad: lost contact with Nomad quorum, falling back to Consul for server list
2018/01/09 11:51:24.065587 [ERR] consul: error looking up Nomad servers: server.nomad: unable to query Consul datacenters: Get http://192.168.10.10:8500/v1/catalog/datacenters: dial tcp 192.168.10.10:8500: getsockopt: connection refused
2018/01/09 11:51:24.066907 [INFO] client: using alloc directory /tmp/NomadClient800136322`
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels