I get this error when installing and running "vault init"
Running
CentoOS 64 bit
Using the downloaded 64 bit binaries from the vault and consul sites.
HCL file:
backend "consul" {
address = "127.0.0.1:8500"
path = "vault"
}
listener "tcp" {
address = "127.0.0.1:8200"
tls_disable = 1
}
consul start up:
==> WARNING: BootstrapExpect Mode is specified as 1; this is the same as Bootstrap mode.
==> WARNING: Bootstrap mode enabled! Do not enable unless necessary
==> WARNING: It is highly recommended to set GOMAXPROCS higher than 1
==> Starting raft data migration...
==> Starting Consul agent...
==> Starting Consul agent RPC...
==> Consul agent running!
Node name: 'kozmo.*.net'
Datacenter: 'dc1'
Server: true (bootstrap: true)
Client Addr: 127.0.0.1 (HTTP: 8500, HTTPS: -1, DNS: 8600, RPC: 8400)
Cluster Addr: 192.168.3.2 (LAN: 8301, WAN: 8302)
Gossip encrypt: false, RPC-TLS: false, TLS-Incoming: false
Atlas:
==> Log data will now stream in as it occurs:
2015/11/19 10:02:47 [INFO] serf: EventMemberJoin: kozmo.***.net 192.168.3.2
2015/11/19 10:02:47 [INFO] serf: EventMemberJoin: kozmo.***.net.dc1 192.168.3.2
2015/11/19 10:02:47 [INFO] raft: Node at 192.168.3.2:8300 [Follower] entering Follower state
2015/11/19 10:02:47 [INFO] consul: adding server kozmo.***.net (Addr: 192.168.3.2:8300) (DC: dc1)
2015/11/19 10:02:47 [INFO] consul: adding server kozmo.***.net.dc1 (Addr: 192.168.3.2:8300) (DC: dc1)
2015/11/19 10:02:47 [ERR] agent: failed to sync remote state: No cluster leader
2015/11/19 10:02:49 [WARN] raft: Heartbeat timeout reached, starting election
2015/11/19 10:02:49 [INFO] raft: Node at 192.168.3.2:8300 [Candidate] entering Candidate state
2015/11/19 10:02:49 [INFO] raft: Election won. Tally: 1
2015/11/19 10:02:49 [INFO] raft: Node at 192.168.3.2:8300 [Leader] entering Leader state
2015/11/19 10:02:49 [INFO] consul: cluster leadership acquired
2015/11/19 10:02:49 [INFO] consul: New leader elected: kozmo.***.net
2015/11/19 10:02:49 [INFO] raft: Disabling EnableSingleNode (bootstrap)
then my vault start:
==> Vault server configuration:
Log Level: info
Mlock: supported: true, enabled: true
Backend: consul (HA available)
Advertise Address: http://127.0.0.1:8200
Listener 1: tcp (addr: "127.0.0.1:8200", tls: "disabled")
==> Vault server started! Log data will stream in below:
^C==> Vault shutdown triggered
[root@kozmo ~]# vault server -config=./kozmo.hcl
==> Vault server configuration:
Log Level: info
Mlock: supported: true, enabled: true
Backend: consul (HA available)
Advertise Address: http://127.0.0.1:8200
Listener 1: tcp (addr: "127.0.0.1:8200", tls: "disabled")
==> Vault server started! Log data will stream in below:
now my attempt to run vault init:
Error initializing Vault: Put /v1/sys/init: unsupported protocol scheme ""
Please let me know if you need any more information. Thanks!
[closed]
Running from a shell that didn't have this set worked:
export VAULT_ADDR='http://127.0.0.1:8200'
closed
Most helpful comment
[closed]
Running from a shell that didn't have this set worked:
export VAULT_ADDR='http://127.0.0.1:8200'