Details
-
Bug
-
Status: Confirmed (View Workflow)
-
Major
-
Resolution: Unresolved
-
10.6.27, 10.11.18, 11.4.12, 11.8.8
-
None
Description
when changing file_key_management_encryption_algorithm from AES_CBC to AES_CTR or vice versa server startup fails with a very unhelpful error message:
2026-08-06 13:18:47 0 [Warning] InnoDB: Log scan aborted at LSN 6614528
2026-08-06 13:18:47 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
Same when having used AES_CTR and then trying to switch to a different plugin with same keys having been set up
Switching to e.g. HashiCorp Vault only works with AES_CBC; with AES_CTR being used originally it will fail with the exact same messages above; never saying WHAT plugin failed to initialize or WHY ...