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

Assertion `0' failed in Item::val_native_result / Timestamp_or_zero_datetime_native_null::Timestamp_or_zero_datetime_native_null upon mysqld_list_fields after crash recovery

    XMLWordPrintable

Details

    Description

      Note: the failure was observed as an aftermath of MDEV-18402 and MDEV-18401, so it's possible that it's a garbage-in-garbage-out situation. However, I don't have test cases for these two bugs yet, while this after-recovery failure is reproducible on their datasets, so it might be worth checking independently anyway.

      10.4 4007eab

      mysqld: /data/src/10.4/sql/item.h:1330: virtual bool Item::val_native(THD*, Native*): Assertion `0' failed.
      190129  3:47:32 [ERROR] mysqld got signal 6 ;
       
      #7  0x00007f58f5cc7ee2 in __assert_fail () from /lib/x86_64-linux-gnu/libc.so.6
      #8  0x0000559e90b7c604 in Item::val_native (this=0x7f588817b850, thd=0x7f5888000b00, to=0x7f58e04eda60) at /data/src/10.4/sql/item.h:1330
      #9  0x0000559e90e93958 in Timestamp_or_zero_datetime_native_null::Timestamp_or_zero_datetime_native_null (this=0x7f58e04eda60, thd=0x7f5888000b00, item=0x7f588817b850, conv=false) at /data/src/10.4/sql/sql_type.cc:8155
      #10 0x0000559e90e976c1 in Timestamp_or_zero_datetime_native_null::Timestamp_or_zero_datetime_native_null (this=0x7f58e04eda60, thd=0x7f5888000b00, item=0x7f588817b850) at /data/src/10.4/sql/sql_type.h:2457
      #11 0x0000559e90e8e403 in Type_handler::Item_send_timestamp (this=0x559e923053f0 <type_handler_timestamp2>, item=0x7f588817b850, protocol=0x7f58e04edbe0, buf=0x7f58e04edc80) at /data/src/10.4/sql/sql_type.cc:6704
      #12 0x0000559e90e9a920 in Type_handler_timestamp_common::Item_send (this=0x559e923053f0 <type_handler_timestamp2>, item=0x7f588817b850, protocol=0x7f58e04edbe0, buf=0x7f58e04edc80) at /data/src/10.4/sql/sql_type.h:5465
      #13 0x0000559e90b7c3e0 in Item::send (this=0x7f588817b850, protocol=0x7f58e04edbe0, buffer=0x7f58e04edc80) at /data/src/10.4/sql/item.h:1032
      #14 0x0000559e90b769f0 in Protocol::send_result_set_metadata (this=0x7f58880010c8, list=0x7f58e04ee080, flags=2) at /data/src/10.4/sql/protocol.cc:937
      #15 0x0000559e90d2a98b in mysqld_list_fields (thd=0x7f5888000b00, table_list=0x7f58e04ee3b0, wild=0x7f5888013da8 "") at /data/src/10.4/sql/sql_show.cc:1553
      #16 0x0000559e90c8adc7 in dispatch_command (command=COM_FIELD_LIST, thd=0x7f5888000b00, packet=0x7f588801bfb9 "test\aview_BB\aview_BB\002pk\002pk\f?", packet_length=8, is_com_multi=false, is_next_command=false) at /data/src/10.4/sql/sql_parse.cc:2050
      #17 0x0000559e90c88bd5 in do_command (thd=0x7f5888000b00) at /data/src/10.4/sql/sql_parse.cc:1395
      #18 0x0000559e90df7b67 in do_handle_one_connection (connect=0x559e951c5880) at /data/src/10.4/sql/sql_connect.cc:1398
      #19 0x0000559e90df78e2 in handle_one_connection (arg=0x559e951c5880) at /data/src/10.4/sql/sql_connect.cc:1301
      #20 0x00007f58f799e494 in start_thread (arg=0x7f58e04ef700) at pthread_create.c:333
      #21 0x00007f58f5d8493f in clone () from /lib/x86_64-linux-gnu/libc.so.6
      

      To reproduce, download the datadir from here:
      ftp://ftp.askmonty.org/public/mdev18408-data.tar.gz

      Unpack it and start the server on it, all default options will do.
      It starts seemingly normally, apart from numerous InnoDB notes "Ignoring data file...".
      Then, connect by the command-line client to the database test without -A, or somehow else invoke the corresponding command.

      Attachments

        Issue Links

          Activity

            People

              bar Alexander Barkov
              elenst Elena Stepanova
              Votes:
              1 Vote for this issue
              Watchers:
              3 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.