Emergency

Getting "InnoDB: Encryption algorithm support missing: N"

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Getting "InnoDB: Encryption algorithm support missing: N"

    Hi all,
    For some reason when restoring db and then applying logs I am getting "InnoDB: Encryption algorithm support missing: N" couldn't find anything about this message.
    BTW, the apply-log succeed.

    BR

  • #2
    Hi,
    Could you please share more information?
    What is server and xtrabackup version? What are in my.cnf? Are there any special conditions?
    What was the backup and prepare command exactly?

    Comment


    • #3
      Hi,
      Version

      Code:
      xtrabackup version 2.4.4 based on MySQL server 5.7.13 Linux (x86_64) (revision id: df58cf2)
      My cnf file:

      Code:
      # Generated by Chef
      # Local modifications will be overwritten. mysql 57 test
      # Cookbook:
      # Template: my.cnf.erb
      ########################################################################
      [client]
      port   = 3306
      socket = /var/run/mysqld/mysqld_db1.sock
      
      [mysqld_safe]
      socket            = /var/run/mysqld/mysqld_db1.sock
      nice              = 0
      open-files-limit  = 16384
      
      # *** Application-specific options follow here ***
      #
      # The MySQL server
      #
      [mysqld]
      
      #
      # * Basic Settings
      #
      user                      = mysql
      pid-file                  = /var/run/mysqld/mysqld_db1.pid
      socket                    = /var/run/mysqld/mysqld_db1.sock
      port                      = 3306
      basedir                   = /usr
      datadir                   = /var/lib/mysql/db1/data
      tmpdir                    = /var/lib/mysql/db1/tmp
      innodb_log_group_home_dir = /var/lib/mysql/db1/journal
      
      thread_concurrency      = 12
      innodb_file_format = Barracuda
      language = /usr/share/mysql/english
      innodb_additional_mem_pool_size = 32M
      
      
      skip-name-resolve
      skip-external-locking
      
      net_read_timeout  = 120
      net_write_timeout = 120
      net_retry_count   = 10
      net_buffer_length = 16384
      
      bind-address  = 10.10.10.1
      report-host   = mysql-host1
      
      character_set_server = utf8
      collation_server     = utf8_general_ci
      
      max_allowed_packet      = 512M
      thread_stack            = 192K
      query_alloc_block_size  = 16K
      transaction_isolation   = REPEATABLE-READ
      tmp_table_size          = 64M
      default_storage_engine  = InnoDB
      max_heap_table_size     = 64M
      sort_buffer_size        = 8M
      join_buffer_size        = 8M
      thread_cache_size       = 256
      back_log                = 50
      max_connections         = 1024
      max_connect_errors      = 9999999
      table_open_cache        = 8192
      query_cache_size        = 0
      query_cache_type        = 0
      query_cache_limit       = 2M
      
      # * Logging and Replication
      #
      general_log      = 0
      general_log_file = /var/lib/mysql/db1/log/mysql-host1.general.log
      
      # sync_binlog ensures that all writes to the binary log are immediately
      # flushed to disk.  This is important, especially for replication, because
      # if the server crashes and has not written all of the binary log to disk (and flushed it)
      # then some rows will not make it to the slave
      sync_binlog               = 1
      slave_compressed_protocol = 1
      
      # Replication Params
      slave-skip-errors = 1032,1062
      
      
      
      
      
      
      log_error             = /var/lib/mysql/db1/log/mysql-host1.err
      slow_query_log        = 1
      slow_query_log_file   = /var/lib/mysql/db1/log/mysql-host1-slow.log
      long_query_time       = 2
      
      
      
      server-id = 154949191919
      
      log_bin          = /var/lib/mysql/db1/binary/mysql-bin
      log_bin_index    = /var/lib/mysql/db1/binary/mysql-bin.index
      expire_logs_days = 10
      max_binlog_size  = 1G
      
      binlog_cache_size = 1M
      
      relay_log       = /var/lib/mysql/db1/relay/relay-bin
      relay_log_index = /var/lib/mysql/db1/relay/relay-bin.index
      relay_log_info_file = /var/lib/mysql/db1/relay/relay-log.info
      
      auto_increment_increment = 1
      auto_increment_offset = 1
      
      log_slave_updates=OFF
      binlog_format=MIXED
      binlog_row_image=MINIMAL
      
      # Enable the full query log. Every query (even ones with incorrect
      # syntax) that the server receives will be logged. This is useful for
      # debugging, it is usually disabled in production use.
      #log
      
      # Log warnings to the error log
      log_warnings = 1
      
      # Log more information in the slow query log. Normally it is good to
      # have this turned on. This will enable logging of queries that are not
      # using indexes in addition to long running queries.
      # this parameter is removed as of mysql5.5
      
      innodb_doublewrite = 1
      
      
      innodb_buffer_pool_size = 16G
      innodb_file_per_table
      innodb_thread_concurrency = 0
      innodb_flush_log_at_trx_commit = 2
      innodb_fast_shutdown
      innodb_log_buffer_size = 64M
      innodb_log_file_size = 1G
      innodb_log_files_in_group = 3
      innodb_max_dirty_pages_pct = 80
      innodb_flush_method = O_DIRECT
      innodb_lock_wait_timeout = 120
      
      innodb_commit_concurrency  = 0
      innodb_open_files = 2000
      
      [mysqldump]
      quick
      quote-names
      max_allowed_packet = 512M
      net_buffer_length  = 16384
      
      [mysql]
      prompt = \u@\h(mysql-host1):[\d]>\_
      
      !includedir  /etc/mysql/db1_conf.d/

      I am not aware of any special conditions

      My backup script for incremental is :
      Code:
      innobackupex --defaults-file=/etc/mysql/my.cnf --user=root --password=*** --no-lock --safe-slave-backup --slave-info --extra-lsndir=/backup/billing/lsns/2016_09_13__14_17_18 --stream=xbstream --compress --encrypt=AES192 --encrypt-key-file="/backup/mysql/inc/2016_09_13__14_17_18/key" --encrypt-threads=4 --incremental /backup/mysql/inc/2016_09_13__14_17_18 --incremental-lsn="1541031622708"
      My backup command for the full backup is:

      Code:
      innobackupex --defaults-file=/etc/mysql/my.cnf --user=root --password=*** --no-lock --safe-slave-backup --slave-info --extra-lsndir=/backup/billing/lsns/2016_09_13__14_17_18 --stream=xbstream --compress --encrypt=AES192 --encrypt-key-file="/backup/mysql/full/2016_09_13__14_17_18/key" --encrypt-threads=4
      My restore commands are:
      For the full backup
      Code:
      xbstream  -v -x -C /tmp/tmpN1Lfa0/0 /var/lib/mysql/db1/data/
      innobackupex --parallel={} --decrypt=AES192 --decompress --encrypt-key-file=<path to key> /var/lib/mysql/db1/data

      For inc backup:
      Code:
      xbstream  -v -x -C  /tmp/tmpN1Lfa0/1 /tmp/tmpN1Lfa0/1/extract  #It's a temp location
      innobackupex --parallel={} --decrypt=AES192 --decompress --encrypt-key-file=<path to key> /tmp/tmpN1Lfa0/1/extract
      Then applying logs: --IN THIS STAGE AI AM GETTING THE MESSAGES
      Code:
      innobackupex --apply-log --redo-only /var/lib/mysql/data
      
      innobackupex --apply-log --redo-only /var/lib/mysql/db1/data  --incremental-dir=/tmp/tmpzIvrJT/1/extract #for each inc
      
      innobackupex --apply-log  /var/lib/mysql/db1/data
      Last edited by tapuhi; 09-13-2016, 10:41 AM.

      Comment


      • #4
        Thanks.
        And could you please share the xtrabackup's backup/prepare outputs?

        Comment


        • #5
          Hi,
          All the percona mails went to spam and I totally missed all notifications.


          I have the full restore log, not sure which output you need ?

          BR

          Comment


          • #6
            We would need full backup, incremental backup and --apply-log (prepare) commands full outputs to check further.

            Comment


            • #7
              tapuhi is it the data available or not, after apply-log is successful. Even though you encounter the issue "InnoDB: Encryption algorithm support missing: N"

              Comment


              • #8
                I encounter the same issue as tapuhi mentioned.
                xtrabackup version 2.4.8 based on MySQL server 5.7.13 Linux (x86_64) (revision id: 97330f7)

                when i apply-log redo-only for incremental. The table is very big;50,000,000 (50million);
                i don't know how to upload file, it seems that attachments always failed to upload.


                email: windy.jian@qq.com

                Comment

                Working...
                X