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

Server crashed in find_per_thread_mutex_class_wait_stat, rpl.rpl_row_index_choice failed in buildbot

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 5.5
    • Fix Version/s: 5.5
    • Component/s: Replication, Tests
    • Labels:
      None

      Description

      http://buildbot.askmonty.org/buildbot/builders/kvm-fulltest2/builds/8840/steps/test_3/logs/stdio

      CURRENT_TEST: rpl.rpl_row_index_choice
      mysqltest: At line 150: failed in 'select master_pos_wait('master-bin.000001', 102603, 300)': 2013: Lost connection to MySQL server during query
       
      The result from queries just before the failure was:
      < snip >
      DROP TABLE t2;
      CREATE TABLE t2 (a INT NOT NULL, b INT NOT NULL, c INT NOT NULL, d INT NOT NULL,
      KEY expected_key(b),
      KEY wrong_key7(d),
      KEY wrong_key8(c)) ENGINE=myisam;
      INSERT INTO t2 SELECT d DIV 10, d MOD 41, d MOD 37, d FROM t1;
      # Slave will crash if using the wrong or no index
      SET GLOBAL debug_dbug="+d,slave_crash_if_wrong_index,slave_crash_if_table_scan";
      UPDATE t2 SET d=10042 WHERE d=42;
      DELETE FROM t2 WHERE d=53;
      SET GLOBAL debug_dbug="";
      SELECT * FROM t2 WHERE d IN (10042,53);
      a	b	c	d
      4	1	5	10042
      DROP TABLE t2;
      CREATE TABLE t2 (a INT NOT NULL, b INT NOT NULL, c INT NOT NULL, d INT,
      UNIQUE wrong_key9(d),
      KEY wrong_key10(a),
      PRIMARY KEY expected_key(c,b)) ENGINE=innodb;
      INSERT INTO t2 SELECT d DIV 10, d MOD 41, d MOD 37, d FROM t1;
       
      More results from queries before failure can be found in /mnt/buildbot/build/mariadb-5.5.57/mysql-test/var/2/log/rpl_row_index_choice.log
       
       
      Server [mysqld.2 - pid: 25863, winpid: 25863, exit: 256] failed during test run
      Server log from this test:
      ----------SERVER LOG START-----------
      170718 14:13:46 [Note] 'CHANGE MASTER TO executed'. Previous state master_host='127.0.0.1', master_port='16040', master_log_file='', master_log_pos='4'. New state master_host='127.0.0.1', master_port='16040', master_log_file='master-bin.000001', master_log_pos='4'.
      170718 14:13:46 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000001' at position 4, relay log './slave-relay-bin.000001' position: 4
      170718 14:13:46 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:16040',replication started in log 'master-bin.000001' at position 4
      170718 14:13:47 [ERROR] 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.
       
      To report this bug, see http://kb.askmonty.org/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: 5.5.57-MariaDB-debug
      key_buffer_size=1048576
      read_buffer_size=131072
      max_used_connections=5
      max_threads=153
      thread_count=4
      It is possible that mysqld could use up to 
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 61511 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 0x48000
      mysys/stacktrace.c:246(my_print_stacktrace)[0x88dcdd4]
      sql/signal_handler.cc:155(handle_fatal_signal)[0x83d8edf]
      [0xb76ee400]
      dbug/dbug.c:2141(_db_flush_)[0x88f7391]
      perfschema/pfs_instr.cc:298(find_per_thread_mutex_class_wait_stat(PFS_thread*, PFS_mutex_class*))[0x8556289]
      perfschema/pfs.cc:1635(end_mutex_wait_v1)[0x8566a35]
      /mnt/buildbot/build/mariadb-5.5.57/mysql-test/var/2/plugins/ha_innodb.so(+0x15f489)[0xb475b489]
      /mnt/buildbot/build/mariadb-5.5.57/mysql-test/var/2/plugins/ha_innodb.so(+0x1635ae)[0xb475f5ae]
      /mnt/buildbot/build/mariadb-5.5.57/mysql-test/var/2/plugins/ha_innodb.so(+0x1637ca)[0xb475f7ca]
      /mnt/buildbot/build/mariadb-5.5.57/mysql-test/var/2/plugins/ha_innodb.so(+0x163936)[0xb475f936]
      /mnt/buildbot/build/mariadb-5.5.57/mysql-test/var/2/plugins/ha_innodb.so(+0x1130b7)[0xb470f0b7]
      /mnt/buildbot/build/mariadb-5.5.57/mysql-test/var/2/plugins/ha_innodb.so(+0x1132c6)[0xb470f2c6]
      /mnt/buildbot/build/mariadb-5.5.57/mysql-test/var/2/plugins/ha_innodb.so(+0x1133f0)[0xb470f3f0]
      /mnt/buildbot/build/mariadb-5.5.57/mysql-test/var/2/plugins/ha_innodb.so(+0x1a1962)[0xb479d962]
      /mnt/buildbot/build/mariadb-5.5.57/mysql-test/var/2/plugins/ha_innodb.so(+0x18eb69)[0xb478ab69]
      /mnt/buildbot/build/mariadb-5.5.57/mysql-test/var/2/plugins/ha_innodb.so(+0x18f23f)[0xb478b23f]
      /lib/i386-linux-gnu/libpthread.so.0(+0x6d4c)[0xb7678d4c]
      /lib/i386-linux-gnu/libc.so.6(clone+0x5e)[0xb7487ace]
      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.
      Writing a core file
      ----------SERVER LOG END-------------
       
       
       - saving '/mnt/buildbot/build/mariadb-5.5.57/mysql-test/var/2/log/rpl.rpl_row_index_choice-innodb_plugin,row/' to '/mnt/buildbot/build/mariadb-5.5.57/mysql-test/var/log/rpl.rpl_row_index_choice-innodb_plugin,row/'
       
      Retrying test rpl.rpl_row_index_choice, attempt(2/3)...
       
      worker[2] > Restart  - not started
      worker[2] > Restart  - not started
      ***Warnings generated in error logs during shutdown after running tests: rpl.rpl_row_func003 rpl.rpl_row_drop_create_temp_table rpl.rpl_row_index_choice rpl.rpl_row_implicit_commit_binlog rpl.rpl_row_idempotency rpl.rpl_row_blob_innodb
       
      170718 14:13:47 [ERROR] mysqld got signal 11 ;
      

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            elenst Elena Stepanova
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:

                Git Integration

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