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

kill user command cause MariaDB crash!

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 5.3.12, 5.5.40, 10.0.12, 10.0.14, 10.1.0
    • Fix Version/s: 5.5.41, 10.0.16
    • Component/s: Admin statements
    • Labels:
      None
    • Environment:
      CentOS6.4

      Description

      i create user 'test'@'192.168.26.172' ,and MariaDB on 192.168.26.171,when i use user 'root'@'localhost' login DB ,and issue command kill user 'test'@'192.168.26.172 ,the DB crashed \ T.T /

      MariaDB [(none)]> show processlist;
      +----+------+----------------------+------+---------+------+-------+------------------+----------+
      | Id | User | Host                 | db   | Command | Time | State | Info             | Progress |
      +----+------+----------------------+------+---------+------+-------+------------------+----------+
      |  3 | root | localhost            | NULL | Query   |    0 | init  | show processlist |    0.000 |
      |  4 | test | localhost            | NULL | Sleep   |   20 |       | NULL             |    0.000 |
      |  5 | test | 192.168.26.172:14061 | NULL | Sleep   |   14 |       | NULL             |    0.000 |
      +----+------+----------------------+------+---------+------+-------+------------------+----------+
      3 rows in set (0.00 sec)

       
      MariaDB [(none)]> kill user 'test'@'192.168.26.172';
      ERROR 2013 (HY000): Lost connection to MySQL server during query
      MariaDB [(none)]> show processlist;
      ERROR 2006 (HY000): MySQL server has gone away
      No connection. Trying to reconnect...
      Connection id:    3
      Current database: *** NONE ***
       
      +----+------+-----------+------+---------+------+-------+------------------+----------+
      | Id | User | Host      | db   | Command | Time | State | Info             | Progress |
      +----+------+-----------+------+---------+------+-------+------------------+----------+
      |  3 | root | localhost | NULL | Query   |    0 | init  | show processlist |    0.000 |
      +----+------+-----------+------+---------+------+-------+------------------+----------+
      1 row in set (0.00 sec)
       

      Version: '10.0.12-MariaDB-log'  socket: '/tmp/mysql99.sock'  port: 3306  MariaDB Server
      141020 14:33:12 [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: 10.0.12-MariaDB-log
      key_buffer_size=134217728
      read_buffer_size=131072
      max_used_connections=3
      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 = 467144 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
       
      Thread pointer: 0x0x7feb7b7f5008
      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 = 0x7feb94db4d10 thread_stack 0x48000
      /usr/sbin/mysqld(my_print_stacktrace+0x2b)[0xb6c14b]
      /usr/sbin/mysqld(handle_fatal_signal+0x398)[0x7255f8]
      /lib64/libpthread.so.0[0x377d60f500]
      /lib64/libc.so.6[0x377d327a96]
      /usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x599f)[0x5d4d5f]
      /usr/sbin/mysqld[0x5d5b12]
      /usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x1b20)[0x5d7cd0]
      /usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x453)[0x6950e3]
      /usr/sbin/mysqld(handle_one_connection+0x42)[0x6951b2]
      /lib64/libpthread.so.0[0x377d607851]
      /lib64/libc.so.6(clone+0x6d)[0x377d2e890d]
       
      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort.
      Query (0x7feb6a81e020): 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=on,exists_to_in=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.
      141020 14:33:12 mysqld_safe Number of processes running now: 0
      141020 14:33:12 mysqld_safe mysqld restarted
      141020 14:33:12 [Note] InnoDB: Using mutexes to ref count buffer pool pages
      141020 14:33:12 [Note] InnoDB: The InnoDB memory heap is disabled
      141020 14:33:12 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
      141020 14:33:12 [Note] InnoDB: Compressed tables use zlib 1.2.3
      141020 14:33:12 [Note] InnoDB: Using Linux native AIO
      141020 14:33:12 [Note] InnoDB: Using CPU crc32 instructions
      2014-10-20 14:33:12 7fad0089d840 InnoDB: Warning: io_setup() failed with EAGAIN. Will make 5 attempts before giving up.
      InnoDB: Warning: io_setup() attempt 1 failed.
      InnoDB: Warning: io_setup() attempt 2 failed.
      InnoDB: Warning: io_setup() attempt 3 failed.
      InnoDB: Warning: io_setup() attempt 4 failed.
      InnoDB: Warning: io_setup() attempt 5 failed.
      2014-10-20 14:33:14 7fad0089d840 InnoDB: Error: io_setup() failed with EAGAIN after 5 attempts.
      InnoDB: You can disable Linux Native AIO by setting innodb_use_native_aio = 0 in my.cnf
        InnoDB: Warning: Linux Native AIO disabled because os_aio_linux_create_io_ctx() failed. To get rid of this warning you can try increasing system fs.aio-max-nr to 1048576 or larger or setting innodb_use_native_aio = 0 in my.cnf
      141020 14:33:14 [Note] InnoDB: Initializing buffer pool, size = 128.0M
      141020 14:33:14 [Note] InnoDB: Completed initialization of buffer pool
      141020 14:33:14 [Note] InnoDB: Highest supported file format is Barracuda.
      141020 14:33:14 [Note] InnoDB: The log sequence numbers 1616727 and 1616727 in ibdata files do not match the log sequence number 1244040091 in the ib_logfiles!
      141020 14:33:14 [Note] InnoDB: Database was not shutdown normally!
      141020 14:33:14 [Note] InnoDB: Starting crash recovery.
      141020 14:33:14 [Note] InnoDB: Reading tablespace information from the .ibd files...
      141020 14:33:14 [Note] InnoDB: Restoring possible half-written data pages
      141020 14:33:14 [Note] InnoDB: from the doublewrite buffer...
      InnoDB: Last MySQL binlog file position 0 316868674, file name /var/lib/mysql/99/sm_99db-bin.000016
      141020 14:33:14 [Note] InnoDB: 128 rollback segment(s) are active.
      141020 14:33:14 [Note] InnoDB: Waiting for purge to start
      141020 14:33:14 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.17-65.0 started; log sequence number 1244040091
      141020 14:33:14 [Note] Plugin 'FEEDBACK' is disabled.
      141020 14:33:14 [Note] Recovering after a crash using /var/lib/mysql/99/sm_99db-bin
      141020 14:33:14 [Note] Starting crash recovery...
      141020 14:33:14 [Note] Crash recovery finished.
      141020 14:33:14 [Note] Server socket created on IP: '0.0.0.0'.
      141020 14:33:14 [Warning] 'user' entry 'root@hzih171' ignored in --skip-name-resolve mode.

        Attachments

          Activity

            People

            • Assignee:
              monty Michael Widenius
              Reporter:
              alexkim 黄春晖
            • Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: