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

innodb.truncate_restart failed in buildbot, assertion failed

    XMLWordPrintable

Details

    Description

      http://buildbot.askmonty.org/buildbot/builders/kvm-fulltest2/builds/10523/steps/mtr_nm/logs/stdio

      innodb.truncate_restart 'innodb'         w4 [ fail ]  Found warnings/errors in server log file!
              Test ended at 2017-11-24 06:06:52
      line
      mysqld: /home/buildbot/buildbot/build/mariadb-10.2.11/storage/innobase/trx/trx0purge.cc:305: void trx_purge_add_update_undo_to_history(trx_t*, ib_page_t*, mtr_t*): Assertion `srv_undo_sources || ((srv_startup_is_before_trx_rollback_phase || trx_rollback_or_clean_is_active) && purge_sys->state == PURGE_STATE_INIT) || (srv_force_recovery >= SRV_FORCE_NO_BACKGROUND && purge_sys->state == PURGE_STATE_DISABLED) || ((trx->undo_no == 0 || trx->in_mysql_trx_list) && srv_fast_shutdown)' failed.
      Attempting backtrace. You can use the following information to find out
      ^ Found warnings in /mnt/buildbot/build/mariadb-10.2.11/mysql-test/var/4/log/mysqld.1.err
      

      http://buildbot.askmonty.org/buildbot/builders/kvm-fulltest2/builds/10523/steps/mtr_nm/logs/mysqld.1.err.4

      2017-11-24  6:06:53 2956729152 [Note] /mnt/buildbot/build/mariadb-10.2.11/sql/mysqld (root[root] @ localhost []): Normal shutdown
       
      2017-11-24  6:06:53 2956729152 [Note] Event Scheduler: Purging the queue. 0 events
      2017-11-24  6:06:53 2849987392 [Note] InnoDB: FTS optimize thread exiting.
      mysqld: /home/buildbot/buildbot/build/mariadb-10.2.11/storage/innobase/trx/trx0purge.cc:305: void trx_purge_add_update_undo_to_history(trx_t*, ib_page_t*, mtr_t*): Assertion `srv_undo_sources || ((srv_startup_is_before_trx_rollback_phase || trx_rollback_or_clean_is_active) && purge_sys->state == PURGE_STATE_INIT) || (srv_force_recovery >= SRV_FORCE_NO_BACKGROUND && purge_sys->state == PURGE_STATE_DISABLED) || ((trx->undo_no == 0 || trx->in_mysql_trx_list) && srv_fast_shutdown)' failed.
      171124  6:06: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.11-MariaDB-debug-log
      key_buffer_size=1048576
      read_buffer_size=131072
      max_used_connections=2
      max_threads=153
      thread_count=3
      It is possible that mysqld could use up to 
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 61898 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
       
      Thread pointer: 0xa8a05dd8
      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 = 0xb136a2a0 thread_stack 0x49000
      /mnt/buildbot/build/mariadb-10.2.11/sql/mysqld(my_print_stacktrace+0x32)[0x8cf2ea2]
      /mnt/buildbot/build/mariadb-10.2.11/sql/mysqld(handle_fatal_signal+0x3c7)[0x85a526b]
      [0xb76ec400]
      [0xb76ec424]
      /lib/i386-linux-gnu/libc.so.6(gsignal+0x4f)[0xb71c81ef]
      /lib/i386-linux-gnu/libc.so.6(abort+0x175)[0xb71cb835]
      /lib/i386-linux-gnu/libc.so.6(+0x27095)[0xb71c1095]
      /lib/i386-linux-gnu/libc.so.6(+0x27147)[0xb71c1147]
      /mnt/buildbot/build/mariadb-10.2.11/sql/mysqld[0x8a86039]
      /mnt/buildbot/build/mariadb-10.2.11/sql/mysqld[0x8abd356]
      /mnt/buildbot/build/mariadb-10.2.11/sql/mysqld[0x8aab4c5]
      /mnt/buildbot/build/mariadb-10.2.11/sql/mysqld[0x8aacdac]
      /mnt/buildbot/build/mariadb-10.2.11/sql/mysqld[0x8aacf61]
      /mnt/buildbot/build/mariadb-10.2.11/sql/mysqld[0x8aad823]
      /mnt/buildbot/build/mariadb-10.2.11/sql/mysqld[0x8b9064f]
      /mnt/buildbot/build/mariadb-10.2.11/sql/mysqld[0x8b94c4c]
      mysys/stacktrace.c:267(my_print_stacktrace)[0x8b96a10]
      sql/signal_handler.cc:168(handle_fatal_signal)[0x8a2c858]
      trx/trx0undo.cc:1757(trx_undo_update_cleanup(trx_t*, unsigned char*, mtr_t*))[0x8a2e5a1]
      trx/trx0trx.cc:1463(trx_write_serialisation_history)[0x88bd601]
      row/row0trunc.cc:1278(row_truncate_complete)[0x85afa23]
      handler/ha_innodb.cc:13565(ha_innobase::truncate())[0x8766c3c]
      sql/handler.cc:4079(handler::ha_truncate())[0x876729c]
      sql/sql_truncate.cc:498(Sql_cmd_truncate_table::execute(THD*))[0x876741b]
      /mnt/buildbot/build/mariadb-10.2.11/sql/mysqld(_Z21mysql_execute_commandP3THD+0xb516)[0x8348453]
      sql/sql_parse.cc:6197(mysql_execute_command(THD*))[0x834ccd4]
      sql/sql_parse.cc:1807(dispatch_command(enum_server_command, THD*, char*, unsigned int, bool, bool))[0x833a0c3]
      sql/sql_parse.cc:1360(do_command(THD*))[0x8338a77]
      sql/sql_connect.cc:1354(do_handle_one_connection(CONNECT*))[0x8479210]
      sql/sql_connect.cc:1261(handle_one_connection)[0x8478f9e]
      perfschema/pfs.cc:1865(pfs_spawn_thread)[0x87b70a0]
      /lib/i386-linux-gnu/libpthread.so.0(+0x6d4c)[0xb7474d4c]
      /lib/i386-linux-gnu/libc.so.6(clone+0x5e)[0xb7284ace]
       
      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort.
      Query (0xa8a173a0): TRUNCATE TABLE t1
      Connection ID (thread ID): 10
      Status: KILL_SERVER
      

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              alice Alice Sherepa
              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.