VPS重启后MYSQL启动不起了求助

kua5

1. Usage: /root/lnmp {start|stop|reload|restart|kill|status}
   
2. =========================================================================
   
3. Stoping LNMP...
   
4. Stopping nginx daemon: nginx.
   
5. Gracefully shutting down php-fpm . done
   
6. ERROR! MySQL server PID file could not be found!
   
7. Starting LNMP...
   
8. Starting nginx daemon: nginx.
   
9. Starting php-fpm  done
   
10. Starting MySQL.. ERROR! The server quit without updating PID file (/usr/local/mysql/var/default.hostname.pid).
    
11. 
    
12. Exit code: 1

复制代码

1. [root /]# ps aux |grep mysq*
   
2. root      4239  0.0  0.1   3040  1168 ?        Ss   17:34   0:00 /bin/bash -c cd "/"; ps aux |grep mysq* 2>&1 | head -n 10000; echo
   
3. [root /]# kill 4239
   
4. /bin/bash: line 0: kill: (4239) - No such process
   
5. 
   
6. Exit code: 1
   
7. [root /]# service mysql start
   
8. Starting MySQL........ ERROR! The server quit without updating PID file (/usr/local/mysql/var/default.hostname.pid).
   
9. 
   
10. Exit code: 1

复制代码

1. It is possible that mysqld could use up to
   
2. key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 133456 K  bytes of memory
   
3. Hope that's ok; if not, decrease some variables in the equation.
   
4. 
   
5. Thread pointer: 0x0
   
6. Attempting backtrace. You can use the following information to find out
   
7. where mysqld died. If you see no messages after this, something went
   
8. terribly wrong...
   
9. stack_bottom = 0 thread_stack 0x30000
   
10. /usr/local/mysql/bin/mysqld(my_print_stacktrace+0x33)[0x838ba93]
    
11. /usr/local/mysql/bin/mysqld(handle_fatal_signal+0x432)[0x8280d72]
    
12. [0xb7769500]
    
13. /lib/libc.so.6(abort+0x17a)[0xb726d3aa]
    
14. /usr/local/mysql/bin/mysqld[0x842fef8]
    
15. /usr/local/mysql/bin/mysqld[0x8430477]
    
16. /usr/local/mysql/bin/mysqld[0x84e64be]
    
17. /usr/local/mysql/bin/mysqld[0x84dd1fe]
    
18. /usr/local/mysql/bin/mysqld[0x842ed8e]
    
19. /usr/local/mysql/bin/mysqld[0x84225d5]
    
20. /usr/local/mysql/bin/mysqld[0x84250f7]
    
21. /lib/libpthread.so.0(+0x6a49)[0xb774ba49]
    
22. /lib/libc.so.6(clone+0x5e)[0xb7323aae]
    
23. The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
    
24. information that should help you find out what is causing the crash.
    
25. 160703 17:35:58 mysqld_safe mysqld from pid file /usr/local/mysql/var/default.hostname.pid ended

复制代码

kua5

错误信息。。。

1. key_buffer_size=16777216
   
2. read_buffer_size=262144
   
3. max_used_connections=0
   
4. max_threads=151
   
5. thread_count=0
   
6. connection_count=0
   
7. It is possible that mysqld could use up to
   
8. key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 133456 K  bytes of memory
   
9. Hope that's ok; if not, decrease some variables in the equation.
   
10. 
    
11. Thread pointer: 0x0
    
12. Attempting backtrace. You can use the following information to find out
    
13. where mysqld died. If you see no messages after this, something went
    
14. terribly wrong...
    
15. stack_bottom = 0 thread_stack 0x30000
    
16. /usr/local/mysql/bin/mysqld(my_print_stacktrace+0x33)[0x838ba93]
    
17. /usr/local/mysql/bin/mysqld(handle_fatal_signal+0x432)[0x8280d72]
    
18. [0xb77bd500]
    
19. /lib/libc.so.6(abort+0x17a)[0xb72c13aa]
    
20. /usr/local/mysql/bin/mysqld[0x842fef8]
    
21. /usr/local/mysql/bin/mysqld[0x8430477]
    
22. /usr/local/mysql/bin/mysqld[0x84e64be]
    
23. 160703 17:58:02 [Note] Event Scheduler: Loaded 0 events
    
24. 160703 17:58:02 [Note] /usr/local/mysql/bin/mysqld: ready for connections.
    
25. Version: '5.5.28-log'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
    
26. /usr/local/mysql/bin/mysqld[0x84dd1fe]
    
27. /usr/local/mysql/bin/mysqld[0x842ed8e]
    
28. /usr/local/mysql/bin/mysqld[0x84225d5]
    
29. /usr/local/mysql/bin/mysqld[0x84250f7]
    
30. /lib/libpthread.so.0(+0x6a49)[0xb779fa49]
    
31. /lib/libc.so.6(clone+0x5e)[0xb7377aae]
    
32. The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
    
33. information that should help you find out what is causing the crash.
    
34. 160703 17:58:02 mysqld_safe Number of processes running now: 0
    
