MariaDB Crashed when I Updated WSREP_ON Global Variable



  • Official comment
    Krzysztof Ksiazek


    It seems like you hit some bug in MariaDB or Galera code. I think the best course of action would be to open a bug report in MariaDB Jira ( and see if they can help you debugging this issue further. If you'll open the bug report, please paste the link to it here for the reference and for further readers who may end up with the similar case like you have.


    Comment actions Permalink
  • Avatar

    Complete log here....

    2018-12-05 16:33:15 0 [Note] InnoDB: Starting shutdown...
    2018-12-05 16:33:15 0 [Note] InnoDB: Dumping buffer pool(s) to /var/lib/mysql/ib_buffer_pool
    2018-12-05 16:33:15 0 [Note] InnoDB: Buffer pool(s) dump completed at 181205 16:33:15
    2018-12-05 16:33:16 0 [Note] InnoDB: Shutdown completed; log sequence number 23935227307; transaction id 55857476
    2018-12-05 16:33:16 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
    2018-12-05 16:33:16 0 [Note] /usr/sbin/mysqld: Shutdown complete

    2018-12-05 16:33:47 0 [Warning] You need to use --log-bin to make --binlog-format work.
    2018-12-05 16:33:47 0 [Note] InnoDB: Using Linux native AIO
    2018-12-05 16:33:47 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
    2018-12-05 16:33:47 0 [Note] InnoDB: Uses event mutexes
    2018-12-05 16:33:47 0 [Note] InnoDB: Compressed tables use zlib 1.2.7
    2018-12-05 16:33:47 0 [Note] InnoDB: Number of pools: 1
    2018-12-05 16:33:47 0 [Note] InnoDB: Using SSE2 crc32 instructions
    2018-12-05 16:33:47 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
    2018-12-05 16:33:47 0 [Note] InnoDB: Completed initialization of buffer pool
    2018-12-05 16:33:47 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
    2018-12-05 16:33:47 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
    2018-12-05 16:33:47 0 [Note] InnoDB: Creating shared tablespace for temporary tables
    2018-12-05 16:33:47 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
    2018-12-05 16:33:47 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
    2018-12-05 16:33:47 0 [Note] InnoDB: 10.3.10 started; log sequence number 23935227307; transaction id 55857469
    2018-12-05 16:33:47 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
    2018-12-05 16:33:47 0 [Note] Plugin 'FEEDBACK' is disabled.
    2018-12-05 16:33:47 0 [Note] Server socket created on IP: '::'.
    2018-12-05 16:33:47 0 [Note] InnoDB: Buffer pool(s) load completed at 181205 16:33:47
    2018-12-05 16:33:47 0 [Note] Reading of all Master_info entries succeded
    2018-12-05 16:33:47 0 [Note] Added new Master_info '' to hash table
    2018-12-05 16:33:47 0 [Note] /usr/sbin/mysqld: ready for connections.
    Version: '10.3.10-MariaDB'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MariaDB Server
    2018-12-05 16:33:47 8 [Warning] Access denied for user 'root'@'localhost' (using password: NO)
    181205 16:56:15 [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

    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.3.10-MariaDB
    It is possible that mysqld could use up to
    key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467398 K  bytes of memory
    Hope that's ok; if not, decrease some variables in the equation.

    Thread pointer: 0x7f13f00009a8
    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 = 0x7f1445cb3d70 thread_stack 0x49000

    Trying to get some variables.
    Some pointers may be invalid and cause the dump to abort.
    Query (0x0): is an invalid pointer
    Connection ID (thread ID): 10
    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,orderby_uses_equalities=on,condition_pushdown_for_derived=on,split_materialized=on

    The manual page at contains
    information that should help you find out what is causing the crash.

    We think the query pointer is invalid, but we will try to print it anyway.

    Comment actions Permalink
  • Avatar

    Already reported the bug to

    Comment actions Permalink

Please sign in to leave a comment.

Powered by Zendesk