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

Crash when enabling encryption on Slave

    XMLWordPrintable

Details

    Description

      I've got this crash, working on reproduction steps

      2017-04-27 17:11:35 140015867094784 [Note] /home/a/mariadb-environs/m1-10.2.5/../_depot/m-tar/10.2.5/bin/mysqld: Shutdown complete
       
      2017-04-27 17:11:53 140001983624704 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
      2017-04-27 17:11:53 140001983624704 [Note] InnoDB: Uses event mutexes
      2017-04-27 17:11:53 140001983624704 [Note] InnoDB: Compressed tables use zlib 1.2.3
      2017-04-27 17:11:53 140001983624704 [Note] InnoDB: Using Linux native AIO
      2017-04-27 17:11:53 140001983624704 [Note] InnoDB: Number of pools: 1
      2017-04-27 17:11:53 140001983624704 [Note] InnoDB: Using SSE2 crc32 instructions
      2017-04-27 17:11:53 140001983624704 [Note] InnoDB: Initializing buffer pool, total size = 4G, instances = 8, chunk size = 128M
      2017-04-27 17:11:53 140001983624704 [Note] InnoDB: Completed initialization of buffer pool
      2017-04-27 17:11:53 139996821378816 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
      2017-04-27 17:11:53 140001983624704 [Note] InnoDB: Highest supported file format is Barracuda.
      2017-04-27 17:11:53 140001983624704 [Note] InnoDB: S: (0x0B0F05010D06080B01070A060003030A0E050B02050C07050C09090D0F0F060B02080201050607070506080704010E07000F0B0B0D0B05000D000200060801070B03050D0E0C0D0D010102020B09060C050B090205080C0D0707070D060B0E0900020D00040C0D0F0D090706020B0B0C0805080F0D0B060D02040F020A050600070B090A0F0E050002050D050E0107000D000605040E01010302080A040E0B040F030E0C0D03090B080C090F00070F0B020803010C0B0C06050903050D050B000C0B0F0E060B09060E0B0B0D0F0A060A0B090C00070A0B08090809050F0F0E020B080200040E010A090B0E0E030B0E09030A050102090C03030102000800000A030D08020D090F000A030A0B0C0A0605010F000707080406070504090E010C010B0F0A00040301020B050B0500060904000409060C0E08030A0E08080301020707090206050C08090B09060F07080A000D09010E010F0F04070A0107030706070809080C090D00070E0F09000B08040609060D0403090B0F0E070A030C080700030A030D0C02030E0202020F01060A06080A090304000B0805060E0B090F060B0D0304060B0B0A0E0305010C0B0C02010F010E04070E02050B0B0207050A01010B0B0809050B03070F05010E0C060C09020B030102090F0804070C060A0D030C080B040603000508080507010D0C0107010F010B040406070
      2017-04-27 17:11:53 140001983624704 [Note] InnoDB: c: (0x010F000A0000000000020E000C000400020E000E000F0400020F0002000F0F0F0F0200020F0006000400020F0008000F0F0F0F0200020F000C000400020F000E000F040002000002000F0F0F0F02000200000600040002000008000F0F0F0F02000200000C0004000200000E000F0200010A0E0A00040002030002000F0F0F0F02000203000600040002030008000F0F0F0F02000203000C0004000203000E000400020C0002000F0F0F0F0100000104000A0100000104000A040000000A01090800020C000200000000000400020C000E000A050C0304000203000A000F0200020D0000000400010B0C0E000F0F0F0F010000020E000A010000020E000A040000000A01080F0400010B0C0A000F0F0F0F010000020E000E010000020E000E040000000A01070F0400010B0C06000F0F0F0F010000020D000B010000020D000B040000000A01060F04000D0002000F0F0F0F02000D00060004000D0008000F0F0F0F02000D000C0004000D000E000400010B0C02000F0F0F0F010000020D000F010000020D000F040000000A01050800010B0C0200000000000400010B0C0E000A050C0304000D000A000F000303020C0D0D0501050107090503070D090402010F0C080202010004000200020900040F04080B06050A0B060409080803050F020D02020D030D0A0C09080F0500020A080706000B04040E040
      2017-04-27 17:11:53 140001983624704 [Note] InnoDB: S: (0x0B0F05010D06080B01070A060003030A0E050B02050C07050C09090D0F0F060B02080201050607070506080704010E07000F0B0B0D0B05000D000200060801070B03050D0E0C0D0D010102020B09060C050B090205080C0D0707070D060B0E0900020D00040C0D0F0D090706020B0B0C0805080F0D0B060D02040F020A050600070B090A0F0E050002050D050E0107000D000605040E01010302080A040E0B040F030E0C0D03090B080C090F00070F0B020803010C0B0C06050903050D050B000C0B0F0E060B09060E0B0B0D0F0A060A0B090C00070A0B08090809050F0F0E020B080200040E010A090B0E0E030B0E09030A050102090C03030102000800000A030D08020D090F000A030A0B0C0A0605010F000707080406070504090E010C010B0F0A00040301020B050B0500060904000409060C0E08030A0E08080301020707090206050C08090B09060F07080A000D09010E010F0F04070A0107030706070809080C090D00070E0F09000B08040609060D0403090B0F0E070A030C080700030A030D0C02030E0202020F01060A06080A090304000B0805060E0B090F060B0D0304060B0B0A0E0305010C0B0C02010F010E04070E02050B0B0207050A01010B0B0809050B03070F05010E0C060C09020B030102090F0804070C060A0D030C080B040603000508080507010D0C0107010F010B040406070
      2017-04-27 17:11:53 140001983624704 [Note] InnoDB: c: (0x010F000A0000000000020E000C000400020E000E000F0400020F0002000F0F0F0F0200020F0006000400020F0008000F0F0F0F0200020F000C000400020F000E000F040002000002000F0F0F0F02000200000600040002000008000F0F0F0F02000200000C0004000200000E000F0200010A0E0A00040002030002000F0F0F0F02000203000600040002030008000F0F0F0F02000203000C0004000203000E000400020C0002000F0F0F0F0100000104000A0100000104000A040000000A01090800020C000200000000000400020C000E000A050C0304000203000A000F0200020D0000000400010B0C0E000F0F0F0F010000020E000A010000020E000A040000000A01080F0400010B0C0A000F0F0F0F010000020E000E010000020E000E040000000A01070F0400010B0C06000F0F0F0F010000020D000B010000020D000B040000000A01060F04000D0002000F0F0F0F02000D00060004000D0008000F0F0F0F02000D000C0004000D000E000400010B0C02000F0F0F0F010000020D000F010000020D000F040000000A01050800010B0C0200000000000400010B0C0E000A050C0304000D000A000F000303020C0D0D0501050107090503070D090402010F0C080202010004000200020900040F04080B06050A0B060409080803050F020D02020D030D0A0C09080F0500020A080706000B04040E040
      2017-04-27 17:11:53 140001983624704 [ERROR] InnoDB: The page [page id: space=0, page number=6] in file innodb_system cannot be decrypted.
      2017-04-27 17:11:53 140001983624704 [Note] InnoDB: However key management plugin or used key_version 1 is not found or used encryption algorithm or method does not match.
      2017-04-27 17:11:53 0x7f54c0807600  InnoDB: Assertion failure in file /home/buildbot/buildbot/build/storage/innobase/buf/buf0buf.cc line 6088
      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.
      170427 17:11:53 [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.5-MariaDB
      key_buffer_size=134217728
      read_buffer_size=131072
      max_used_connections=0
      max_threads=153
      thread_count=0
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467200 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
      /home/a/mariadb-environs/m1-10.2.5/../_depot/m-tar/10.2.5/bin/mysqld(my_print_stacktrace+0x2e)[0xdd68de]
      /home/a/mariadb-environs/m1-10.2.5/../_depot/m-tar/10.2.5/bin/mysqld(handle_fatal_signal+0x444)[0x7d2454]
      /lib/x86_64-linux-gnu/libpthread.so.0(+0x11630)[0x7f54c03f8630]
      /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x9f)[0x7f54bf17e7ef]
      /lib/x86_64-linux-gnu/libc.so.6(abort+0x16a)[0x7f54bf1803ea]
      /home/a/mariadb-environs/m1-10.2.5/../_depot/m-tar/10.2.5/bin/mysqld[0xb626d3]
      /home/a/mariadb-environs/m1-10.2.5/../_depot/m-tar/10.2.5/bin/mysqld[0xbb2578]
      /home/a/mariadb-environs/m1-10.2.5/../_depot/m-tar/10.2.5/bin/mysqld[0xbd5c02]
      /home/a/mariadb-environs/m1-10.2.5/../_depot/m-tar/10.2.5/bin/mysqld[0xbd6fa9]
      /home/a/mariadb-environs/m1-10.2.5/../_depot/m-tar/10.2.5/bin/mysqld[0xbb6c59]
      /home/a/mariadb-environs/m1-10.2.5/../_depot/m-tar/10.2.5/bin/mysqld[0xb44276]
      /home/a/mariadb-environs/m1-10.2.5/../_depot/m-tar/10.2.5/bin/mysqld[0xb44be9]
      /home/a/mariadb-environs/m1-10.2.5/../_depot/m-tar/10.2.5/bin/mysqld[0xb55d52]
      /home/a/mariadb-environs/m1-10.2.5/../_depot/m-tar/10.2.5/bin/mysqld[0xb4a77b]
      /home/a/mariadb-environs/m1-10.2.5/../_depot/m-tar/10.2.5/bin/mysqld[0xb196b8]
      /home/a/mariadb-environs/m1-10.2.5/../_depot/m-tar/10.2.5/bin/mysqld[0x9dbce6]
      /home/a/mariadb-environs/m1-10.2.5/../_depot/m-tar/10.2.5/bin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x5e)[0x7d7bfe]
      /home/a/mariadb-environs/m1-10.2.5/../_depot/m-tar/10.2.5/bin/mysqld[0x5fb46a]
      /home/a/mariadb-environs/m1-10.2.5/../_depot/m-tar/10.2.5/bin/mysqld(_Z11plugin_initPiPPci+0xbc0)[0x5fddc0]
      /home/a/mariadb-environs/m1-10.2.5/../_depot/m-tar/10.2.5/bin/mysqld[0x549fcd]
      /home/a/mariadb-environs/m1-10.2.5/../_depot/m-tar/10.2.5/bin/mysqld(_Z11mysqld_mainiPPc+0xa08)[0x54b358]
      /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7f54bf1693f1]
      /home/a/mariadb-environs/m1-10.2.5/../_depot/m-tar/10.2.5/bin/mysqld(__gxx_personality_v0+0x3d1)[0x5406d9]
      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.
      

      Attachments

        Activity

          People

            jplindst Jan Lindström (Inactive)
            anikitin Andrii Nikitin (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Git Integration

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