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

gcol.innodb_virtual_basic fails in buildbot, Failing assertion: cursor->old_rec

    Details

      Description

      http://buildbot.askmonty.org/buildbot/builders/kvm-rpm-centos74-amd64/builds/4044

      gcol.innodb_virtual_basic 'innodb'       w3 [ fail ]
              Test ended at 2018-08-10 15:44:09
       
      CURRENT_TEST: gcol.innodb_virtual_basic
      mysqltest: At line 432: query 'CALL DELETE_insert_t()' failed: 2013: Lost connection to MySQL server during query
       
      The result from queries just before the failure was:
      < snip >
      UPDATE t SET a = REPEAT(CAST(1 AS CHAR), 1000) WHERE h = 1;
      CREATE PROCEDURE UPDATE_t()
      begin
      DECLARE i INT DEFAULT 1;
      WHILE (i <= 200) DO
      UPDATE t SET a = REPEAT(CAST(i AS CHAR), 2000) WHERE h = 1;
      SET i = i + 1;
      END WHILE;
      END|
      CREATE PROCEDURE DELETE_insert_t()
      begin
      DECLARE i INT DEFAULT 1;
      WHILE (i <= 200) DO
      DELETE FROM t WHERE h = 1;
      INSERT INTO t VALUES (REPEAT(CAST(i AS CHAR), 2000) ,  REPEAT('b', 2000), DEFAULT, DEFAULT, DEFAULT, 1);
      SET i = i + 1;
      END WHILE;
      END|
      CALL UPDATE_t();
      CALL DELETE_insert_t();
       
      More results from queries before failure can be found in /dev/shm/var/3/log/innodb_virtual_basic.log
       
       
      Server [mysqld.1 - pid: 24469, winpid: 24469, exit: 256] failed during test run
      Server log from this test:
      ----------SERVER LOG START-----------
      2018-08-10 15:44:06 0x7f677affd700  InnoDB: Assertion failure in file /home/buildbot/buildbot/padding_for_CPACK_RPM_BUILD_SOURCE_DIRS_PREFIX/mariadb-10.2.17/storage/innobase/btr/btr0pcur.cc line 273
      InnoDB: Failing assertion: cursor->old_rec
      InnoDB: We intentionally generate a memory trap.
      InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
      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: https://mariadb.com/kb/en/library/xtradbinnodb-recovery-modes/
      InnoDB: about forcing recovery.
      180810 15:44:06 [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.17-MariaDB-log
      key_buffer_size=1048576
      read_buffer_size=131072
      max_used_connections=2
      max_threads=153
      thread_count=8
      It is possible that mysqld could use up to 
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 63022 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
       
      Thread pointer: 0x7f674c0009a8
      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 = 0x7f677affcc30 thread_stack 0x49000
      /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x55b243beb42e]
      /usr/sbin/mysqld(handle_fatal_signal+0x355)[0x55b243669125]
      sigaction.c:0(__restore_rt)[0x7f679dcfc5e0]
      :0(__GI_raise)[0x7f679c2091f7]
      :0(__GI_abort)[0x7f679c20a8e8]
      /usr/sbin/mysqld(+0x429928)[0x55b243418928]
      /usr/sbin/mysqld(+0x9e7c76)[0x55b2439d6c76]
      ut/ut0rbt.cc:221(rbt_tree_add_child(ib_rbt_t const*, ib_rbt_bound_t*, ib_rbt_node_t*) [clone .isra.4] [clone .part.5])[0x55b243929f53]
      btr/btr0pcur.cc:251(btr_pcur_restore_position_func(unsigned long, btr_pcur_t*, char const*, unsigned int, mtr_t*))[0x55b24392ae32]
      row/row0purge.cc:724(row_purge_step(que_thr_t*))[0x55b24392c4ee]
      que/que0que.cc:1049(que_run_threads(que_thr_t*))[0x55b2438e8164]
      include/my_atomic.h:274(srv_worker_thread)[0x55b24395bf1c]
      pthread_create.c:0(start_thread)[0x7f679dcf4e25]
      /lib64/libc.so.6(clone+0x6d)[0x7f679c2cc34d]
       
      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort.
      Query (0x0): 
      Connection ID (thread ID): 5
      Status: NOT_KILLED
       
      Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on
       
      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 at /dev/shm/var/3/mysqld.1/data/
      ----------SERVER LOG END-------------
      

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                serg Sergei Golubchik
                Reporter:
                elenst Elena Stepanova
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated: