# Call to sys/init API results in "core: barrier reports initialized but no seal configuration found"

**URL:** <https://discuss.hashicorp.com/t/call-to-sys-init-api-results-in-core-barrier-reports-initialized-but-no-seal-configuration-found/17272>\
**Category:** Vault\
**Tags:** k8s, helm\
**Created:** [November 6, 2020, 6:46am UTC](https://discuss.hashicorp.com/t/call-to-sys-init-api-results-in-core-barrier-reports-initialized-but-no-seal-configuration-found/17272 "2020-11-06T06:46:51Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![rishabkatta](https://sea2.discourse-cdn.com/hashicorp/user_avatar/discuss.hashicorp.com/rishabkatta/32/13915_2.png) [@rishabkatta](https://discuss.hashicorp.com/u/rishabkatta)\
**Post date:** [November 6, 2020, 6:46am UTC](https://discuss.hashicorp.com/t/call-to-sys-init-api-results-in-core-barrier-reports-initialized-but-no-seal-configuration-found/17272/1 "2020-11-06T06:46:51Z")

</div>

Vault status -

[root@jade-cw01 ~]# curl --insecure -g -s https://[2001:db8:1234::39d5]:8200/v1/sys/seal-status  
{“type”:“shamir”,“initialized”:false,“sealed”:true,“t”:0,“n”:0,“progress”:0,“nonce”:"",“version”:"",“migration”:false,“recovery\_seal”:false,“storage\_type”:“mysql”}

trying to initialize -  
[root@jade-cw01 ~]# curl --insecure -g -s --request PUT --data ‘{“secret\_shares”: 1, “secret\_threshold”: 1}’ https://[2001:db8:1234::39d5]:8200/v1/sys/init  
{“errors”:[“core: barrier reports initialized but no seal configuration found”]}

What is going on? I need some help

---

<div class="post-metadata">

**Author:** ![rishabkatta](https://sea2.discourse-cdn.com/hashicorp/user_avatar/discuss.hashicorp.com/rishabkatta/32/13915_2.png) [@rishabkatta](https://discuss.hashicorp.com/u/rishabkatta)\
**Post date:** [November 9, 2020, 5:57pm UTC](https://discuss.hashicorp.com/t/call-to-sys-init-api-results-in-core-barrier-reports-initialized-but-no-seal-configuration-found/17272/2 "2020-11-09T17:57:49Z")

</div>

I need some help understanding what is causing that API to return that error?

---

<div class="post-metadata">

**Author:** ![christopher-demarco](https://sea2.discourse-cdn.com/hashicorp/user_avatar/discuss.hashicorp.com/christopher-demarco/32/15682_2.png) [@christopher-demarco](https://discuss.hashicorp.com/u/christopher-demarco)\
**Post date:** [December 10, 2020, 10:17pm UTC](https://discuss.hashicorp.com/t/call-to-sys-init-api-results-in-core-barrier-reports-initialized-but-no-seal-configuration-found/17272/3 "2020-12-10T22:17:26Z")

</div>

I’m encountering this while experimenting—I’m running Vault with the Consul backend, and I deleted the `vault` folder from the Consul k/v store.

In older versions of Vault, removing that folder would permit re-initializing Vault with new keys, but now I get the error you’re reporting—so it seems that there’s some “I’m initialized” state either stored elsewhere in Consul, or in one of the Vault nodes themselves.

More research is required, will follow-up once I learn something.

---

<div class="post-metadata">

**Author:** ![christopher-demarco](https://sea2.discourse-cdn.com/hashicorp/user_avatar/discuss.hashicorp.com/christopher-demarco/32/15682_2.png) [@christopher-demarco](https://discuss.hashicorp.com/u/christopher-demarco)\
**Post date:** [December 11, 2020, 1:19am UTC](https://discuss.hashicorp.com/t/call-to-sys-init-api-results-in-core-barrier-reports-initialized-but-no-seal-configuration-found/17272/4 "2020-12-11T01:19:35Z")

</div>

Confirmed: removing the entire `vault/` key from the Consul kv store (instead of just leaving the key intact and removing the nodes beneath it) lets me re-initialize the Vault.

So it looks like @rishabkatta you might have a a `vault` key in Consul which is preventing Vault from initializing.