无法弄清楚MySQL服务器有什么问题。错误日志如下。我尝试了innodb恢复并删除文件并重新启动但它没有帮助。 http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html
InnoDB: Serious error! InnoDB is trying to free page 1344
InnoDB: though it is already marked as free in the tablespace!
InnoDB: The tablespace free space info is corrupt.
InnoDB: You may need to dump your InnoDB tables and recreate the whole
InnoDB: database!
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
160805 9:43:22 InnoDB: Assertion failure in thread 139839724754688 in file fsp0fsp.c line 3329
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.
16:43:22 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=0
max_threads=153
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 = 343009 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+0x35)[0x7ce5a5]
/usr/sbin/mysqld(handle_fatal_signal+0x4b4)[0x6a2f54]
/lib64/libpthread.so.0(+0xf7e0)[0x7f2f139367e0]
/lib64/libc.so.6(gsignal+0x35)[0x7f2f11f915e5]
/lib64/libc.so.6(abort+0x175)[0x7f2f11f92dc5]
/usr/sbin/mysqld[0x919d97]
/usr/sbin/mysqld[0x91a148]
/usr/sbin/mysqld[0x8bb858]
/usr/sbin/mysqld[0x97b427]
/usr/sbin/mysqld[0x97b9d8]
/usr/sbin/mysqld[0x96f907]
/usr/sbin/mysqld[0x88e7a7]
/usr/sbin/mysqld[0x882d6c]
/lib64/libpthread.so.0(+0x7aa1)[0x7f2f1392eaa1]
/lib64/libc.so.6(clone+0x6d)[0x7f2f12047aad]
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.
160805 09:43:22 mysqld_safe mysqld from pid file /var/lib/mysql/websult.arvixevps.com.pid ended
答案 0 :(得分：1)
InnoDB: Error: log file ./ib_logfile0 is of different size 0 33554432 bytes
InnoDB: than specified in the .cnf file 0 5242880 bytes!
当日志文件大小与其预期不同时，InnoDB不喜欢它。如果存在文件丢失或损坏的风险，则可能无法用于数据恢复。 MySQL关闭了，而不是冒着对数据造成进一步损害的风险。
默认文件大小为5MB。但是你拥有的日志文件的大小是32MB。因此，很明显您使用来配置将日志文件大小设置为32MB。可能有人删除了/etc/my.cnf文件，或者对其进行了编辑。
您可以编辑/etc/my.cnf并设置：
[mysqld]
innodb_log_file_size=33554432
然后重启MySQL服务。
＆＃34;您的数据库可能已损坏，或者您可能已复制InnoDB InnoDB：表空间，但未复制InnoDB日志文件。＆＃34;
这是非常不言自明的。我怀疑你（或其他人）试图在不了解MySQL的情况下移动文件。如果您有最近的备份，则可以删除ibdata1和ib_logfile*，启动MySQL，然后恢复备份。
如果您没有备份，则需要一位可以解决此问题的MySQL顾问。我建议https://twindb.com/mysql-data-recovery/或https://www.percona.com/solutions/fix/data-recovery获取专家帮助。
答案 1 :(得分：0)
尝试将以下内容添加到/etc/my.cnf
[mysqld] ...
innodb_force_recovery = 1