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

Server Crash on Update with joins

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Duplicate
    • Affects Version/s: 5.5.45, 10.0.21, 10.1.7, 5.5, 10.0, 10.1
    • Fix Version/s: 5.5.47
    • Labels:
    • Environment:
      CentOS 7.1 64-bit, running inside VirtualBox
    • Sprint:
      10.1.9-2

      Description

      I've seen there are other bugs which have similar titles, but every one has been marked as closed, and since I've verified this with the 3 latest versions available for my distribution, I'm reporting it as a new bug. This was found trying to run CloudStack.

      Whenever the following query is executed, the server crashes:

      UPDATE `cloud`.`configuration` SET value = CONCAT("*.",(SELECT `temptable`.`value` FROM (SELECT * FROM `cloud`.`configuration` WHERE `name`="consoleproxy.url.domain") AS `temptable` WHERE `temptable`.`name`="consoleproxy.url.domain")) WHERE `name`="consoleproxy.url.domain";

      I've cut the database in question down to the absolute minimum:

      CREATE TABLE `configuration` (
        `name` varchar(255) NOT NULL,
        `value` varchar(4095) DEFAULT NULL,
        PRIMARY KEY (`name`)
      );

      Tested on a clean CentOS7.1 64bit install (running under VirtualBox, provisioned with vagrant using bento/centos-7.1)

      The contents of the error log are as follows:

      151013 11:00:25 [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.45-MariaDB
      key_buffer_size=134217728
      read_buffer_size=131072
      max_used_connections=1
      max_threads=153
      thread_count=1
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 466712 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
       
      Thread pointer: 0x0x7fe313239000
      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 = 0x7fe32f557d80 thread_stack 0x48000
      /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0xac241e]
      /usr/sbin/mysqld(handle_fatal_signal+0x390)[0x6e20f0]
      /lib64/libpthread.so.0(+0xf130)[0x7fe32f1a2130]
      /usr/sbin/mysqld[0x5ceb80]
      /usr/sbin/mysqld[0x5ced80]
      /usr/sbin/mysqld[0x5d137a]
      /usr/sbin/mysqld[0x5d3a6b]
      /usr/sbin/mysqld[0x5ec6d7]
      /usr/sbin/mysqld(_ZN4JOIN8optimizeEv+0x6ed)[0x5f0d8d]
      /usr/sbin/mysqld(_ZN13st_select_lex31optimize_unflattened_subqueriesEb+0x90)[0x59ada0]
      /usr/sbin/mysqld(_Z12mysql_updateP3THDP10TABLE_LISTR4ListI4ItemES6_PS4_jP8st_ordery15enum_duplicatesbPySB_+0x37c)[0x631e9c]
      /usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x3c0d)[0x5aa2fd]
      /usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x11e)[0x5ad00e]
      /usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x1729)[0x5aef69]
      /usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x20b)[0x6655bb]
      /usr/sbin/mysqld(handle_one_connection+0x43)[0x665683]
      /lib64/libpthread.so.0(+0x7df5)[0x7fe32f19adf5]
      /lib64/libc.so.6(clone+0x6d)[0x7fe32da181ad]
       
      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort.
      Query (0x7fe305420018): is an invalid pointer
      Connection ID (thread ID): 3
      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=off
       
      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.

        Attachments

          Activity

            People

            Assignee:
            sanja Oleksandr Byelkin
            Reporter:
            richard.lawley Richard Lawley
            Votes:
            1 Vote for this issue
            Watchers:
            6 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Git Integration