2014-11-05 05:54:26 8632 [Note] Plugin 'FEDERATED' is disabled. 2014-11-05 05:54:26 8632 [Note] InnoDB: Using atomics to ref count buffer pool pages 2014-11-05 05:54:26 7f898938a780 InnoDB: !!!!!!!! UNIV_DEBUG switched on !!!!!!!!! 2014-11-05 05:54:26 7f898938a780 InnoDB: !!!!!!!! UNIV_SYNC_DEBUG switched on !!!!!!!!! 2014-11-05 05:54:26 8632 [Note] InnoDB: The InnoDB memory heap is disabled 2014-11-05 05:54:26 8632 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2014-11-05 05:54:26 8632 [Note] InnoDB: Memory barrier is not used 2014-11-05 05:54:26 8632 [Note] InnoDB: Compressed tables use zlib 1.2.3 2014-11-05 05:54:26 8632 [Note] InnoDB: Using Linux native AIO 2014-11-05 05:54:26 8632 [Note] InnoDB: Using CPU crc32 instructions 2014-11-05 05:54:26 8632 [Note] InnoDB: Initializing buffer pool, size = 2.0G 2014-11-05 05:54:26 8632 [Note] InnoDB: Completed initialization of buffer pool 2014-11-05 05:54:26 8632 [Note] InnoDB: Highest supported file format is Barracuda. 2014-11-05 05:54:27 8632 [Note] InnoDB: 128 rollback segment(s) are active. 2014-11-05 05:54:27 8632 [Note] InnoDB: Waiting for purge to start 2014-11-05 05:54:27 8632 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.21-69.0 started; log sequence number 1625987 2014-11-05 05:54:27 8632 [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: 33fe0ed1-64b0-11e4-98c3-002590e9b49b. 2014-11-05 05:54:27 8632 [Note] Server hostname (bind-address): '*'; port: 12270 2014-11-05 05:54:27 8632 [Note] IPv6 is available. 2014-11-05 05:54:27 8632 [Note] - '::' resolves to '::'; 2014-11-05 05:54:27 8632 [Note] Server socket created on IP: '::'. 2014-11-05 05:54:27 8632 [Note] Event Scheduler: Loaded 0 events 2014-11-05 05:54:27 8632 [Note] /ssd/ramesh/Percona-Server-5.6.21-rel69.0-681.Linux.x86_64-debug/bin/mysqld: ready for connections. Version: '5.6.21-69.0-debug' socket: '/ssd/ramesh/Percona-Server-5.6.21-rel69.0-681.Linux.x86_64-debug/socket.sock' port: 12270 Percona Server (GPL), Release 69.0, Revision 681, DEBUG BINARY InnoDB: error in sec index entry update in InnoDB: index `z` of table `data`.`#sql21b8_1_0` InnoDB: tuple DATA TUPLE: 2 fields; 0: len 4; hex 80000008; asc ;; 1: len 6; hex 000000000200; asc ;; InnoDB: record PHYSICAL RECORD: n_fields 2; compact format; info bits 32 0: len 4; hex 80000003; asc ;; 1: len 6; hex 000000000200; asc ;; TRANSACTION 1799, ACTIVE 0 sec updating or deleting mysql tables in use 1, locked 1 2 lock struct(s), heap size 376, 1 row lock(s) MySQL thread id 1, OS thread handle 0x7f898932e700, query id 15 localhost root updating UPDATE t1 SET a=2 InnoDB: Submit a detailed bug report to http://bugs.mysql.com 2014-11-05 05:54:30 7f898932e700 InnoDB: Assertion failure in thread 140228689061632 in file row0upd.cc line 1794 InnoDB: Failing assertion: 0 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. 05:54:30 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=8388608 read_buffer_size=131072 max_used_connections=1 max_threads=153 thread_count=1 connection_count=1 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 69191 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x7f88f43f2000 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 = 7f898932de18 thread_stack 0x40000 /ssd/ramesh/Percona-Server-5.6.21-rel69.0-681.Linux.x86_64-debug/bin/mysqld(my_print_stacktrace+0x35)[0xab7504] /ssd/ramesh/Percona-Server-5.6.21-rel69.0-681.Linux.x86_64-debug/bin/mysqld(handle_fatal_signal+0x41a)[0x72f806] /lib64/libpthread.so.0(+0xf130)[0x7f8988d3e130] /lib64/libc.so.6(gsignal+0x39)[0x7f898793f5c9] /lib64/libc.so.6(abort+0x148)[0x7f8987940cd8] /ssd/ramesh/Percona-Server-5.6.21-rel69.0-681.Linux.x86_64-debug/bin/mysqld[0xc1864e] /ssd/ramesh/Percona-Server-5.6.21-rel69.0-681.Linux.x86_64-debug/bin/mysqld[0xc18929] /ssd/ramesh/Percona-Server-5.6.21-rel69.0-681.Linux.x86_64-debug/bin/mysqld[0xc1a2b6] /ssd/ramesh/Percona-Server-5.6.21-rel69.0-681.Linux.x86_64-debug/bin/mysqld[0xc1a5b5] /ssd/ramesh/Percona-Server-5.6.21-rel69.0-681.Linux.x86_64-debug/bin/mysqld[0xbdaa0a] /ssd/ramesh/Percona-Server-5.6.21-rel69.0-681.Linux.x86_64-debug/bin/mysqld[0xad7990] /ssd/ramesh/Percona-Server-5.6.21-rel69.0-681.Linux.x86_64-debug/bin/mysqld(_ZN7handler13ha_update_rowEPKhPh+0x18d)[0x64cc99] /ssd/ramesh/Percona-Server-5.6.21-rel69.0-681.Linux.x86_64-debug/bin/mysqld(_Z12mysql_updateP3THDP10TABLE_LISTR4ListI4ItemES6_PS4_jP8st_ordery15enum_duplicatesbPySB_+0x1bf6)[0x879052] /ssd/ramesh/Percona-Server-5.6.21-rel69.0-681.Linux.x86_64-debug/bin/mysqld(_Z21mysql_execute_commandP3THD+0x2d29)[0x7e4d76] /ssd/ramesh/Percona-Server-5.6.21-rel69.0-681.Linux.x86_64-debug/bin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x5a6)[0x7ed193] /ssd/ramesh/Percona-Server-5.6.21-rel69.0-681.Linux.x86_64-debug/bin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0xc88)[0x7df5fc] /ssd/ramesh/Percona-Server-5.6.21-rel69.0-681.Linux.x86_64-debug/bin/mysqld(_Z10do_commandP3THD+0x3ac)[0x7de528] /ssd/ramesh/Percona-Server-5.6.21-rel69.0-681.Linux.x86_64-debug/bin/mysqld(_Z24do_handle_one_connectionP3THD+0x1c4)[0x7a64e5] /ssd/ramesh/Percona-Server-5.6.21-rel69.0-681.Linux.x86_64-debug/bin/mysqld(handle_one_connection+0x33)[0x7a5fed] /ssd/ramesh/Percona-Server-5.6.21-rel69.0-681.Linux.x86_64-debug/bin/mysqld(pfs_spawn_thread+0x159)[0xdc5bac] /lib64/libpthread.so.0(+0x7df3)[0x7f8988d36df3] /lib64/libc.so.6(clone+0x6d)[0x7f8987a0001d] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (7f88cb01f010): UPDATE t1 SET a=2 Connection ID (thread ID): 1 Status: NOT_KILLED 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