restart vault to apply config changes

1,930 views
Skip to first unread message

rt

unread,
Apr 6, 2017, 6:33:45 PM4/6/17
to Vault
I am new to using vault. I used Hashicorp template to get vault set up on AWS. I made changes to vault.hcl. How do these configurations get reflected? Is there a way to restart?

backend "consul" {
  address = "consul.service.consul:8500"
  path = "vault/"
}

listener "tcp" {
  address = "0.0.0.0:8200"
  tls_disable = 1
}



Jeff Mitchell

unread,
Apr 6, 2017, 6:38:55 PM4/6/17
to Vault
Hi Rajesh,

You do indeed need to restart Vault.

Best,
Jeff


--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/hashicorp/vault/issues
IRC: #vault-tool on Freenode
---
You received this message because you are subscribed to the Google Groups "Vault" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vault-tool+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vault-tool/5adbe1e7-fdd6-4756-9f55-c460468f953d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

rt

unread,
Apr 6, 2017, 6:54:34 PM4/6/17
to Vault
Thanks Jeff. I am unable to find restart steps in the documentation. Could you share any leads please?
I referred here > https://www.vaultproject.io/docs/index.html


On Thursday, April 6, 2017 at 3:38:55 PM UTC-7, Jeff Mitchell wrote:
Hi Rajesh,

You do indeed need to restart Vault.

Best,
Jeff


On Apr 6, 2017 18:33, "rt" <rajesh....@gmail.com> wrote:
I am new to using vault. I used Hashicorp template to get vault set up on AWS. I made changes to vault.hcl. How do these configurations get reflected? Is there a way to restart?

backend "consul" {
  address = "consul.service.consul:8500"
  path = "vault/"
}

listener "tcp" {
  address = "0.0.0.0:8200"
  tls_disable = 1
}



--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/hashicorp/vault/issues
IRC: #vault-tool on Freenode
---
You received this message because you are subscribed to the Google Groups "Vault" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vault-tool+...@googlegroups.com.

rt

unread,
Apr 7, 2017, 2:31:55 PM4/7/17
to Vault
I tried following steps which seems to pick up the latest config changes. This is brand new env so I kind of played around. I am not sure if it is the best way to restart vault

1. Seal the vault: vault seal
2. Kill the vault process: kill -9 {PID_OF_VAULT}   (SIGKILL may be bad idea but it worked)
3. Unseal the vault: vault unseal

Please correct me if this is not the way to do it.

Jeff Mitchell

unread,
Apr 7, 2017, 3:47:46 PM4/7/17
to Vault
Hi Rajesh,

SIGKILL is almost never the right way to gracefully restart a process. Vault accepts SIGINT or SIGTERM to shut down gracefully.

Best,
Jeff

To unsubscribe from this group and stop receiving emails from it, send an email to vault-tool+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vault-tool/f260e1f9-2d63-4199-8b62-c14bee34a473%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages