我有一台安装了OwnCloud应用程序的Linux Gentoo服务器。 它可以工作大约2个月没有任何问题，突然今天早上MySQL死了。 我试图重新启动mysql服务器，并在mysqld.err日志文件中有这个：
2015-04-16 21:39:59 28987 [Warning] No argument was provided to --log-bin,
and --log-bin-index was not used; so replication may break when this MySQL server acts as a master and has his hostname changed!! Please use '--log-bin=mysqld-bin' to avoid this problem.
2015-04-16 21:39:59 28987 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-04-16 21:39:59 28987 [Note] InnoDB: The InnoDB memory heap is disabled
2015-04-16 21:39:59 28987 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2015-04-16 21:39:59 28987 [Note] InnoDB: Memory barrier is not used
2015-04-16 21:39:59 28987 [Note] InnoDB: Compressed tables use zlib 1.2.8
2015-04-16 21:39:59 28987 [Note] InnoDB: Using Linux native AIO
2015-04-16 21:39:59 28987 [Note] InnoDB: Using CPU crc32 instructions
2015-04-16 21:39:59 28987 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2015-04-16 21:39:59 28987 [Note] InnoDB: Completed initialization of buffer pool
2015-04-16 21:39:59 28987 [Note] InnoDB: Highest supported file format is Barracuda.
2015-04-16 21:39:59 28987 [Note] InnoDB: The log sequence numbers 50092945 and 50092945 in ibdata files do not match the log sequence number 447541274 in the ib_logfiles!
2015-04-16 21:39:59 28987 [Note] InnoDB: Database was not shutdown normally!
2015-04-16 21:39:59 28987 [Note] InnoDB: Starting crash recovery.
2015-04-16 21:39:59 28987 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-04-16 21:39:59 28987 [Note] InnoDB: Restoring possible half-written data pages
2015-04-16 21:39:59 28987 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Last MySQL binlog file position 0 106756973, file name ./mysqld-bin.000032
18:39:59 UTC - mysqld got signal 11 ;
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.
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 134417 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
/usr/sbin/mysqld(my_print_stacktrace+0x29)[0x857f39]
/usr/sbin/mysqld(handle_fatal_signal+0x350)[0x628700]
/lib64/libpthread.so.0(+0x11260)[0x7f27d6403260]
/usr/sbin/mysqld[0x9a643a]
/usr/sbin/mysqld[0x9a744b]
/usr/sbin/mysqld[0x920e29]
/usr/sbin/mysqld[0x8692f7]
/usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x41)[0x58c251]
/usr/sbin/mysqld[0x6a131a]
/usr/sbin/mysqld(_Z11plugin_initPiPPci+0x7b8)[0x6a4238]
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x749)[0x5848a9]
/lib64/libc.so.6(__libc_start_main+0xf5)[0x7f27d5a71db5]
/usr/sbin/mysqld[0x57a935]
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.
在搜索并尝试我在互联网上找到的所有内容后，包括将数据库复制到另一台Linux服务器，我仍然无法启动mysql服务器。
我甚至将整个数据库复制到带有XAMPP MySQL服务器的Windows 7操作系统，当我尝试启动MySQL服务器时，它给我发出消息“应用程序遇到错误并需要关闭”，参考mysqld.exe < / p>
如何修复此数据库并使MySql服务器再次运行？
我想提一下，我没有使用任何复制，关于mysqld.err文件中的第一个警告，所以没问题。