[MDEV-19118] encryption.innodb-bad-key-change2 failed in buildbot with Can't connect to local MySQL server through socket Created: 2019-04-01  Updated: 2023-11-29  Resolved: 2023-11-29

Status: Closed
Project: MariaDB Server
Component/s: Tests
Affects Version/s: 10.1
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Elena Stepanova Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: None


 Description   

http://buildbot.askmonty.org/buildbot/builders/kvm-deb-bionic-aarch64/builds/1631

10.1 d0116e10a5da52503a89a413e481996c

encryption.innodb-bad-key-change2 'innodb_plugin' w4 [ fail ]
        Test ended at 2019-03-28 14:38:07
 
CURRENT_TEST: encryption.innodb-bad-key-change2
mysqltest: In included file "./include/wait_until_connected_again.inc": 
included from ./include/restart_mysqld.inc at line 52:
included from /usr/share/mysql/mysql-test/suite/encryption/t/innodb-bad-key-change2.test at line 49:
At line 12: query 'whiile ($mysql_errno)
{
# Strangely enough, the server might return "Too many connections"
  # while being shutdown, thus 1040 is an "allowed" error
# See BUG#36228
--error 0,ER_CON_COUNT_ERROR,ER_SERVER_SHUTDOWN,ER_LOCK_WAIT_TIMEOUT,ER_CONNECTION_KILLED,2002,2003,2005,2006,2013
show status' failed: 2002: Can't connect to local MySQL server through socket '/dev/shm/var/tmp/4/mysqld.1.sock' (2 "No such file or directory")
 
The result from queries just before the failure was:
< snip >
ALTER TABLE t1 engine=InnoDB;
ERROR HY000: Got error 192 'Table encrypted but decryption failed. This could be because correct encryption management plugin is not loaded, used encryption key is not available or encryption method does not match.' from InnoDB
SHOW WARNINGS;
Level	Code	Message
Warning	192	Table "test"."t1" in file ./test/t1.ibd is encrypted but encryption service or used key_id is not available.  Can't continue reading table.
Error	1296	Got error 192 'Table encrypted but decryption failed. This could be because correct encryption management plugin is not loaded, used encryption key is not available or encryption method does not match.' from InnoDB
OPTIMIZE TABLE t1;
Table	Op	Msg_type	Msg_text
test.t1	optimize	Warning	Table "test"."t1" in file ./test/t1.ibd is encrypted but encryption service or used key_id is not available.  Can't continue reading table.
test.t1	optimize	Error	Got error 192 'Table encrypted but decryption failed. This could be because correct encryption management plugin is not loaded, used encryption key is not available or encryption method does not match.' from InnoDB
test.t1	optimize	error	Corrupt
SHOW WARNINGS;
Level	Code	Message
CHECK TABLE t1;
Table	Op	Msg_type	Msg_text
test.t1	check	Warning	Table "test"."t1" in file ./test/t1.ibd is encrypted but encryption service or used key_id is not available.  Can't continue reading table.
test.t1	check	Error	Got error 192 'Table encrypted but decryption failed. This could be because correct encryption management plugin is not loaded, used encryption key is not available or encryption method does not match.' from InnoDB
test.t1	check	error	Corrupt
SHOW WARNINGS;
Level	Code	Message
 
More results from queries before failure can be found in /dev/shm/var/4/log/innodb-bad-key-change2.log


Generated at Thu Feb 08 08:49:11 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.