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

Full backup fails when PS is initialized and started with encryption options

    XMLWordPrintable

    Details

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

      Description

      Initialize and start PS8.0.15-4 with following encryption options:

      ./all_no_cl --early-plugin-load=keyring_file.so --keyring_file_data=/home/mchawla/PS8_0_15_4_opt/keyring --binlog-encryption --innodb-undo-log-encrypt --innodb-redo-log-encrypt --innodb_encrypt_tables=ON --innodb_encrypt_online_alter_logs=ON --innodb_temp_tablespace_encrypt=ON --log-bin=mysql-bin --log-slave-updates --gtid-mode=ON --enforce-gtid-consistency --binlog-format=row --master_verify_checksum=ON --binlog_checksum=CRC32 --encrypt-tmp-files

      Add encrypted tables data
      Take full backup

      ./xtrabackup --user=root --password='' --backup --target-dir=$HOME/dbbackup_PS8/full -S $HOME/PS8_0_15_4_opt/socket.sock --datadir=$HOME/PS8_0_15_4_opt/data --keyring_file_data=$HOME/PS8_0_15_4_opt/keyring --xtrabackup-plugin-dir=$HOME/pxb_8_0_5_debug/lib/plugin

      Full backup fails and PXB displays a crash

      190225 09:20:55 [01] Copying ./mysql.ibd to /home/mchawla/dbbackup_PS8/full/mysql.ibd
      09:20:55 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 = 0 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)+0x43) [0x4313e45]
      ./xtrabackup(handle_fatal_signal+0x3e3) [0x2ec5530]
      /usr/lib64/libpthread.so.0(+0xf5d0) [0x7fb322ca45d0]
      /usr/lib64/libcrypto.so.10(aesni_cbc_encrypt+0x827) [0x7fb32198d2e7]
      Please report a bug at https://jira.percona.com/projects/PXB

      Note: PXB also displays a crash when full backup is taken without keyring plugin options.

        Smart Checklist

          Attachments

            Activity

              People

              • Assignee:
                sergei.glushchenko Sergei Glushchenko
                Reporter:
                manish.chawla Manish Chawla
              • Votes:
                0 Vote for this issue
                Watchers:
                1 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, 16 minutes
                  2h 16m