35. 160703 17:58:02 mysqld_safe mysqld restarted
    
36. 160703 17:58:02 InnoDB: The InnoDB memory heap is disabled
    
37. 160703 17:58:02 InnoDB: Mutexes and rw_locks use GCC atomic builtins
    
38. 160703 17:58:02 InnoDB: Compressed tables use zlib 1.2.3
    
39. 160703 17:58:02 InnoDB: Initializing buffer pool, size = 16.0M
    
40. 160703 17:58:02 InnoDB: Completed initialization of buffer pool
    
41. 160703 17:58:02 InnoDB: highest supported file format is Barracuda.
    
42. InnoDB: The log sequence number in ibdata files does not match
    
43. InnoDB: the log sequence number in the ib_logfiles!
    
44. 160703 17:58:02  InnoDB: Database was not shut down normally!
    
45. InnoDB: Starting crash recovery.
    
46. InnoDB: Reading tablespace information from the .ibd files...
    
47. InnoDB: Restoring possible half-written data pages from the doublewrite
    
48. InnoDB: buffer...
    
49. InnoDB: Last MySQL binlog file position 0 5602, file name ./mysql-bin.000126
    
50. 160703 17:58:02  InnoDB: Waiting for the background threads to start
    
51. 160703 17:58:03 InnoDB: 1.1.8 started; log sequence number 4422896040
    
52. 160703 17:58:03 [Note] Recovering after a crash using mysql-bin
    
53. 160703 17:58:03 [Note] Starting crash recovery...
    
54. 160703 17:58:03 [Note] Crash recovery finished.
    
55. 160703 17:58:03 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
    
56. 160703 17:58:03 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
    
57. 160703 17:58:03 [Note] Server socket created on IP: '0.0.0.0'.
    
58. 160703 17:58:03  InnoDB: Assertion failure in thread 2874518384 in file trx0purge.c line 829
    
59. InnoDB: Failing assertion: purge_sys->purge_trx_no <= purge_sys->rseg->last_trx_no
    
60. InnoDB: We intentionally generate a memory trap.
    
61. InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
    
62. InnoDB: If you get repeated assertion failures or crashes, even
    
63. InnoDB: immediately after the mysqld startup, there may be
    
64. InnoDB: corruption in the InnoDB tablespace. Please refer to
    
65. InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
    
66. InnoDB: about forcing recovery.
    
67. 09:58:03 UTC - mysqld got signal 6 ;
    
68. This could be because you hit a bug. It is also possible that this binary
    
69. or one of the libraries it was linked against is corrupt, improperly built,
    
70. or misconfigured. This error can also be caused by malfunctioning hardware.
    
71. We will try our best to scrape up some info that will hopefully help
    
72. diagnose the problem, but since we have already crashed,
    
73. something is definitely wrong and this may fail.
    
74. 
    
75. key_buffer_size=16777216
    
76. read_buffer_size=262144
    
77. max_used_connections=0
    
78. max_threads=151
    
79. thread_count=0
    
80. connection_count=0
    
81. It is possible that mysqld could use up to
    
82. key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 133456 K  bytes of memory
    
83. Hope that's ok; if not, decrease some variables in the equation.
    
84. 
    
85. Thread pointer: 0x0
    
86. Attempting backtrace. You can use the following information to find out
    
87. where mysqld died. If you see no messages after this, something went
    
88. terribly wrong...
    
89. stack_bottom = 0 thread_stack 0x30000
    
90. /usr/local/mysql/bin/mysqld(my_print_stacktrace+0x33)[0x838ba93]
    
91. /usr/local/mysql/bin/mysqld(handle_fatal_signal+0x432)[0x8280d72]
    
92. [0xb7728500]
    
93. /lib/libc.so.6(abort+0x17a)[0xb722c3aa]
    
94. /usr/local/mysql/bin/mysqld[0x842fef8]
    
95. /usr/local/mysql/bin/mysqld[0x8430477]
    
96. /usr/local/mysql/bin/mysqld[0x84e64be]
    
97. /usr/local/mysql/bin/mysqld[0x84dd1fe]
    
98. /usr/local/mysql/bin/mysqld[0x842ed8e]
    
99. /usr/local/mysql/bin/mysqld[0x84225d5]
    
100. /usr/local/mysql/bin/mysqld[0x84250f7]
     
101. /lib/libpthread.so.0(+0x6a49)[0xb770aa49]
     
102. /lib/libc.so.6(clone+0x5e)[0xb72e2aae]
     
103. The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
     
104. information that should help you find out what is causing the crash.
     
105. 160703 17:58:03 mysqld_safe mysqld from pid file /usr/local/mysql/var/default.hostname.pid ended

复制代码

licess

首先检查硬盘或分区占用情况，不行的话再试试看https://bbs.vpser.net/thread-13040-1-1.html

kua5

innodb_force_recovery=6
加上这个 可以正常启动
修复了数据库 有些提示不能直接修复的
去掉innodb_force_recovery=6后 还是 原来那样