Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.1.4
Description
If the server starts on a fresh datadir with
innodb-encrypt-tables
|
innodb-encryption-threads = 4
|
(only with them on top of defaults),
it goes down with the assertion failure:
Stack trace from 10.1 commit 22a7b4dee0 |
2015-04-18 04:08:34 7fe59fbfa700 InnoDB: Assertion failure in thread 140624204375808 in file fil0crypt.cc line 988
|
InnoDB: Failing assertion: new_state->key_version != ENCRYPTION_KEY_VERSION_INVALID
|
InnoDB: We intentionally generate a memory trap.
|
 |
#0 0x00007fe5c8fe8165 in *__GI_raise (sig=<optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
|
#1 0x00007fe5c8feb3e0 in *__GI_abort () at abort.c:92
|
#2 0x00007fe5cbf5c59c in fil_crypt_get_key_state (new_state=0x7fe59ebfed90) at 10.1/storage/xtradb/fil/fil0crypt.cc:988
|
#3 0x00007fe5cbf5e734 in fil_crypt_thread (arg=0x0) at 10.1/storage/xtradb/fil/fil0crypt.cc:2148
|
#4 0x00007fe5caffcb50 in start_thread (arg=<optimized out>) at pthread_create.c:304
|
#5 0x00007fe5c909195d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
|
#6 0x0000000000000000 in ?? ()
|