Vault: core: seal configuration missing, not initialized

Created on 29 Aug 2017  路  10Comments  路  Source: hashicorp/vault

Hi,
Can you please help I have the issue with Vault in Linux the command that I performed are locally, so when I try to connect to check the status of the vault server vault status

it display:

Code: 400. Errors:

* server is not yet initialized

Environment:

  • Vault Version: Vault v0.8.1
  • Operating System/Architecture: Ubuntu 16.04.3 LTS x86_64

Vault Config File:

$ cat vault.hcl
storage "file" {
  path = "/home/vault/data"
}

listener "tcp" {
 address = "127.0.0.1:8200"
 tls_disable = 1

Startup Log Output:

==> Vault server configuration:

                     Cgo: disabled
              Listener 1: tcp (addr: "127.0.0.1:8200", cluster address: "127.0.0.1:8201", tls: "disabled")
               Log Level: info
                   Mlock: supported: true, enabled: true
                 Storage: file
                 Version: Vault v0.8.1
             Version Sha: 8d76a41854608c547a233f2e6292ae5355154695

==> Vault server started! Log data will stream in below:

Expected Behavior:

Actual Behavior:

Steps to Reproduce:

Important Factoids:

References:

_That I am missing something?_
Regards.

Most helpful comment

You have vault set up to listen on HTTP (tls_disable = 1) but you are hitting an HTTPS endpoint. Try export VAULT_ADDR=http://127.0.0.1:8200 followed by vault init.

All 10 comments

@alfer71 Looks like you are working on empty data. If this is the first time you are starting the server, you will have to initialize it.
https://www.vaultproject.io/intro/getting-started/deploy.html#initializing-the-vault

Hi @gobins
is not the first time, but I tried to initialize and display the following:

$ ./vault init
Error initializing Vault: Put https://127.0.0.1:8200/v1/sys/init: dial tcp 127.0.0.1:8200: getsockopt: connection refused

Any other advice that I can perform?
Thanks for your reply

You have vault set up to listen on HTTP (tls_disable = 1) but you are hitting an HTTPS endpoint. Try export VAULT_ADDR=http://127.0.0.1:8200 followed by vault init.

Great!!!! Awesome!!!
Thanks for your advice @calvn , now my vault is working.
Also thanks for you post @gobins.
Have a nice day!
Regards.

Hi calvn
Error initializing Vault: Put http://127.0.0.1:8200/v1/sys/init: dial tcp 127.0.0.1:8200: getsockopt: connection refused.

after initializing i am getting following error

@sure17490 how you solved this problem ? I'm getting the same error

Same issue when I try to run vault using file storage with data coming from a previous instance using s3

Share your config file.

@satheeshCharles @asyd I would recommend you open a new issue or reach out to the mailing list to get your answers. This is a long closed issue and the error above is unrelated to the original issue.

@chrishoffman never mind. I have fixed my problem, long back. I was trying to help @asyd .

Was this page helpful?
0 / 5 - 0 ratings

Related issues

dwdraju picture dwdraju  路  3Comments

lexsys27 picture lexsys27  路  3Comments

anthonyGuo picture anthonyGuo  路  3Comments

narayan8291 picture narayan8291  路  3Comments

0x9090 picture 0x9090  路  3Comments