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

Server crashes on TRUNCATE TABLE

    XMLWordPrintable

    Details

      Description

      Another crash. 10.3 seems to be incredibly unstable. This is the third crash we are reporting. Here is the log:

      Mar 2 19:23:23 litemasha mysqld[1246]: 190302 19:23:23 [ERROR] mysqld got signal 11 ;
      Mar 2 19:23:23 litemasha mysqld[1246]: This could be because you hit a bug. It is also possible that this binary
      Mar 2 19:23:23 litemasha mysqld[1246]: or one of the libraries it was linked against is corrupt, improperly built,
      Mar 2 19:23:23 litemasha mysqld[1246]: or misconfigured. This error can also be caused by malfunctioning hardware.
      Mar 2 19:23:23 litemasha mysqld[1246]: To report this bug, see https://mariadb.com/kb/en/reporting-bugs
      Mar 2 19:23:23 litemasha mysqld[1246]: We will try our best to scrape up some info that will hopefully help
      Mar 2 19:23:23 litemasha mysqld[1246]: diagnose the problem, but since we have already crashed,
      Mar 2 19:23:23 litemasha mysqld[1246]: something is definitely wrong and this may fail.
      Mar 2 19:23:23 litemasha mysqld[1246]: Server version: 10.3.13-MariaDB-1:10.3.13+maria~xenial
      Mar 2 19:23:23 litemasha mysqld[1246]: key_buffer_size=134217728
      Mar 2 19:23:23 litemasha mysqld[1246]: read_buffer_size=2097152
      Mar 2 19:23:23 litemasha mysqld[1246]: max_used_connections=23
      Mar 2 19:23:23 litemasha mysqld[1246]: max_threads=202
      Mar 2 19:23:23 litemasha mysqld[1246]: thread_count=21
      Mar 2 19:23:23 litemasha mysqld[1246]: It is possible that mysqld could use up to
      Mar 2 19:23:23 litemasha mysqld[1246]: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1376643 K bytes of memory
      Mar 2 19:23:23 litemasha mysqld[1246]: Hope that's ok; if not, decrease some variables in the equation.
      Mar 2 19:23:23 litemasha mysqld[1246]: Thread pointer: 0x7f9f30269288
      Mar 2 19:23:23 litemasha mysqld[1246]: Attempting backtrace. You can use the following information to find out
      Mar 2 19:23:23 litemasha mysqld[1246]: where mysqld died. If you see no messages after this, something went
      Mar 2 19:23:23 litemasha mysqld[1246]: terribly wrong...
      Mar 2 19:23:23 litemasha mysqld[1246]: stack_bottom = 0x7f9f84c09cf8 thread_stack 0x49000
      Mar 2 19:23:40 litemasha mysqld[1246]: /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x558792c5936e]
      Mar 2 19:23:40 litemasha mysqld[1246]: /usr/sbin/mysqld(handle_fatal_signal+0x347)[0x558792708187]
      Mar 2 19:23:40 litemasha mysqld[1246]: /lib/x86_64-linux-gnu/libpthread.so.0(+0x11390)[0x7fa0b3d5c390]
      Mar 2 19:23:40 litemasha mysqld[1246]: /usr/sbin/mysqld(+0xbb7c67)[0x558792b6dc67]
      Mar 2 19:23:41 litemasha mysqld[1246]: /usr/sbin/mysqld(+0xb18fa5)[0x558792acefa5]
      Mar 2 19:23:41 litemasha mysqld[1246]: /usr/sbin/mysqld(+0xb1ac0b)[0x558792ad0c0b]
      Mar 2 19:23:41 litemasha mysqld[1246]: /usr/sbin/mysqld(+0xb45f0d)[0x558792afbf0d]
      Mar 2 19:23:41 litemasha mysqld[1246]: /usr/sbin/mysqld(+0xa67635)[0x558792a1d635]
      Mar 2 19:23:41 litemasha mysqld[1246]: /usr/sbin/mysqld(+0x9af282)[0x558792965282]
      Mar 2 19:23:41 litemasha mysqld[1246]: /usr/sbin/mysqld(+0x9ab3db)[0x5587929613db]
      Mar 2 19:23:41 litemasha mysqld[1246]: /usr/sbin/mysqld(_ZN22Sql_cmd_truncate_table16handler_truncateEP3THDP10TABLE_LISTb+0x108)[0x558792854a88]
      Mar 2 19:23:41 litemasha mysqld[1246]: /usr/sbin/mysqld(_ZN22Sql_cmd_truncate_table14truncate_tableEP3THDP10TABLE_LIST+0x1d0)[0x5587928552f0]
      Mar 2 19:23:41 litemasha mysqld[1246]: /usr/sbin/mysqld(_ZN22Sql_cmd_truncate_table7executeEP3THD+0x50)[0x5587928553a0]
      Mar 2 19:23:41 litemasha mysqld[1246]: /usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x13d7)[0x558792527477]
      Mar 2 19:23:41 litemasha mysqld[1246]: /usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_statebb+0x21a)[0x55879252eb8a]
      Mar 2 19:23:41 litemasha mysqld[1246]: /usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcjbb+0x1cc0)[0x5587925315b0]
      Mar 2 19:23:41 litemasha mysqld[1246]: /usr/sbin/mysqld(_Z10do_commandP3THD+0x13c)[0x5587925320bc]
      Mar 2 19:23:41 litemasha mysqld[1246]: /usr/sbin/mysqld(_Z24do_handle_one_connectionP7CONNECT+0x252)[0x558792604042]
      Mar 2 19:23:41 litemasha mysqld[1246]: /usr/sbin/mysqld(handle_one_connection+0x3d)[0x5587926041bd]
      Mar 2 19:23:41 litemasha mysqld[1246]: /lib/x86_64-linux-gnu/libpthread.so.0(+0x76ba)[0x7fa0b3d526ba]
      Mar 2 19:23:41 litemasha mysqld[1246]: /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7fa0b33fd41d]
      Mar 2 19:23:41 litemasha mysqld[1246]: Trying to get some variables.
      Mar 2 19:23:41 litemasha mysqld[1246]: Some pointers may be invalid and cause the dump to abort.
      Mar 2 19:23:41 litemasha mysqld[1246]: Query (0x7f9f30888940): TRUNCATE TABLE `LiteworldCompany-Site5`.`ZipCodes`
      Mar 2 19:23:41 litemasha mysqld[1246]: Connection ID (thread ID): 80684
      Mar 2 19:23:41 litemasha mysqld[1246]: Status: NOT_KILLED
      Mar 2 19:23:41 litemasha mysqld[1246]: 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,split_materialized=on
      Mar 2 19:23:42 litemasha kernel: [355725.768030] do_general_protection: 9 callbacks suppressed
      Mar 2 19:23:42 litemasha kernel: [355725.816626] traps: mysqld[7494] general protection ip:558792b6dc67 sp:7f9f84c06060 error:0 in mysqld[558791fb6000+1261000]
      Mar 2 19:23:42 litemasha mysqld[1246]: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
      Mar 2 19:23:42 litemasha mysqld[1246]: information that should help you find out what is causing the crash.
      Mar 2 19:23:53 litemasha systemd[1]: mariadb.service: Main process exited, code=dumped, status=11/SEGV
      Mar 2 19:23:53 litemasha systemd[1]: mariadb.service: Unit entered failed state.
      Mar 2 19:23:53 litemasha systemd[1]: mariadb.service: Failed with result 'core-dump'.
      Mar 2 19:23:58 litemasha systemd[1]: mariadb.service: Service hold-off time over, scheduling restart.
      Mar 2 19:23:58 litemasha systemd[1]: Stopped MariaDB 10.3.13 database server.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              marko Marko Mäkelä
              Reporter:
              kvasserman Konstantin Vasserman
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: