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

mariabackup.xb_compressed_encrypted failed in buildbot, InnoDB: assertion failure





      mariabackup.xb_compressed_encrypted '8k,innodb' w1 [ fail ]
              Test ended at 2017-09-12 18:24:56
      CURRENT_TEST: mariabackup.xb_compressed_encrypted
      mysqltest: At line 25: exec of '/usr/bin/mariabackup --innobackupex --apply-log /run/shm/var/1/tmp/backup 2>&1' failed, error: 34304, status: 134, errno: 11
      Output from before failure:
      170912 18:24:49 innobackupex: Starting the apply-log operation
      IMPORTANT: Please check that the apply-log run completes successfully.
                 At the end of a successful apply-log run innobackupex
                 prints "completed OK!".
      --innobackupex based on MariaDB server 10.2.9-MariaDB debian-linux-gnu (i686) 
      xtrabackup: cd to /run/shm/var/1/tmp/backup/
      Loading encryption plugin
      	 Encryption plugin parameter :  '--file_key_management_encryption_algorithm=aes_cbc'
      	 Encryption plugin parameter :  '--file_key_management_filekey='
      	 Encryption plugin parameter :  '--file_key_management_filename=/usr/share/mysql/mysql-test/std_data/logkey.txt'
      	 Encryption plugin parameter :  '--apply-log'
      	 Encryption plugin parameter :  '/run/shm/var/1/tmp/backup'
      xtrabackup: This target seems to be not prepared yet.
      InnoDB: The universal page size of the database is set to 8192.
      xtrabackup: using the following InnoDB configuration for recovery:
      xtrabackup:   innodb_data_home_dir = .
      xtrabackup:   innodb_data_file_path = ibdata1:12M:autoextend
      xtrabackup:   innodb_log_group_home_dir = .
      xtrabackup: Starting InnoDB instance for recovery.
      xtrabackup: Using 104857600 bytes for buffer pool (set by --use-memory parameter)
      2017-09-12 18:24:49 3055650560 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
      2017-09-12 18:24:49 3055650560 [Note] InnoDB: Uses event mutexes
      2017-09-12 18:24:49 3055650560 [Note] InnoDB: Compressed tables use zlib 1.2.8
      2017-09-12 18:24:49 3055650560 [Note] InnoDB: Number of pools: 1
      2017-09-12 18:24:49 3055650560 [Note] InnoDB: Using generic crc32 instructions
      2017-09-12 18:24:49 3055650560 [Note] InnoDB: Initializing buffer pool, total size = 100M, instances = 1, chunk size = 100M
      2017-09-12 18:24:49 3055650560 [Note] InnoDB: Completed initialization of buffer pool
      2017-09-12 18:24:49 2851584832 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
      2017-09-12 18:24:49 3055650560 [Note] InnoDB: Highest supported file format is Barracuda.
      2017-09-12 18:24:49 3055650560 [Note] InnoDB: Starting crash recovery from checkpoint LSN=938243
      2017-09-12 18:24:49 3055650560 [Note] InnoDB: 1 transaction(s) which must be rolled back or cleaned up in total 0 row operations to undo
      2017-09-12 18:24:49 3055650560 [Note] InnoDB: Trx id counter is 1792
      2017-09-12 18:24:49 3055650560 [Note] InnoDB: Starting final batch to recover 265 pages from redo log.

      2017-09-12 18:24:50 0xb6218700  InnoDB: Assertion failure in file /home/buildbot/buildbot/build/mariadb-10.2.9/storage/innobase/trx/trx0trx.cc line 624
      InnoDB: Failing assertion: trx_state_eq(trx, TRX_STATE_PREPARED) || (trx_state_eq(trx, TRX_STATE_ACTIVE) && trx->is_recovered && (!srv_was_started || srv_operation == SRV_OPERATION_RESTORE || srv_read_only_mode || srv_force_recovery >= SRV_FORCE_NO_TRX_UNDO))
      InnoDB: We intentionally generate a memory trap.
      InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
      InnoDB: If you get repeated assertion failures or crashes, even
      InnoDB: immediately after the mysqld startup, there may be
      InnoDB: corruption in the InnoDB tablespace. Please refer to
      InnoDB: http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html
      InnoDB: about forcing recovery.
      170912 18:24:50 [ERROR] mysqld got signal 6 ;
      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 https://mariadb.com/kb/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.2.9-MariaDB-10.2.9+maria~trusty
      It is possible that mysqld could use up to 
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 4225 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
      Thread pointer: 0x0
      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 = 0x0 thread_stack 0x49000
      addr2line: '--innobackupex': No such file
      The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
      information that should help you find out what is causing the crash.
      Aborted (core dumped)
      The result from queries just before the failure was:
      CREATE TABLE t1(c1 INT, b VARCHAR(2400), index(b(100),c1))
      # xtrabackup backup
      drop table t1;


        Issue Links



              marko Marko Mäkelä
              elenst Elena Stepanova
              0 Vote for this issue
              3 Start watching this issue



                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.