[MDEV-8021] "InnoDB: Tablespace id 4 encrypted but encryption service not available. Can't continue opening tablespace" on server restart when there are encrypted tables Created: 2015-04-19  Updated: 2015-05-09  Resolved: 2015-05-09

Status: Closed
Project: MariaDB Server
Component/s: Encryption, Storage Engine - InnoDB, Storage Engine - XtraDB
Affects Version/s: 10.1.4
Fix Version/s: 10.1.5

Type: Bug Priority: Blocker
Reporter: Elena Stepanova Assignee: Sergei Golubchik
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Relates
relates to MDEV-8011 Table encryption issues Closed

 Description   
  • start server on a clean datadir with all default options and 

    --plugin-load-add=file_key_management.so --file_key_management_filename=/git/10.1/mysql-test/std_data/keys.txt  --innodb-encrypt-tables=ON

  • run CREATE TABLE t1 (i INT);
  • shutdown the server
  • start the server again, with the same opitons =>

150419 19:42:42 [ERROR] InnoDB: Tablespace id 4 encrypted but encryption service not available. Can't continue opening tablespace.
 
 
 
2015-04-19 19:42:42 7f54192db760  InnoDB: Assertion failure in thread 139999176406880 in file ha_innodb.cc line 21064
 
 
 
#5  0x00007f5416eb83e0 in *__GI_abort () at abort.c:92
 
#6  0x00007f5419bd3754 in ib_logf (level=IB_LOG_LEVEL_FATAL, format=0x7f541a2dd398 "Tablespace id %ld encrypted but encryption service not available. Can't continue opening tablespace.\n") at 10.1/storage/xtradb/handler/ha_innodb.cc:21064
 
#7  0x00007f5419e1a360 in fil_read_first_page (data_file=15, one_read_already=0, flags=0x7ffc003ec728, space_id=0x7ffc003ec720, min_flushed_lsn=0x7ffc003ec718, max_flushed_lsn=0x7ffc003ec718, orig_space_id=4, crypt_data=0x7ffc003ec738) at 10.1/storage/xtradb/fil/fil0fil.cc:2041
 
#8  0x00007f5419e1d64b in fil_open_single_table_tablespace (validate=true, fix_dict=true, id=4, flags=0, tablename=0x7f53fab6f778 "test/t1", path_in=0x0) at 10.1/storage/xtradb/fil/fil0fil.cc:3740
 
#9  0x00007f5419df7c05 in dict_check_tablespaces_and_store_max_id (dict_check=DICT_CHECK_NONE_LOADED) at 10.1/storage/xtradb/dict/dict0load.cc:1171
 
#10 0x00007f5419d1bcc8 in innobase_start_or_create_for_mysql () at 10.1/storage/xtradb/srv/srv0start.cc:2597
 
#11 0x00007f5419bb6772 in innobase_init (p=0x7f541654f070) at 10.1/storage/xtradb/handler/ha_innodb.cc:4083
 
#12 0x00007f5419a098b4 in ha_initialize_handlerton (plugin=0x7f541653c6e8) at 10.1/sql/handler.cc:512
 
#13 0x00007f54197f1bd8 in plugin_initialize (tmp_root=0x7ffc003f0dd0, plugin=0x7f541653c6e8, argc=0x7f541aac5950, argv=0x7f541641e6a0, options_only=false) at 10.1/sql/sql_plugin.cc:1403
 
#14 0x00007f54197f27aa in plugin_init (argc=0x7f541aac5950, argv=0x7f541641e6a0, flags=2) at 10.1/sql/sql_plugin.cc:1676
 
#15 0x00007f5419714627 in init_server_components () at 10.1/sql/mysqld.cc:5041
 
#16 0x00007f5419715768 in mysqld_main (argc=14, argv=0x7f541641e6a0) at 10.1/sql/mysqld.cc:5631
 
#17 0x00007f541970b340 in main (argc=14, argv=0x7ffc003f1b18) at 10.1/sql/main.cc:25

A variation of the same problem:
Bootstrap cannot be run with encryption. If it is, the system InnoDB tables are created encrypted, and the server cannot start anymore.

See also MDEV-8011 for another scenario causing the same error.


Generated at Thu Feb 08 07:24:03 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.