mysql 启动报错

Posted wonderful day

tags:

篇首语:本文由小常识网(cha138.com)小编为大家整理,主要介绍了mysql 启动报错相关的知识,希望对你有一定的参考价值。

之前用我这个机器做mysql的测试来,今天启动准备搭建一套线上的主从,结果起不来了。。。

 

错误日志:

                                                                                                                                                                                                                       ;InnoDB: End of page dump
170807 11:37:02  InnoDB: Page checksum 1575996416, prior-to-4.0.14-form checksum 1371122432
InnoDB: stored checksum 0, prior-to-4.0.14-form stored checksum 0
InnoDB: Page lsn 0 0, low 4 bytes of lsn at page end 0
InnoDB: Page number (if stored to page already) 0,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: Page may be a freshly allocated page
170807 11:37:02InnoDB: Error: trying to access a stray pointer 0x80007f66af393ff8
InnoDB: buf pool start is at 0x7f66af384000, end at 0x7f66afb84000
InnoDB: Probable reason is database corruption or memory
InnoDB: corruption. If this happens in an InnoDB database recovery, see
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html
InnoDB: how to force recovery.
170807 11:37:02  InnoDB: Assertion failure in thread 140079112959968 in file ../../storage/innobase/include/buf0buf.ic line 264
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.1/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
03:37:02 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=8384512
read_buffer_size=131072
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 = 338336 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/libexec/mysqld(my_print_stacktrace+0x29) [0x850ca9]
/usr/libexec/mysqld(handle_fatal_signal+0x483) [0x6a4143]
/lib64/libpthread.so.0() [0x3514e0f7e0]
/lib64/libc.so.6(gsignal+0x35) [0x3514a32625]
/lib64/libc.so.6(abort+0x175) [0x3514a33e05]
/usr/libexec/mysqld(page_cur_search_with_match+0x77b) [0x79855b]
/usr/libexec/mysqld(btr_cur_search_to_nth_level+0x6ea) [0x73bd9a]
/usr/libexec/mysqld(btr_pcur_open_on_user_rec+0x64) [0x7eab34]
/usr/libexec/mysqld() [0x75a46f]
/usr/libexec/mysqld(dict_load_sys_table+0x59) [0x7602d9]
/usr/libexec/mysqld(dict_boot+0x91c) [0x7ebf6c]
/usr/libexec/mysqld(innobase_start_or_create_for_mysql+0x11f6) [0x7c8466]
/usr/libexec/mysqld() [0x72f84b]
/usr/libexec/mysqld(ha_initialize_handlerton(st_plugin_int*)+0x31) [0x697b91]
/usr/libexec/mysqld() [0x7177db]
/usr/libexec/mysqld(plugin_init(int*, char**, int)+0x6e4) [0x719ad4]
/usr/libexec/mysqld() [0x5bf242]
/usr/libexec/mysqld(main+0x1b3) [0x5c1bb3]
/lib64/libc.so.6(__libc_start_main+0xfd) [0x3514a1ed5d]
/usr/libexec/mysqld() [0x509939]
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.
170807 11:37:02 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended

  

看日志信息应该是异常关闭导致库损坏,找了一下帖子解决:

[[email protected] mysql]# cd /var/lib/mysql
[[email protected] mysql]# ll
total 20496
drwx------ 2 mysql mysql     4096 Jul 19 05:49 hotel_cdn_control
-rw-rw---- 1 mysql mysql 10485760 Aug  7 11:41 ibdata1
-rw-rw---- 1 mysql mysql  5242880 Aug  7 11:41 ib_logfile0
-rw-rw---- 1 mysql mysql  5242880 Aug  7 11:41 ib_logfile1
drwx------ 2 mysql mysql     4096 Jul 19 03:44 mysql
srwxrwxrwx 1 mysql mysql        0 Aug  7 11:41 mysql.sock
drwxr-xr-x 2 root  root      4096 Aug  7 11:41 old
drwx------ 2 mysql mysql     4096 Jul 19 03:44 test
[[email protected] mysql]# mkdir bcksql
[[email protected] mysql]# mv *ib* bcksql
[[email protected] mysql]# service mysqld start

  已解决。

 

以上是关于mysql 启动报错的主要内容,如果未能解决你的问题,请参考以下文章

Nginx——Nginx启动报错Job for nginx.service failed because the control process exited with error code(代码片段

项目启动报错Failed to configure a DataSource: 'url' attribute is not specified and no embedde(代码片段

mysql启动报错:由于找不到vcruntime140_1.dll,无法继续执行代码

Vue报错:Uncaught TypeError: Cannot assign to read only property 'exports' of object 的解决方法(代码片段

从mysql的片段中加载ListView

连接MySQL出现错误:ERROR 1045 (28000): Access denied for user ‘root‘@‘localhost‘ (using password: YES)(代码片段