Assertion `(uint)v->offset <= vars->dynamic_variables_head' failure and further refusal to start

commit 28ebc2a72485c4b2956531010bd3ee247ae91df2

Author: Sergei Golubchik <serg@mariadb.org>

Date:   Wed Aug 27 20:32:32 2014 +0200

    cleanup: sysvar, only one common check_update_type()

--source include/have_innodb.inc

--connect (con1,localhost,root,,)

create table t1 (i int) engine=InnoDB;

install soname 'ha_tokudb';

--disconnect

--connection default

select "Still here?";

Version: '10.1.1-MariaDB-wsrep-debug'  socket: '/home/elenst/git/10.1/data/tmp/mysql.sock'  port: 3306  Source distribution, wsrep_25.10.r4123

mysqld: /home/elenst/git/10.1/sql/sql_plugin.cc:3111: void cleanup_variables(THD*, system_variables*): Assertion `(uint)v->offset <= vars->dynamic_variables_head' failed.

141025 11:50:37 [ERROR] mysqld got signal 6 ;

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.1.1-MariaDB-wsrep-debug

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 = 467303 K  bytes of memory

Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0x7f3a7df44070

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 = 0x7f3a99e47e30 thread_stack 0x48000

Fatal signal 11 while backtracing

commit 0a16fe4ec9add45532b6fd36a1059c33bac14f05

Author: Alexey Botchkov <holyfoot@montyprogram.com>

Date:   Fri Oct 24 17:12:03 2014 +0500

    GIS-related test results updated.

141025 11:51:29 [ERROR] mysqld: Table './mysql/plugin' is marked as crashed and should be repaired

141025 11:51:29 [Warning] Checking table:   './mysql/plugin'

141025 11:51:29 [ERROR] mysql.plugin: 1 client is using or hasn't closed the table properly

Sat Oct 25 11:51:29 2014 TokuFT recovery starting in env /home/elenst/git/10.1/data/

Sat Oct 25 11:51:29 2014 TokuFT recovery scanning backward from 12

Sat Oct 25 11:51:29 2014 TokuFT recovery bw_end_checkpoint at 12 timestamp 1414223435280149 xid 8 (bw_newer)

Sat Oct 25 11:51:29 2014 TokuFT recovery bw_begin_checkpoint at 8 timestamp 1414223434743935 (bw_between)

Sat Oct 25 11:51:29 2014 TokuFT recovery turning around at begin checkpoint 8 time 536214

Sat Oct 25 11:51:29 2014 TokuFT recovery starts scanning forward to 12 from 8 left 4 (fw_between)

Sat Oct 25 11:51:29 2014 TokuFT recovery closing 2 dictionaries

Sat Oct 25 11:51:29 2014 TokuFT recovery making a checkpoint

Sat Oct 25 11:51:29 2014 TokuFT recovery done

141025 11:51:29 [Note] Recovering after a crash using tc.log

141025 11:51:29 [ERROR] Recovery failed! You must enable exactly 2 storage engines that support two-phase commit protocol

141025 11:51:29 [ERROR] Crash recovery failed. Either correct the problem (if it's, for example, out of memory error) and restart, or delete tc log and start mysqld with --tc-heuristic-recover={commit|rollback}

141025 11:51:29 [ERROR] Can't init tc log

141025 11:51:29 [ERROR] Aborting

141025 11:51:31 [Note] InnoDB: FTS optimize thread exiting.

141025 11:51:31 [Note] InnoDB: Starting shutdown...