-
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
vault crashed with : panic: runtime error: invalid memory address or nil pointer dereference #819
Comments
Hi Wayne, What version of Vault is this? Thanks, |
Definitely running Vault v0.3.1 Let's just close this and we'll see if it comes back after we upgrade ( which will be a while. |
We are facing the same issue with v0.6.2. Unable to unseal the vault. Any idea? {VAULT_HOME}/vault --version journalctl --unit vault |
That panic is a bug that has been fixed for more than a year and a half. |
@jefferai It seems this bug was fixed earlier, but I am still getting this error again on the new version. Any help is appreciated.
==> Vault server started! Log data will stream in below: 2018/03/29 15:53:05.789456 [INFO ] core: security barrier not initialized |
@smitjainsj File a new ticket, please. |
This is the most likely pertinent info:
Attached log file excerpt: vault.log-excerpt.txt
The text was updated successfully, but these errors were encountered: