Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-8799

Server crashes in btr_defragment_add_index, encryption.innodb-bad-key-change5 and alike fail in buildbot

    Details

      Description

      http://buildbot.askmonty.org/buildbot/builders/kvm-bintar-quantal-amd64/builds/1759/steps/test/logs/stdio

      encryption.innodb-bad-key-change5 'innodb_plugin' w3 [ fail ]
              Test ended at 2015-09-14 19:42:15
       
      CURRENT_TEST: encryption.innodb-bad-key-change5
      mysqltest: At line 61: query 'OPTIMIZE TABLE t1' failed: 2013: Lost connection to MySQL server during query
       
      The result from queries just before the failure was:
      call mtr.add_suppression("InnoDB: Block in space_id .* in file test/.* encrypted");
      call mtr.add_suppression("InnoDB: However key management plugin or used key_id 1 is not found or used encryption algorithm or method does not match.");
      call mtr.add_suppression("InnoDB: Marking tablespace as missing. You may drop this table or install correct key management plugin and key file.");
      call mtr.add_suppression(".*InnoDB: Cannot open table test/.* from the internal data dictionary of InnoDB though the .frm file for the table exists. See .* for how you can resolve the problem.");
      call mtr.add_suppression("InnoDB: .ibd file is missing for table test/.*");
      call mtr.add_suppression("Couldn't load plugins from 'file_key_management*");
      SET GLOBAL innodb_file_format = `Barracuda`;
      SET GLOBAL innodb_file_per_table = ON;
      CREATE TABLE t1 (pk INT PRIMARY KEY, f VARCHAR(8)) ENGINE=InnoDB ENCRYPTION_KEY_ID=4;
      INSERT INTO t1 VALUES (1,'foo'),(2,'bar');
      SET GLOBAL innodb_file_format = `Barracuda`;
      SET GLOBAL innodb_file_per_table = ON;
      OPTIMIZE TABLE t1;

      2015-09-14 19:42:14 139766419814144 [ERROR] InnoDB: Block in space_id 4 in file test/t1 encrypted.
      2015-09-14 19:42:14 139766419814144 [ERROR] InnoDB: However key management plugin or used key_id 1 is not found or used encryption algorithm or method does not match.
      2015-09-14 19:42:14 139766419814144 [ERROR] InnoDB: Marking tablespace as missing. You may drop this table or install correct key management plugin and key file.
      2015-09-14 19:42:14 139766419814144 [ERROR] InnoDB: Block in space_id 4 in file test/t1 encrypted.
      2015-09-14 19:42:14 139766419814144 [ERROR] InnoDB: However key management plugin or used key_id 1 is not found or used encryption algorithm or method does not match.
      2015-09-14 19:42:14 139766419814144 [ERROR] InnoDB: Marking tablespace as missing. You may drop this table or install correct key management plugin and key file.
      150914 19:42:14 [ERROR] mysqld got signal 11 ;
      This could be because you hit a bug. It is also possible that this binary
      or one of the libraries it was linked against is corrupt, improperly built,
      or misconfigured. This error can also be caused by malfunctioning hardware.
       
      To report this bug, see http://kb.askmonty.org/en/reporting-bugs
       
      We will try our best to scrape up some info that will hopefully help
      diagnose the problem, but since we have already crashed, 
      something is definitely wrong and this may fail.
       
      Server version: 10.1.8-MariaDB-log
      key_buffer_size=1048576
      read_buffer_size=131072
      max_used_connections=1
      max_threads=153
      thread_count=1
      It is possible that mysqld could use up to 
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 62878 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
       
      Thread pointer: 0x0x7f1de0fd0008
      Attempting backtrace. You can use the following information to find out
      where mysqld died. If you see no messages after this, something went
      terribly wrong...
      stack_bottom = 0x7f1de7cdeda0 thread_stack 0x48000
      /usr/local/mariadb-10.1.8-linux-x86_64/bin/mysqld(my_print_stacktrace+0x2b)[0x7f1de879083b]
      /usr/local/mariadb-10.1.8-linux-x86_64/bin/mysqld(handle_fatal_signal+0x475)[0x7f1de82f0545]
      /lib/x86_64-linux-gnu/libpthread.so.0(+0xfcb0)[0x7f1de6ea2cb0]
      /usr/local/mariadb-10.1.8-linux-x86_64/lib/plugin/ha_innodb.so(_Z24btr_defragment_add_indexP12dict_index_tbP7dberr_t+0xfd)[0x7f1ddf77a51d]
      /usr/local/mariadb-10.1.8-linux-x86_64/lib/plugin/ha_innodb.so(+0x11ced0)[0x7f1ddf83bed0]
      /usr/local/mariadb-10.1.8-linux-x86_64/lib/plugin/ha_innodb.so(+0x11d0eb)[0x7f1ddf83c0eb]
      /usr/local/mariadb-10.1.8-linux-x86_64/bin/mysqld(+0x5019e9)[0x7f1de82519e9]
      /usr/local/mariadb-10.1.8-linux-x86_64/bin/mysqld(_ZN22Sql_cmd_optimize_table7executeEP3THD+0x18f)[0x7f1de8252dff]
      /usr/local/mariadb-10.1.8-linux-x86_64/bin/mysqld(_Z21mysql_execute_commandP3THD+0x13d0)[0x7f1de8180c00]
      /usr/local/mariadb-10.1.8-linux-x86_64/bin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x22d)[0x7f1de81887ad]
      /usr/local/mariadb-10.1.8-linux-x86_64/bin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x2293)[0x7f1de818b253]
      /usr/local/mariadb-10.1.8-linux-x86_64/bin/mysqld(_Z10do_commandP3THD+0x16b)[0x7f1de818b7fb]
      /usr/local/mariadb-10.1.8-linux-x86_64/bin/mysqld(_Z24do_handle_one_connectionP3THD+0x187)[0x7f1de8246377]
      /usr/local/mariadb-10.1.8-linux-x86_64/bin/mysqld(handle_one_connection+0x47)[0x7f1de8246547]
      /usr/local/mariadb-10.1.8-linux-x86_64/bin/mysqld(+0x92dc8d)[0x7f1de867dc8d]
      /lib/x86_64-linux-gnu/libpthread.so.0(+0x7e9a)[0x7f1de6e9ae9a]
      /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f1de65c8cbd]
       
      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort.
      Query (0x7f1dd14c4020): OPTIMIZE TABLE t1
      Connection ID (thread ID): 2
      Status: NOT_KILLED

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                jplindst Jan Lindström
                Reporter:
                elenst Elena Stepanova
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: