Feb  6 12:51:51 server06 mysqld: 140206 12:51:51  InnoDB: Assertion failure in thread 140222036240128 in file dict0load.c line 2199
Feb  6 12:51:51 server06 mysqld: InnoDB: Failing assertion: len == id_len
Feb  6 12:51:51 server06 mysqld: InnoDB: We intentionally generate a memory trap.
Feb  6 12:51:51 server06 mysqld: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
Feb  6 12:51:51 server06 mysqld: InnoDB: If you get repeated assertion failures or crashes, even
Feb  6 12:51:51 server06 mysqld: InnoDB: immediately after the mysqld startup, there may be
Feb  6 12:51:51 server06 mysqld: InnoDB: corruption in the InnoDB tablespace. Please refer to
Feb  6 12:51:51 server06 mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
Feb  6 12:51:51 server06 mysqld: InnoDB: about forcing recovery.
Feb  6 12:51:51 server06 mysqld: 140206 12:51:51 [ERROR] mysqld got signal 6 ;
Feb  6 12:51:51 server06 mysqld: This could be because you hit a bug. It is also possible that this binary
Feb  6 12:51:51 server06 mysqld: or one of the libraries it was linked against is corrupt, improperly built,
Feb  6 12:51:51 server06 mysqld: or misconfigured. This error can also be caused by malfunctioning hardware.
Feb  6 12:51:51 server06 mysqld: 
Feb  6 12:51:51 server06 mysqld: To report this bug, see http://kb.askmonty.org/en/reporting-bugs
Feb  6 12:51:51 server06 mysqld: 
Feb  6 12:51:51 server06 mysqld: We will try our best to scrape up some info that will hopefully help
Feb  6 12:51:51 server06 mysqld: diagnose the problem, but since we have already crashed, 
Feb  6 12:51:51 server06 mysqld: something is definitely wrong and this may fail.
Feb  6 12:51:51 server06 mysqld: 
Feb  6 12:51:51 server06 mysqld: Server version: 5.5.35-MariaDB-1~wheezy-log
Feb  6 12:51:51 server06 mysqld: key_buffer_size=134217728
Feb  6 12:51:51 server06 mysqld: read_buffer_size=131072
Feb  6 12:51:51 server06 mysqld: max_used_connections=54
Feb  6 12:51:51 server06 mysqld: max_threads=202
Feb  6 12:51:51 server06 mysqld: thread_count=16
Feb  6 12:51:51 server06 mysqld: It is possible that mysqld could use up to 
Feb  6 12:51:51 server06 mysqld: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 574216 K  bytes of memory
Feb  6 12:51:51 server06 mysqld: Hope that's ok; if not, decrease some variables in the equation.
Feb  6 12:51:51 server06 mysqld: 
Feb  6 12:51:51 server06 mysqld: Thread pointer: 0x0x7f87e9d4a000
Feb  6 12:51:51 server06 mysqld: Attempting backtrace. You can use the following information to find out
Feb  6 12:51:51 server06 mysqld: where mysqld died. If you see no messages after this, something went
Feb  6 12:51:51 server06 mysqld: terribly wrong...
Feb  6 12:51:51 server06 mysqld: stack_bottom = 0x7f87fca8de10 thread_stack 0x40000
Feb  6 12:51:51 server06 mysqld: /usr/sbin/mysqld(my_print_stacktrace+0x2b)[0x7f880c394b4b]
Feb  6 12:51:51 server06 mysqld: /usr/sbin/mysqld(handle_fatal_signal+0x422)[0x7f880bfd0da2]
Feb  6 12:51:51 server06 mysqld: /lib/x86_64-linux-gnu/libpthread.so.0(+0xf030)[0x7f880b6c8030]
Feb  6 12:51:51 server06 mysqld: /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x35)[0x7f8809f3a475]
Feb  6 12:51:51 server06 mysqld: /lib/x86_64-linux-gnu/libc.so.6(abort+0x180)[0x7f8809f3d6f0]
Feb  6 12:51:51 server06 mysqld: /usr/sbin/mysqld(+0x6f44ef)[0x7f880c1eb4ef]
Feb  6 12:51:51 server06 mysqld: /usr/sbin/mysqld(+0x65a44e)[0x7f880c15144e]
Feb  6 12:51:51 server06 mysqld: /usr/sbin/mysqld(+0x6354fb)[0x7f880c12c4fb]
Feb  6 12:51:51 server06 mysqld: /usr/sbin/mysqld(_Z18mysql_rename_tableP10handlertonPKcS2_S2_S2_j+0x159)[0x7f880bf0d3f9]
Feb  6 12:51:51 server06 mysqld: /usr/sbin/mysqld(_Z17mysql_alter_tableP3THDPcS1_P24st_ha_create_informationP10TABLE_LISTP10Alter_infojP8st_orderbb+0x2535)[0x7f880bf11dd5]
Feb  6 12:51:51 server06 mysqld: /usr/sbin/mysqld(_ZN21Alter_table_statement7executeEP3THD+0x4b3)[0x7f880c0f9863]
Feb  6 12:51:51 server06 mysqld: /usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x1952)[0x7f880be98372]
Feb  6 12:51:51 server06 mysqld: /usr/sbin/mysqld(+0x3a5887)[0x7f880be9c887]
Feb  6 12:51:51 server06 mysqld: /usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x148f)[0x7f880be9de6f]
Feb  6 12:51:51 server06 mysqld: /usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x21b)[0x7f880bf5311b]
Feb  6 12:51:51 server06 mysqld: /usr/sbin/mysqld(handle_one_connection+0x51)[0x7f880bf531a1]
Feb  6 12:51:51 server06 mysqld: /lib/x86_64-linux-gnu/libpthread.so.0(+0x6b50)[0x7f880b6bfb50]
Feb  6 12:51:51 server06 mysqld: /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f8809fe2a7d]
Feb  6 12:51:51 server06 mysqld: 
Feb  6 12:51:51 server06 mysqld: Trying to get some variables.
Feb  6 12:51:51 server06 mysqld: Some pointers may be invalid and cause the dump to abort.
Feb  6 12:51:51 server06 mysqld: Query (0x7f87d2d58018): is an invalid pointer
Feb  6 12:51:51 server06 mysqld: Connection ID (thread ID): 993964
Feb  6 12:51:51 server06 mysqld: Status: NOT_KILLED
Feb  6 12:51:51 server06 mysqld: 
Feb  6 12:51:51 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
Feb  6 12:51:51 server06 mysqld: 
Feb  6 12:51:51 server06 mysqld: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
Feb  6 12:51:51 server06 mysqld: information that should help you find out what is causing the crash.
Feb  6 12:51:52 server06 mysqld_safe: Number of processes running now: 0
Feb  6 12:51:52 server06 mysqld_safe: mysqld restarted
Feb  6 12:51:53 server06 mysqld: 140206 12:51:53 [Warning] The syntax '--log-slow-queries' is deprecated and will be removed in a future release. Please use '--slow-query-log'/'--slow-query-log-file' instead.
Feb  6 12:51:53 server06 mysqld: 140206 12:51:53 [Warning] An old style --language or -lc-message-dir value with language specific part detected: /usr/share/mysql/english/
Feb  6 12:51:53 server06 mysqld: 140206 12:51:53 [Warning] Use --lc-messages-dir without language specific part instead.
Feb  6 12:51:53 server06 mysqld: 140206 12:51:53 InnoDB: The InnoDB memory heap is disabled
Feb  6 12:51:53 server06 mysqld: 140206 12:51:53 InnoDB: Mutexes and rw_locks use GCC atomic builtins
Feb  6 12:51:53 server06 mysqld: 140206 12:51:53 InnoDB: Compressed tables use zlib 1.2.7
Feb  6 12:51:53 server06 mysqld: 140206 12:51:53 InnoDB: Using Linux native AIO
Feb  6 12:51:53 server06 mysqld: 140206 12:51:53 InnoDB: Initializing buffer pool, size = 16.0M
Feb  6 12:51:53 server06 mysqld: 140206 12:51:53 InnoDB: Completed initialization of buffer pool
Feb  6 12:51:53 server06 mysqld: 140206 12:51:53 InnoDB: highest supported file format is Barracuda.
Feb  6 12:51:53 server06 mysqld: InnoDB: The log sequence number in ibdata files does not match
Feb  6 12:51:53 server06 mysqld: InnoDB: the log sequence number in the ib_logfiles!
Feb  6 12:51:53 server06 mysqld: 140206 12:51:53  InnoDB: Database was not shut down normally!
Feb  6 12:51:53 server06 mysqld: InnoDB: Starting crash recovery.
Feb  6 12:51:53 server06 mysqld: InnoDB: Reading tablespace information from the .ibd files...
Feb  6 12:52:30 server06 mysqld: InnoDB: Restoring possible half-written data pages from the doublewrite
Feb  6 12:52:30 server06 mysqld: InnoDB: buffer...
Feb  6 12:52:31 server06 mysqld: InnoDB: 1 transaction(s) which must be rolled back or cleaned up
Feb  6 12:52:31 server06 mysqld: InnoDB: in total 2 row operations to undo
Feb  6 12:52:31 server06 mysqld: InnoDB: Trx id counter is B13A0E00
Feb  6 12:52:31 server06 mysqld: 140206 12:52:31  InnoDB: Rolling back trx with id B13A0C88, 2 rows to undo
Feb  6 12:52:31 server06 mysqld: 
Feb  6 12:52:31 server06 mysqld: InnoDB: Rolling back of trx id B13A0C88 completed
Feb  6 12:52:31 server06 mysqld: 140206 12:52:31  InnoDB: Error: table 'poppe_activereal/#sql-4bfb_3c2e1'
Feb  6 12:52:31 server06 mysqld: InnoDB: in InnoDB data dictionary has tablespace id 20702,
Feb  6 12:52:31 server06 mysqld: InnoDB: but the tablespace with that id has name ./poppe_activereal/estates.ibd.
Feb  6 12:52:31 server06 mysqld: InnoDB: Have you deleted or moved .ibd files?
Feb  6 12:52:31 server06 mysqld: InnoDB: Please refer to
Feb  6 12:52:31 server06 mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html
Feb  6 12:52:31 server06 mysqld: InnoDB: for how to resolve the issue.
Feb  6 12:52:31 server06 mysqld: 140206 12:52:31  InnoDB: Error: table 'poppe_kadernicky/#sql-7a9_daeb0a'
Feb  6 12:52:31 server06 mysqld: InnoDB: in InnoDB data dictionary has tablespace id 15600,
Feb  6 12:52:31 server06 mysqld: InnoDB: but tablespace with that id or name does not exist. Have
Feb  6 12:52:31 server06 mysqld: InnoDB: you deleted or moved .ibd files?
Feb  6 12:52:31 server06 mysqld: InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
Feb  6 12:52:31 server06 mysqld: InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
Feb  6 12:52:31 server06 mysqld: InnoDB: table still exists in the InnoDB internal data dictionary.
Feb  6 12:52:31 server06 mysqld: InnoDB: Please refer to
Feb  6 12:52:31 server06 mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html
Feb  6 12:52:31 server06 mysqld: InnoDB: for how to resolve the issue.
Feb  6 12:52:31 server06 mysqld: 140206 12:52:31  InnoDB: Error: table 'poppe_kadernicky/#sql2-7a9-daeb0a'
Feb  6 12:52:31 server06 mysqld: InnoDB: in InnoDB data dictionary has tablespace id 14084,
Feb  6 12:52:31 server06 mysqld: InnoDB: but tablespace with that id or name does not exist. Have
Feb  6 12:52:31 server06 mysqld: InnoDB: you deleted or moved .ibd files?
Feb  6 12:52:31 server06 mysqld: InnoDB: This may also be a table created with CREATE TEMPORARY TABLE
Feb  6 12:52:31 server06 mysqld: InnoDB: whose .ibd and .frm files MySQL automatically removed, but the
Feb  6 12:52:31 server06 mysqld: InnoDB: table still exists in the InnoDB internal data dictionary.
Feb  6 12:52:31 server06 mysqld: InnoDB: Please refer to
Feb  6 12:52:31 server06 mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html
Feb  6 12:52:31 server06 mysqld: InnoDB: for how to resolve the issue.
Feb  6 12:52:31 server06 mysqld: 140206 12:52:31  InnoDB: Error: table 'poppe_kupeldev2/#sql-6493_f2aac'
Feb  6 12:52:31 server06 mysqld: InnoDB: in InnoDB data dictionary has tablespace id 25329,
Feb  6 12:52:31 server06 mysqld: InnoDB: but the tablespace with that id has name ./poppe_kupeldev2/invoices.ibd.
Feb  6 12:52:31 server06 mysqld: InnoDB: Have you deleted or moved .ibd files?
Feb  6 12:52:31 server06 mysqld: InnoDB: Please refer to
Feb  6 12:52:31 server06 mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html
Feb  6 12:52:31 server06 mysqld: InnoDB: for how to resolve the issue.
Feb  6 12:52:31 server06 mysqld: 140206 12:52:31  InnoDB: Error: table 'poppe_kupelnadev/#sql-737_4180f3'
Feb  6 12:52:31 server06 mysqld: InnoDB: in InnoDB data dictionary has tablespace id 24072,
Feb  6 12:52:31 server06 mysqld: InnoDB: but the tablespace with that id has name ./poppe_kupelnadev/attribute_values.ibd.
Feb  6 12:52:31 server06 mysqld: InnoDB: Have you deleted or moved .ibd files?
Feb  6 12:52:31 server06 mysqld: InnoDB: Please refer to
Feb  6 12:52:31 server06 mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html
Feb  6 12:52:31 server06 mysqld: InnoDB: for how to resolve the issue.
Feb  6 12:52:31 server06 mysqld: 140206 12:52:31  InnoDB: Waiting for the background threads to start
Feb  6 12:52:32 server06 mysqld: 140206 12:52:32 Percona XtraDB (http://www.percona.com) 5.5.35-MariaDB-33.0 started; log sequence number 349498190239
Feb  6 12:52:32 server06 mysqld: 140206 12:52:32 [Note] Plugin 'FEEDBACK' is disabled.
Feb  6 12:52:32 server06 mysqld: 140206 12:52:32 [Note] Server socket created on IP: '::'.
Feb  6 12:52:32 server06 mysqld: 140206 12:52:32 [Note] Event Scheduler: Loaded 0 events
Feb  6 12:52:32 server06 mysqld: 140206 12:52:32 [Note] /usr/sbin/mysqld: ready for connections.
Feb  6 12:52:32 server06 mysqld: Version: '5.5.35-MariaDB-1~wheezy-log'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  mariadb.org binary distribution
Feb  6 12:52:32 server06 mysqld: 140206 12:52:32 [Note] Event Scheduler: scheduler thread started with id 1