-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ERROR] core: post-unseal setup failed: error="failed to update entity in MemDB #5070
Comments
atomd
changed the title
[ERROR] core: post-unseal setup failed: error="failed to update entity in MemDB: alias "xx" in already tied to a different entity "[ERROR] core: post-unseal setup failed: error="failed to update entity in MemDB: alias "xx" in already tied to a different entity "xx"
[ERROR] core: post-unseal setup failed: error="failed to update entity in MemDB
Aug 8, 2018
Here is the detailed logs.
|
Sorry, I was wrong -- duplicate of #5000 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Environment:
I found that this issue (#4326) is similar to what I have encountered.
When I redeployed vault with previous data (everything is new except mysql storage backend), there will always be some errors. At the same time, the vault is looping in the behavior described in the logs, no leader is ever elected.
It is just like the database was written with dirty data (leader info?) and can never be recovered. The key is that the secrets is lost, which is unacceptable. I want to know:
The text was updated successfully, but these errors were encountered: