Bug #80451 | mysqld --initialize does not support the keyring_file_data option | ||
---|---|---|---|
Submitted: | 20 Feb 2016 1:11 | Modified: | 27 Apr 2016 13:45 |
Reporter: | Jesper wisborg Krogh | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Installing | Severity: | S2 (Serious) |
Version: | 5.7.11 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[20 Feb 2016 1:11]
Jesper wisborg Krogh
[20 Feb 2016 1:16]
Jesper wisborg Krogh
Posted by developer: The workaround is to initialise MySQL without the keyring_file_data option, then add it before starting MySQL (or restart MySQL is it's already started).
[24 Feb 2016 7:25]
MySQL Verification Team
Bug #80488 marked as duplicate of this.
[18 Apr 2016 6:58]
Shishir Jaiswal
Posted by developer: Patch approved on RB.
[27 Apr 2016 13:45]
Paul DuBois
Posted by developer: Noted in 5.7.13 changelog. Starting the server with --initialize failed if the keyring_file_data system variable was also set at startup. To handle this, with --initialize the server no longer skips registration of plugins loaded with the --early-plugin-load option.