May 23 13:38:39 server06 mysqld: 140523 13:38:39  InnoDB: Assertion failure in thread 139746668750592 in file dict0load.c line 2200
May 23 13:38:39 server06 mysqld: InnoDB: Failing assertion: ut_memcmp(id, field, len) == 0
May 23 13:38:39 server06 mysqld: InnoDB: We intentionally generate a memory trap.
May 23 13:38:39 server06 mysqld: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
May 23 13:38:39 server06 mysqld: InnoDB: If you get repeated assertion failures or crashes, even
May 23 13:38:39 server06 mysqld: InnoDB: immediately after the mysqld startup, there may be
May 23 13:38:39 server06 mysqld: InnoDB: corruption in the InnoDB tablespace. Please refer to
May 23 13:38:39 server06 mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
May 23 13:38:39 server06 mysqld: InnoDB: about forcing recovery.
May 23 13:38:39 server06 mysqld: 140523 13:38:39 [ERROR] mysqld got signal 6 ;
May 23 13:38:39 server06 mysqld: This could be because you hit a bug. It is also possible that this binary
May 23 13:38:39 server06 mysqld: or one of the libraries it was linked against is corrupt, improperly built,
May 23 13:38:39 server06 mysqld: or misconfigured. This error can also be caused by malfunctioning hardware.
May 23 13:38:39 server06 mysqld: 
May 23 13:38:39 server06 mysqld: To report this bug, see http://kb.askmonty.org/en/reporting-bugs
May 23 13:38:39 server06 mysqld: 
May 23 13:38:39 server06 mysqld: We will try our best to scrape up some info that will hopefully help
May 23 13:38:39 server06 mysqld: diagnose the problem, but since we have already crashed, 
May 23 13:38:39 server06 mysqld: something is definitely wrong and this may fail.
May 23 13:38:39 server06 mysqld: 
May 23 13:38:39 server06 mysqld: Server version: 5.5.37-MariaDB-1~wheezy-log
May 23 13:38:39 server06 mysqld: key_buffer_size=134217728
May 23 13:38:39 server06 mysqld: read_buffer_size=131072
May 23 13:38:39 server06 mysqld: max_used_connections=53
May 23 13:38:39 server06 mysqld: max_threads=202
May 23 13:38:39 server06 mysqld: thread_count=13
May 23 13:38:39 server06 mysqld: It is possible that mysqld could use up to 
May 23 13:38:39 server06 mysqld: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 574216 K  bytes of memory
May 23 13:38:39 server06 mysqld: Hope that's ok; if not, decrease some variables in the equation.
May 23 13:38:39 server06 mysqld: 
May 23 13:38:39 server06 mysqld: Thread pointer: 0x0x7f19285da000
May 23 13:38:39 server06 mysqld: Attempting backtrace. You can use the following information to find out
May 23 13:38:39 server06 mysqld: where mysqld died. If you see no messages after this, something went
May 23 13:38:39 server06 mysqld: terribly wrong...
May 23 13:38:39 server06 mysqld: stack_bottom = 0x7f194e8c9e10 thread_stack 0x40000
May 23 13:38:39 server06 mysqld: /usr/sbin/mysqld(my_print_stacktrace+0x2b)[0x7f195124eeeb]
May 23 13:38:39 server06 mysqld: /usr/sbin/mysqld(handle_fatal_signal+0x422)[0x7f1950e8a5d2]
May 23 13:38:39 server06 mysqld: /lib/x86_64-linux-gnu/libpthread.so.0(+0xf030)[0x7f1950581030]
May 23 13:38:39 server06 mysqld: /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x35)[0x7f194edde475]
May 23 13:38:39 server06 mysqld: /lib/x86_64-linux-gnu/libc.so.6(abort+0x180)[0x7f194ede16f0]
May 23 13:38:39 server06 mysqld: /usr/sbin/mysqld(+0x6f516c)[0x7f19510a516c]
May 23 13:38:39 server06 mysqld: /usr/sbin/mysqld(+0x65b10e)[0x7f195100b10e]
May 23 13:38:39 server06 mysqld: /usr/sbin/mysqld(+0x63617b)[0x7f1950fe617b]
May 23 13:38:39 server06 mysqld: /usr/sbin/mysqld(_Z18mysql_rename_tableP10handlertonPKcS2_S2_S2_j+0x159)[0x7f1950dc6999]
May 23 13:38:39 server06 mysqld: /usr/sbin/mysqld(_Z17mysql_alter_tableP3THDPcS1_P24st_ha_create_informationP10TABLE_LISTP10Alter_infojP8st_orderbb+0x2535)[0x7f1950dcb375]
May 23 13:38:39 server06 mysqld: /usr/sbin/mysqld(_ZN21Alter_table_statement7executeEP3THD+0x4b3)[0x7f1950fb3573]
May 23 13:38:39 server06 mysqld: /usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x1952)[0x7f1950d51562]
May 23 13:38:39 server06 mysqld: /usr/sbin/mysqld(+0x3a5a77)[0x7f1950d55a77]
May 23 13:38:39 server06 mysqld: /usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x14b8)[0x7f1950d57088]
May 23 13:38:39 server06 mysqld: /usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x21b)[0x7f1950e0c63b]
May 23 13:38:39 server06 mysqld: /usr/sbin/mysqld(handle_one_connection+0x51)[0x7f1950e0c6c1]
May 23 13:38:39 server06 mysqld: /lib/x86_64-linux-gnu/libpthread.so.0(+0x6b50)[0x7f1950578b50]
May 23 13:38:39 server06 mysqld: /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f194ee880ed]
May 23 13:38:39 server06 mysqld: 
May 23 13:38:39 server06 mysqld: Trying to get some variables.
May 23 13:38:39 server06 mysqld: Some pointers may be invalid and cause the dump to abort.
May 23 13:38:39 server06 mysqld: Query (0x7f190382f018): is an invalid pointer
May 23 13:38:39 server06 mysqld: Connection ID (thread ID): 11633593
May 23 13:38:39 server06 mysqld: Status: NOT_KILLED
May 23 13:38:39 server06 mysqld: 
May 23 13:38:39 server06 mysqld: 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=off
May 23 13:38:39 server06 mysqld: 
May 23 13:38:39 server06 mysqld: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
May 23 13:38:39 server06 mysqld: information that should help you find out what is causing the crash.
May 23 13:38:40 server06 mysqld_safe: Number of processes running now: 0
May 23 13:38:40 server06 mysqld_safe: mysqld restarted