Hi, I have 2 mariadb nodes on Debian 7.8. After a crash on first node, I can't restart the second one. The message I see in /var/log/mysql/error.log is: 150430 12:55:48 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... 150430 12:55:48 InnoDB: Error: page 7 log sequence number 565808461991 InnoDB: is in the future! Current system log sequence number 565772838412. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html InnoDB: for more information. 150430 12:55:48 InnoDB: Error: page 2 log sequence number 565929024045 InnoDB: is in the future! Current system log sequence number 565772838412. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html InnoDB: for more information. .. .. 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.5/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 150430 12:55:48 [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: 5.5.42-MariaDB-1~wheezy-wsrep-log key_buffer_size=134217728 read_buffer_size=2097152 max_used_connections=0 max_threads=4098 thread_count=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 25383890 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0x0 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 = 0x0 thread_stack 0x30000 /usr/sbin/mysqld(my_print_stacktrace+0x2b)[0x7f3cc9d0c53b] /usr/sbin/mysqld(handle_fatal_signal+0x422)[0x7f3cc993a4f2] /lib/x86_64-linux-gnu/libpthread.so.0(+0xf0a0)[0x7f3cc900f0a0] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x35)[0x7f3cc786c165] /lib/x86_64-linux-gnu/libc.so.6(abort+0x180)[0x7f3cc786f3e0] /usr/sbin/mysqld(+0x73b5dc)[0x7f3cc9b795dc] /usr/sbin/mysqld(+0x709617)[0x7f3cc9b47617] /usr/sbin/mysqld(+0x70a41a)[0x7f3cc9b4841a] /usr/sbin/mysqld(+0x6f25d8)[0x7f3cc9b305d8] /usr/sbin/mysqld(+0x6c4733)[0x7f3cc9b02733] /usr/sbin/mysqld(+0x6b72d2)[0x7f3cc9af52d2] /usr/sbin/mysqld(+0x6b812c)[0x7f3cc9af612c] /usr/sbin/mysqld(+0x6bad41)[0x7f3cc9af8d41] /usr/sbin/mysqld(+0x6a3db5)[0x7f3cc9ae1db5] /usr/sbin/mysqld(+0x659d1f)[0x7f3cc9a97d1f] /usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x48)[0x7f3cc993ce78] /usr/sbin/mysqld(+0x3bb550)[0x7f3cc97f9550] /usr/sbin/mysqld(_Z11plugin_initPiPPci+0x652)[0x7f3cc97fa592] /usr/sbin/mysqld(+0x32b118)[0x7f3cc9769118] /usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x2036)[0x7f3cc976b9b6] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xfd)[0x7f3cc7858ead] /usr/sbin/mysqld(+0x321a4d)[0x7f3cc975fa4d] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash.' how can I solve this issue? First node is ok, all databases are available. Thank you