Uploaded image for project: 'Percona XtraBackup'
  1. Percona XtraBackup
  2. PXB-1839

PXB 8.0.5 crashes when preparing MySQL 8.0.16

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Done
    • Priority: High
    • Resolution: Fixed
    • Affects Version/s: 8.0.5
    • Fix Version/s: 8.0.6
    • Component/s: None
    • Labels:
      None

      Description

      Trying to prepare the be 8.0.16 backup results in a crash:

      Backup completes ok

      190429 18:30:21 [01] Copying performance_schema/events_transacti_128.sdi to /tmp/bkp/performance_schema/events_transacti_128.sdi
      190429 18:30:21 [01]        ...done
      190429 18:30:21 Finished backing up non-InnoDB tables and files
      190429 18:30:21 Executing FLUSH NO_WRITE_TO_BINLOG BINARY LOGS
      190429 18:30:21 Selecting LSN and binary log position from p_s.log_status
      190429 18:30:21 [00] Copying /var/lib/mysql/binlog.000004 to /tmp/bkp/binlog.000004
      190429 18:30:21 [00]        ...done
      190429 18:30:21 [00] Writing /tmp/bkp/binlog.index
      190429 18:30:21 [00]        ...done
      190429 18:30:21 [00] Writing /tmp/bkp/xtrabackup_binlog_info
      190429 18:30:21 [00]        ...done
      190429 18:30:21 Executing FLUSH NO_WRITE_TO_BINLOG ENGINE LOGS...
      xtrabackup: The latest check point (for incremental): '22128075'
      xtrabackup: Stopping log copying thread at LSN 22128075.
      .190429 18:30:21 >> log scanned up to (22128075)
      190429 18:30:21 >> log scanned up to (22128075)
      
      190429 18:30:21 All tables unlocked
      190429 18:30:21 [00] Copying ib_buffer_pool to /tmp/bkp/ib_buffer_pool
      190429 18:30:21 [00]        ...done
      190429 18:30:21 Backup created in directory '/tmp/bkp/'
      MySQL binlog position: filename 'binlog.000004', position '155'
      190429 18:30:21 [00] Writing /tmp/bkp/backup-my.cnf
      190429 18:30:21 [00]        ...done
      190429 18:30:22 [00] Writing /tmp/bkp/xtrabackup_info
      190429 18:30:22 [00]        ...done
      xtrabackup: Transaction log of lsn (22128075) to (22128075) was copied.
      190429 18:30:22 completed OK!
      

      But crashed once I try to prepare

      root@stretch:~# xtrabackup --prepare --target-dir=/tmp/bkp/
      xtrabackup: recognized server arguments: --innodb_checksum_algorithm=innodb --innodb_log_checksums=1 --innodb_data_file_path=ibdata1:12M:autoextend --innodb_log_files_in_group=2 --innodb_log_file_size=50331648 --innodb_page_size=16384 --i
      nnodb_undo_directory=./ --innodb_undo_tablespaces=2 --server-id=0 --innodb_log_checksums=ON --innodb_redo_log_encrypt=0 --innodb_undo_log_encrypt=0
      xtrabackup: recognized client arguments: --prepare=1 --target-dir=/tmp/bkp/
      xtrabackup version 8.0.5 based on MySQL server 8.0.14 Linux (x86_64) (revision id: 40ec8a3)
      xtrabackup: cd to /tmp/bkp/
      xtrabackup: This target seems to be not prepared yet.
      Number of pools: 1
      xtrabackup: xtrabackup_logfile detected: size=8388608, start_lsn=(22128075)
      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:   innodb_log_files_in_group = 1
      xtrabackup:   innodb_log_file_size = 8388608
      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:   innodb_log_files_in_group = 1
      xtrabackup:   innodb_log_file_size = 8388608
      xtrabackup: Starting InnoDB instance for recovery.
      xtrabackup: Using 104857600 bytes for buffer pool (set by --use-memory parameter)
      PUNCH HOLE support available
      Mutexes and rw_locks use GCC atomic builtins
      Uses event mutexes
      GCC builtin __atomic_thread_fence() is used for memory barrier
      Compressed tables use zlib 1.2.8
      Number of pools: 1
      Using CPU crc32 instructions
      Directories to scan '.;.;.'
      Scanning './'
      Completed space ID check of 7 files.
      Initializing buffer pool, total size = 128.000000M, instances = 1, chunk size =128.000000M
      Completed initialization of buffer pool
      page_cleaner coordinator priority: -20
      page_cleaner worker priority: -20
      page_cleaner worker priority: -20
      page_cleaner worker priority: -20
      The log sequence number 19502917 in the system tablespace does not match the log sequence number 22128075 in the ib_logfiles!
      Database was not shutdown normally!
      Starting crash recovery.
      Starting to parse redo log at lsn = 22127709, whereas checkpoint_lsn = 22128075
      Doing recovery: scanned up to log sequence number 22128075
      Log background threads are being started...
      Applying a batch of 0 redo log records ...
      Apply batch completed!
      xtrabackup: Last MySQL binlog file position 1719031, file name binlog.000002
      Using undo tablespace './undo_001'.
      Using undo tablespace './undo_002'.
      Opened 2 existing undo tablespaces.
      Creating shared tablespace for temporary tables
      Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
      File './ibtmp1' size is now 12 MB.
      Scanning temp tablespace dir:'./#innodb_temp/'
      Created 128 and tracked 128 new rollback segment(s) in the temporary tablespace. 128 are now active.
      8.0.14 started; log sequence number 22128075
      Allocated tablespace ID 2 for worlds/City, old maximum was 0
      xtrabackup: Unknown error 3613
      xtrabackup: Unknown error 3613
      xtrabackup: Unknown error 3613
      xtrabackup: Unknown error 3613
      xtrabackup: Unknown error 3613
      18:30:32 UTC - 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.
      Attempting to collect some information that could help diagnose the problem.
      As this is a crash and something is definitely wrong, the information
      collection process might fail.
      
      key_buffer_size=0
      read_buffer_size=131072
      max_used_connections=0
      max_threads=0
      thread_count=0
      connection_count=0
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1676 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 = 0 thread_stack 0x46000
      xtrabackup(my_print_stacktrace(unsigned char*, unsigned long)+0x2e) [0x5597b4ce26ee]
      xtrabackup(handle_fatal_signal+0x4c1) [0x5597b3d5dd91]
      /lib/x86_64-linux-gnu/libpthread.so.0(+0x110c0) [0x7fa2bcb030c0]
      xtrabackup(dd::get_dd_client(THD*)+0x1) [0x5597b424b651]
      xtrabackup(dd_table_open_on_name(THD*, MDL_ticket**, char const*, bool, unsigned long)+0x29d) [0x5597b3f08c4d]
      xtrabackup(+0xc0a2a4) [0x5597b39132a4]
      xtrabackup(+0xc0cf5f) [0x5597b3915f5f]
      xtrabackup(main+0x6dc) [0x5597b38d69ac]
      /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1) [0x7fa2ba84d2e1]
      xtrabackup(_start+0x2a) [0x5597b3903f3a]
      

      Installed packages:

      root@stretch:~# dpkg -l | grep mysql
      ii  libdbd-mysql-perl              4.041-2                        amd64        Perl5 database interface to the MariaDB/MySQL database
      ii  mysql-apt-config               0.8.12-1                       all          Auto configuration for MySQL APT Repo.
      ii  mysql-client                   8.0.16-1debian9                amd64        MySQL Client meta package depending on latest version
      ii  mysql-common                   8.0.16-1debian9                amd64        Common files shared between packages
      ii  mysql-community-client         8.0.16-1debian9                amd64        MySQL Client
      ii  mysql-community-client-core    8.0.16-1debian9                amd64        MySQL Client Core Binaries
      ii  mysql-community-server         8.0.16-1debian9                amd64        MySQL Server
      ii  mysql-community-server-core    8.0.16-1debian9                amd64        MySQL Server Core Binaires
      root@stretch:~# dpkg -l | grep percona
      ii  percona-release                1.0-11.generic                 all          Package to install Percona gpg key and APT repos
      ii  percona-toolkit                3.0.13-1.stretch               amd64        Advanced MySQL and system command-line tools
      ii  percona-xtrabackup-80          8.0.5-1.stretch                amd64        Open source backup tool for InnoDB and XtraDB
      ii  percona-xtrabackup-dbg-80      8.0.5-1.stretch                amd64        Debug symbols for Percona XtraBackup
      ii  percona-xtrabackup-test-80     8.0.5-1.stretch                amd64        Test suite for Percona XtraBackup
      

      MySQL 8.0.16 installed from the Oracle's repo with default config.

      Running this on jenkins, it fails on all supported distros.

        Smart Checklist

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                sergei.glushchenko Sergei Glushchenko (Inactive)
                Reporter:
                hrvoje.matijakovic Hrvoje Matijakovic
                Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    Time Tracking

                    Estimated:
                    Original Estimate - Not Specified
                    Not Specified
                    Remaining:
                    Remaining Estimate - Not Specified
                    Not Specified
                    Logged:
                    Time Spent - 2 hours, 21 minutes
                    2h 21m