We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The issue described here : #512 is still happening when using HA with Mysql Backend ([update] Vault v0.11.3):
Error initializing storage of type mysql: failed to create mysql table: Error 1071: Specified key was too long; max key length is 767 bytes
The vault table exists, but does HA mode try to create another table to store HA lock or something? (I didn't dig into the code)
vault
To reproduce, in conf file, just add ha_enabled = "true" in storage "mysql" section.
ha_enabled = "true"
storage "mysql"
The text was updated successfully, but these errors were encountered:
Changing from varchar to varbinary (as in this issue: #512) fixes the problem.
Sorry, something went wrong.
No branches or pull requests
The issue described here : #512 is still happening when using HA with Mysql Backend ([update] Vault v0.11.3):
Error initializing storage of type mysql: failed to create mysql table: Error 1071: Specified key was too long; max key length is 767 bytes
The
vault
table exists, but does HA mode try to create another table to store HA lock or something? (I didn't dig into the code)To reproduce, in conf file, just add
ha_enabled = "true"
instorage "mysql"
section.The text was updated successfully, but these errors were encountered: