CURRENT_TEST: main.1st
2014-06-07 15:31:22 0 [Warning] The syntax '--master-retry-count' is deprecated and will be removed in a future release. Please use 'CHANGE MASTER TO master_retry_count = <num>' instead.
2014-06-07 15:31:22 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2014-06-07 15:31:22 15298 [Note] Plugin 'FEDERATED' is disabled.
2014-06-07 15:31:22 15298 [Note] InnoDB: Using atomics to ref count buffer pool pages
2014-06-07 15:31:22 7fa696f87760 InnoDB: !!!!!!!! UNIV_DEBUG switched on !!!!!!!!!
2014-06-07 15:31:22 7fa696f87760 InnoDB: !!!!!!!! UNIV_SYNC_DEBUG switched on !!!!!!!!!
2014-06-07 15:31:22 15298 [Note] InnoDB: The InnoDB memory heap is disabled
2014-06-07 15:31:22 15298 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2014-06-07 15:31:22 15298 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-06-07 15:31:22 15298 [Note] InnoDB: Using Linux native AIO
2014-06-07 15:31:22 15298 [Note] InnoDB: Using CPU crc32 instructions
2014-06-07 15:31:22 15298 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2014-06-07 15:31:22 15298 [Note] InnoDB: Completed initialization of buffer pool
2014-06-07 15:31:22 15298 [Note] InnoDB: Highest supported file format is Barracuda.
2014-06-07 15:31:22 15298 [Note] InnoDB: Log scan progressed past the checkpoint lsn 1588712
2014-06-07 15:31:22 15298 [Note] InnoDB: Database was not shutdown normally!
2014-06-07 15:31:22 15298 [Note] InnoDB: Starting crash recovery.
2014-06-07 15:31:22 15298 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-06-07 15:31:22 15298 [Note] InnoDB: Restoring possible half-written data pages 
2014-06-07 15:31:22 15298 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 1626124
2014-06-07 15:31:22 15298 [Note] InnoDB: starting tracking changed pages from LSN 1588712

2014-06-07 15:31:23 15298 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 
InnoDB: Apply batch completed
2014-06-07 15:31:24 15298 [Note] InnoDB: 128 rollback segment(s) are active.
2014-06-07 15:31:24 15298 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.17-66.0 started; log sequence number 1626124
Sat Jun  7 15:31:24 2014 Tokudb file system space is really low and access is restricted
2014-06-07 15:31:24 15298 [Warning] /data/bench/qa56dbg/Percona-Server-5.6.17-rel66.0-608.Linux.x86_64-debug/bin/mysqld: unknown option '--loose-skip-ndbcluster'
2014-06-07 15:31:24 15298 [Warning] /data/bench/qa56dbg/Percona-Server-5.6.17-rel66.0-608.Linux.x86_64-debug/bin/mysqld: unknown option '--loose-debug-assert-if-crashed-table'
2014-06-07 15:31:24 15298 [Warning] /data/bench/qa56dbg/Percona-Server-5.6.17-rel66.0-608.Linux.x86_64-debug/bin/mysqld: unknown option '--loose-debug-assert-on-error'
2014-06-07 15:31:24 15298 [Warning] No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: a3ada413-ee3f-11e3-9470-78e7d18cee28.
2014-06-07 15:31:24 15298 [Note] Server hostname (bind-address): '*'; port: 13120
2014-06-07 15:31:24 15298 [Note] IPv6 is available.
2014-06-07 15:31:24 15298 [Note]   - '::' resolves to '::';
2014-06-07 15:31:24 15298 [Note] Server socket created on IP: '::'.
2014-06-07 15:31:24 15298 [Warning] 'user' entry 'root@hppro1.office.percona.com' ignored in --skip-name-resolve mode.
2014-06-07 15:31:24 15298 [Warning] 'proxies_priv' entry '@ root@hppro1.office.percona.com' ignored in --skip-name-resolve mode.
2014-06-07 15:31:24 15298 [Note] Event Scheduler: Loaded 0 events
2014-06-07 15:31:24 15298 [Note] Execution of init_file '/data/bench/qa56dbg/randgen/conf/percona_qa/5.6/TokuDB.sql' started.
2014-06-07 15:31:24 15298 [Note] Execution of init_file '/data/bench/qa56dbg/randgen/conf/percona_qa/5.6/TokuDB.sql' ended.
2014-06-07 15:31:24 15298 [Note] /data/bench/qa56dbg/Percona-Server-5.6.17-rel66.0-608.Linux.x86_64-debug/bin/mysqld: ready for connections.
Version: '5.6.17-66.0-debug-log'  socket: '/ssd/qa56dbg/33/current1_7/tmp/master.sock'  port: 13120  Percona Server (GPL), Release 66.0, Revision 608, DEBUG BINARY
2014-06-07 15:38:06 7fa66c3fe700  InnoDB: Assertion failure in thread 140352757425920 in file os0file.cc line 5126
InnoDB: Failing assertion: slot != NULL
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
12:38:06 UTC - 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.
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.
Please help us make Percona Server better by reporting any
bugs at http://bugs.percona.com/

key_buffer_size=1048576
read_buffer_size=131072
max_used_connections=2
max_threads=100001
thread_count=2
connection_count=2
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 38403639 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
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 = 0 thread_stack 0x40000
/data/bench/qa56dbg/Percona-Server-5.6.17-rel66.0-608.Linux.x86_64-debug/bin/mysqld(my_print_stacktrace+0x35)[0xaa68c8]
/data/bench/qa56dbg/Percona-Server-5.6.17-rel66.0-608.Linux.x86_64-debug/bin/mysqld(handle_fatal_signal+0x41a)[0x723da2]
/lib64/libpthread.so.0(+0xf500)[0x7fa69693c500]
/lib64/libc.so.6(gsignal+0x35)[0x7fa6955e88e5]
/lib64/libc.so.6(abort+0x175)[0x7fa6955ea0c5]
/data/bench/qa56dbg/Percona-Server-5.6.17-rel66.0-608.Linux.x86_64-debug/bin/mysqld[0xbb9335]
/data/bench/qa56dbg/Percona-Server-5.6.17-rel66.0-608.Linux.x86_64-debug/bin/mysqld[0xbb9683]
/data/bench/qa56dbg/Percona-Server-5.6.17-rel66.0-608.Linux.x86_64-debug/bin/mysqld[0xd8110d]
/data/bench/qa56dbg/Percona-Server-5.6.17-rel66.0-608.Linux.x86_64-debug/bin/mysqld[0xc85e01]
/lib64/libpthread.so.0(+0x7851)[0x7fa696934851]
/lib64/libc.so.6(clone+0x6d)[0x7fa69569e94d]
You may download the Percona Server operations manual by visiting
http://www.percona.com/software/percona-server/. You may find information
in the manual which will help you identify the cause of the crash.
Writing a core file