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

encryption.innodb_onlinealter_encryption failed in buildbot, SIGABRT on server restart

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Won't Fix
    • 10.2
    • N/A
    • Tests
    • None

    Description

      http://buildbot.askmonty.org/buildbot/builders/kvm-zyp-sles114-x86/builds/2684

      encryption.innodb_onlinealter_encryption 'cbc,innodb' w3 [ fail ]
              Test ended at 2018-09-18 07:42:21
       
      CURRENT_TEST: encryption.innodb_onlinealter_encryption
      mysqltest: In included file "./include/wait_until_connected_again.inc": 
      included from ./include/start_mysqld.inc at line 18:
      included from /usr/share/mysql-test/suite/encryption/t/innodb_onlinealter_encryption.test at line 136:
      At line 23: Server failed to restart
       
      The result from queries just before the failure was:
      < snip >
        `a` varchar(255) DEFAULT NULL,
        `b` int(11) DEFAULT 2,
        PRIMARY KEY (`id`),
        KEY `a` (`a`),
        KEY `b` (`b`)
      ) ENGINE=InnoDB DEFAULT CHARSET=latin1 ROW_FORMAT=COMPRESSED `encrypted`=yes
      # t1 yes on expecting NOT FOUND
      NOT FOUND /foobar/ in t1.ibd
      # t2 ... on expecting NOT FOUND
      NOT FOUND /tempsecret/ in t2.ibd
      # t3 ... on expecting NOT FOUND
      NOT FOUND /barfoo/ in t3.ibd
      # t4 ... on expecting NOT FOUND
      NOT FOUND /repeat/ in t4.ibd
      # t5 ... on expecting NOT FOUND
      NOT FOUND /author/ in t5.ibd
      # t6 ... on expecting NOT FOUND
      NOT FOUND /mangled/ in t6.ibd
      # t7 ... on expecting NOT FOUND
      NOT FOUND /mysql/ in t7.ibd
       
      More results from queries before failure can be found in /dev/shm/var/3/log/innodb_onlinealter_encryption.log
      

      According to the error log, the server crashed with SIGABRT after second restart. Please note that it's not a hang/timeout issue which sometimes happens, because there is no 1-2 min delay between the attempt to start and the crash, it happened immediately:

      2018-09-18  7:33:55 3072423632 [Note] Plugin 'INNODB_SYS_TABLESPACES' is disabled.
      2018-09-18  7:33:55 3072423632 [Note] Plugin 'INNODB_TABLESPACES_SCRUBBING' is disabled.
      2018-09-18  7:33:55 3072423632 [Note] Plugin 'INNODB_SYS_SEMAPHORE_WAITS' is disabled.
      2018-09-18  7:33:55 3072423632 [Warning] /usr/sbin/mysqld: unknown variable 'loose-feedback-debug-startup-interval=20'
      2018-09-18  7:33:55 3072423632 [Warning] /usr/sbin/mysqld: unknown variable 'loose-feedback-debug-first-interval=60'
      2018-09-18  7:33:55 3072423632 [Warning] /usr/sbin/mysqld: unknown variable 'loose-feedback-debug-interval=60'
      2018-09-18  7:33:55 3072423632 [Warning] /usr/sbin/mysqld: unknown option '--loose-pam-debug'
      2018-09-18  7:33:55 3072423632 [Warning] /usr/sbin/mysqld: unknown variable 'loose-debug-sync-timeout=300'
      180918  7:33:55 [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.18-MariaDB-log
      key_buffer_size=1048576
      read_buffer_size=131072
      max_used_connections=0
      max_threads=153
      thread_count=5
      It is possible that mysqld could use up to 
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 61845 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
      

      Attachments

        Activity

          People

            Unassigned Unassigned
            elenst Elena Stepanova
            Votes:
            0 Vote for this issue
            Watchers:
            2 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.