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

mariabackup.xb_partition failed in buildbot, mariabackup crashed upon shutdown

    Details

      Description

      http://buildbot.askmonty.org/buildbot/builders/win32-debug/builds/10615

      mariabackup.xb_partition                 w3 [ fail ]
              Test ended at 2018-10-01 10:30:16
       
      CURRENT_TEST: mariabackup.xb_partition
      mysqltest: At line 73: exec of 'D:/win32-debug/build/extra/mariabackup/Debug/mariabackup.exe --innobackupex --defaults-file=D:/win32-debug/build/mysql-test/var/3/my.cnf --apply-log D:/win32-debug/build/mysql-test/var/3/tmp/full 2>&1' failed, error: -2147483645, status: -2147483645, errno: 2
      Output from before failure:
      181001 10:30:07 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.1.37-MariaDB Win32 (AMD64) 
      mariabackup: cd to D:/win32-debug/build/mysql-test/var/3/tmp/full/
      mariabackup: This target seems to be already prepared with --apply-log-only.
      mariabackup: notice: xtrabackup_logfile was already used to '--prepare'.
      mariabackup: using the following InnoDB configuration for recovery:
      mariabackup:   innodb_data_home_dir = .\
      mariabackup:   innodb_data_file_path = ibdata1:12M:autoextend
      mariabackup:   innodb_log_group_home_dir = .\
      mariabackup:   innodb_log_files_in_group = 2
      mariabackup:   innodb_log_file_size = 5242880
      mariabackup: using the following InnoDB configuration for recovery:
      mariabackup:   innodb_data_home_dir = .\
      mariabackup:   innodb_data_file_path = ibdata1:12M:autoextend
      mariabackup:   innodb_log_group_home_dir = .\
      mariabackup:   innodb_log_files_in_group = 2
      mariabackup:   innodb_log_file_size = 5242880
      mariabackup: Starting InnoDB instance for recovery.
      mariabackup: Using 104857600 bytes for buffer pool (set by --use-memory parameter)
      2018-10-01 10:30:07 5168 [Note] InnoDB: Using mutexes to ref count buffer pool pages
      2018-10-01 10:30:07 5168 [Note] InnoDB:  InnoDB: !!!!!!!! UNIV_DEBUG switched on !!!!!!!!!
      2018-10-01 10:30:07 5168 [Note] InnoDB:  InnoDB: !!!!!!!! UNIV_SYNC_DEBUG switched on !!!!!!!!!
      2018-10-01 10:30:07 5168 [Note] InnoDB: The InnoDB memory heap is disabled
      2018-10-01 10:30:07 5168 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
      2018-10-01 10:30:07 5168 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
      2018-10-01 10:30:07 5168 [Note] InnoDB: Compressed tables use zlib 1.2.3
      2018-10-01 10:30:07 5168 [Note] InnoDB: Using generic crc32 instructions
      2018-10-01 10:30:07 5168 [Note] InnoDB: Initializing buffer pool, size = 100.0M
      2018-10-01 10:30:07 5168 [Note] InnoDB: Completed initialization of buffer pool
      2018-10-01 10:30:07 5168 [Note] InnoDB: Setting log file .\ib_logfile101 size to 5 MB
      2018-10-01 10:30:07 5168 [Note] InnoDB: Setting log file .\ib_logfile1 size to 5 MB
      2018-10-01 10:30:07 5168 [Note] InnoDB: Renaming log file .\ib_logfile101 to .\ib_logfile0
      2018-10-01 10:30:07 5168 [Warning] InnoDB: New log files created, LSN=1667881
      2018-10-01 10:30:07 5168 [Note] InnoDB: Highest supported file format is Barracuda.
      2018-10-01 10:30:09 5168 [Note] InnoDB: 128 rollback segment(s) are active.
      2018-10-01 10:30:09 5168 [Note] InnoDB: Waiting for purge to start
      2018-10-01 10:30:09 5168 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.39-83.1 started; log sequence number 1668108
       
      mariabackup: starting shutdown with innodb_fast_shutdown = 1
      2018-10-01 10:30:09 7540 [Note] InnoDB: FTS optimize thread exiting.
      2018-10-01 10:30:09 5168 [Note] InnoDB: Starting shutdown...
      2018-10-01 10:30:09 6052 [Note] InnoDB: Dumping buffer pool(s) not yet started
      2018-10-01 10:30:10 5168 [Note] InnoDB: Waiting for page_cleaner to finish flushing of buffer pool
      2018-10-01 10:30:11 5168 [Warning] InnoDB: Some resources were not cleaned up in shutdown: threads 0, events 16, os_mutexes 16, os_fast_mutexes 32
      2018-10-01 10:30:11 5168 [Note] InnoDB: Shutdown completed; log sequence number 1668118
      mariabackup: using the following InnoDB configuration for recovery:
      mariabackup:   innodb_data_home_dir = .\
      mariabackup:   innodb_data_file_path = ibdata1:12M:autoextend
      mariabackup:   innodb_log_group_home_dir = .\
      mariabackup:   innodb_log_files_in_group = 2
      mariabackup:   innodb_log_file_size = 5242880
      2018-10-01 10:30:12 5168 [Note] InnoDB: Using mutexes to ref count buffer pool pages
      2018-10-01 10:30:12 5168 [Note] InnoDB:  InnoDB: !!!!!!!! UNIV_DEBUG switched on !!!!!!!!!
      2018-10-01 10:30:12 5168 [Note] InnoDB:  InnoDB: !!!!!!!! UNIV_SYNC_DEBUG switched on !!!!!!!!!
      2018-10-01 10:30:12 5168 [Note] InnoDB: The InnoDB memory heap is disabled
      2018-10-01 10:30:12 5168 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
      2018-10-01 10:30:12 5168 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
      2018-10-01 10:30:12 5168 [Note] InnoDB: Compressed tables use zlib 1.2.3
      2018-10-01 10:30:12 5168 [Note] InnoDB: Using generic crc32 instructions
      2018-10-01 10:30:12 5168 [Note] InnoDB: Initializing buffer pool, size = 100.0M
      2018-10-01 10:30:12 5168 [Note] InnoDB: Completed initialization of buffer pool
      2018-10-01 10:30:12 5168 [Note] InnoDB: Highest supported file format is Barracuda.
      2018-10-01 10:30:13 5168 [Note] InnoDB: 128 rollback segment(s) are active.
      2018-10-01 10:30:13 5168 [Note] InnoDB: Waiting for purge to start
      2018-10-01 10:30:14 5168 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.39-83.1 started; log sequence number 1668118
      mariabackup: starting shutdown with innodb_fast_shutdown = 1
      2018-10-01 10:30:14 7300 [Note] InnoDB: FTS optimize thread exiting.
      2018-10-01 10:30:14 5168 [Note] InnoDB: Starting shutdown...
      2018-10-01 10:30:14 7884 [Note] InnoDB: Dumping buffer pool(s) not yet started
      2018-10-01 10:30:14 5168 [Note] InnoDB: Waiting for page_cleaner to finish flushing of buffer pool
      abort() has been called181001 10:30:14 [ERROR] mysqld got exception 0x80000003 ;
      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.1.37-MariaDB-debug
      key_buffer_size=0
      read_buffer_size=131072
      max_used_connections=0
      max_threads=1
      thread_count=0
      It is possible that mysqld could use up to 
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 4163 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...
      abort() has been called
       
       
      The result from queries just before the failure was:
      < snip >
      PARTITION p3 VALUES LESS THAN (400));
      INSERT INTO isam_p VALUES (1), (101), (201), (301);
      DROP TABLE t1;
      DROP TABLE t2;
      CREATE TABLE t2(a INT) ENGINE=InnoDB;
      INSERT INTO t2 VALUES (40), (50), (60);
      ALTER TABLE p DROP PARTITION p0;
      ALTER TABLE p DROP PARTITION p1;
      ALTER TABLE p ADD PARTITION (PARTITION p4 VALUES LESS THAN (500));
      ALTER TABLE p ADD PARTITION (PARTITION p5 VALUES LESS THAN (600));
      INSERT INTO p VALUES (401), (501);
      DROP TABLE isam_t1;
      DROP TABLE isam_t2;
      CREATE TABLE isam_t2(a INT) ENGINE=MyISAM;
      INSERT INTO isam_t2 VALUES (40), (50), (60);
      ALTER TABLE isam_p DROP PARTITION p0;
      ALTER TABLE isam_p DROP PARTITION p1;
      ALTER TABLE isam_p ADD PARTITION (PARTITION p4 VALUES LESS THAN (500));
      ALTER TABLE isam_p ADD PARTITION (PARTITION p5 VALUES LESS THAN (600));
      INSERT INTO isam_p VALUES (401), (501);
      

        Attachments

          Activity

            People

            • Assignee:
              vlad.lesin Vladislav Lesin
              Reporter:
              elenst Elena Stepanova
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: