首页 > 动态 > 常见问题 >

mysql 解决一个奇怪的问题,详见正文

发布时间:2017-04-28 作者:故乡人  浏览:

错误日志报错如下:

130508 16:30:53 mysqld_safe Starting mysqld daemon with databases from /data/mysql
130508 16:30:54 [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.
130508 16:30:54 InnoDB: The InnoDB memory heap is disabled
130508 16:30:54 InnoDB: Mutexes and rw_locks use GCC atomic builtins
130508 16:30:54 InnoDB: Compressed tables use zlib 1.2.3
130508 16:30:54 InnoDB: Initializing buffer pool, size = 500.0M
130508 16:30:54 InnoDB: Completed initialization of buffer pool
130508 16:30:54 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 27219795678
130508 16:30:54  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...
InnoDB: Doing recovery: scanned up to log sequence number 27219928522
InnoDB: Error: tried to read 16384 bytes at offset 0 3473408.
InnoDB: Was only able to read 8192.
InnoDB: Fatal error: cannot read from file. OS error number 17.
130508 16:31:05  InnoDB: Assertion failure in thread 47198419330368 in file os0file.c line 2523
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.
08:31:05 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.

key_buffer_size=16777216
read_buffer_size=1048576
max_used_connections=0
max_threads=500
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 = 1046083 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/local/mysql/bin/mysqld(my_print_stacktrace+0x2e)[0x76a3ee]
/usr/local/mysql/bin/mysqld(handle_fatal_signal+0x386)[0x655046]
/lib64/libpthread.so.0[0x3fade0ebe0]
/lib64/libc.so.6(gsignal+0x35)[0x3fad630265]
/lib64/libc.so.6(abort+0x110)[0x3fad631d10]
/usr/local/mysql/bin/mysqld[0x85bfc4]
/usr/local/mysql/bin/mysqld[0x822641]
/usr/local/mysql/bin/mysqld[0x801597]
/usr/local/mysql/bin/mysqld[0x801a4f]
/usr/local/mysql/bin/mysqld[0x7f4240]
/usr/local/mysql/bin/mysqld[0x7c5c40]
/usr/local/mysql/bin/mysqld[0x7c5fa2]
/usr/local/mysql/bin/mysqld[0x7c7727]
/usr/local/mysql/bin/mysqld[0x7b61b6]
/usr/local/mysql/bin/mysqld[0x78787a]
/usr/local/mysql/bin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x41)[0x657231]
/usr/local/mysql/bin/mysqld[0x56714b]
/usr/local/mysql/bin/mysqld(_Z11plugin_initPiPPci+0xa42)[0x567d12]
/usr/local/mysql/bin/mysqld[0x4f21b2]
/usr/local/mysql/bin/mysqld(_Z11mysqld_mainiPPc+0x865)[0x4f4ec5]
/lib64/libc.so.6(__libc_start_main+0xf4)[0x3fad61d994]
/usr/local/mysql/bin/mysqld[0x4ed769]
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.
130508 16:31:05 mysqld_safe mysqld from pid file /data/mysql/log/scaner.pid ended


解决办法: 
删除掉 
ibdata* ,
ib_logfile* ,
所有的日志。
重启后可启动数据库,因数据库是非正常关闭引起的。所有会造成数据丢失。 要做好备份工作

文章标题:mysql 解决一个奇怪的问题,详见正文
本文地址:http://www.eit0571.com//news/cjwt/458.html
推荐标签:杭州网站建设 | 杭州APP开发公司 | 杭州APP开发 | 杭州网站制作
如果您觉得案例还不错请帮忙分享:

推荐新闻


杭州APP开发公司故乡人网络 故乡人开发-价格优惠-APP开发-建设专业网站设计-手机微信PC多网合一 杭州网站制作杭州网站建设

浙公网安备 33011802000524号