Guest User

ERROR 2002 (HY000): Can't connect to local MySQL server

a guest
Oct 5th, 2014
221
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
MySQL 24.67 KB | None | 0 0
  1. key_buffer_size=16777216
  2. read_buffer_size=131072
  3. 141005 15:13:56max_used_connections=0
  4. max_threads=151
  5.  InnoDB: 5.5.38 started; log sequence number 2455246113
  6. thread_count=0
  7. connection_count=0
  8. It is possible that mysqld could use up to
  9. key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 346700 K  bytes of memory
  10. Hope that's ok; if not, decrease some variables in the equation.
  11.  
  12. Thread pointer: 0x0
  13. Attempting backtrace. You can use the following information to find out
  14. where mysqld died. If you see no messages after this, something went
  15. terribly wrong...
  16. stack_bottom = 0 thread_stack 0x30000
  17. 141005 15:13:56 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
  18. 141005 15:13:56 [Note]   - '127.0.0.1' resolves to '127.0.0.1';
  19. 141005 15:13:56 [Note] Server socket created on IP: '127.0.0.1'.
  20. /usr/sbin/mysqld(my_print_stacktrace+0x20)[0x7fa26639ef20]
  21. /usr/sbin/mysqld(handle_fatal_signal+0x3d5)[0x7fa2662898d5]
  22. /lib/x86_64-linux-gnu/libpthread.so.0(+0x10340)[0x7fa264ff8340]
  23. /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x39)[0x7fa264646bb9]
  24. /lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7fa264649fc8]
  25. /usr/sbin/mysqld(+0x2732d0)[0x7fa2661232d0]
  26. /usr/sbin/mysqld(+0x58b836)[0x7fa26643b836]
  27. /usr/sbin/mysqld(+0x58bbcd)[0x7fa26643bbcd]
  28. /usr/sbin/mysqld(+0x64d16f)[0x7fa2664fd16f]
  29. /usr/sbin/mysqld(+0x643ab5)[0x7fa2664f3ab5]
  30. /usr/sbin/mysqld(+0x58da45)[0x7fa26643da45]
  31. /usr/sbin/mysqld(+0x57f65c)[0x7fa26642f65c]
  32. /usr/sbin/mysqld(+0x583733)[0x7fa266433733]
  33. /lib/x86_64-linux-gnu/libpthread.so.0(+0x8182)[0x7fa264ff0182]
  34. /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7fa26470afbd]
  35. The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
  36. information that should help you find out what is causing the crash.
  37. 141005 15:13:57 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
  38. 141005 15:13:57 [Note] Plugin 'FEDERATED' is disabled.
  39. 141005 15:13:57 InnoDB: The InnoDB memory heap is disabled
  40. 141005 15:13:57 InnoDB: Mutexes and rw_locks use GCC atomic builtins
  41. 141005 15:13:57 InnoDB: Compressed tables use zlib 1.2.8
  42. 141005 15:13:57 InnoDB: Using Linux native AIO
  43. 141005 15:13:57 InnoDB: Initializing buffer pool, size = 128.0M
  44. 141005 15:13:57 InnoDB: Completed initialization of buffer pool
  45. 141005 15:13:57 InnoDB: highest supported file format is Barracuda.
  46. 141005 15:13:57  InnoDB: Error: page 5 log sequence number 2455516206
  47. InnoDB: is in the future! Current system log sequence number 2455246113.
  48. InnoDB: Your database may be corrupt or you may have copied the InnoDB
  49. InnoDB: tablespace but not the InnoDB log files. See
  50. InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
  51. InnoDB: for more information.
  52. 141005 15:13:57  InnoDB: Error: page 51 log sequence number 2455632585
  53. InnoDB: is in the future! Current system log sequence number 2455246113.
  54. InnoDB: Your database may be corrupt or you may have copied the InnoDB
  55. InnoDB: tablespace but not the InnoDB log files. See
  56. InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
  57. InnoDB: for more information.
  58. 141005 15:13:57  InnoDB: Error: page 56 log sequence number 2455644510
  59. InnoDB: is in the future! Current system log sequence number 2455246113.
  60. InnoDB: Your database may be corrupt or you may have copied the InnoDB
  61. InnoDB: tablespace but not the InnoDB log files. See
  62. InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
  63. InnoDB: for more information.
  64. 141005 15:13:57  InnoDB: Error: page 2560 log sequence number 2455258974
  65. InnoDB: is in the future! Current system log sequence number 2455246113.
  66. InnoDB: Your database may be corrupt or you may have copied the InnoDB
  67. InnoDB: tablespace but not the InnoDB log files. See
  68. InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
  69. InnoDB: for more information.
  70. 141005 15:13:57  InnoDB: Error: page 2561 log sequence number 2455270772
  71. InnoDB: is in the future! Current system log sequence number 2455246113.
  72. InnoDB: Your database may be corrupt or you may have copied the InnoDB
  73. InnoDB: tablespace but not the InnoDB log files. See
  74. InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
  75. InnoDB: for more information.
  76. 141005 15:13:57  InnoDB: Error: page 2600 log sequence number 2455282596
  77. InnoDB: is in the future! Current system log sequence number 2455246113.
  78. InnoDB: Your database may be corrupt or you may have copied the InnoDB
  79. InnoDB: tablespace but not the InnoDB log files. See
  80. InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
  81. InnoDB: for more information.
  82. 141005 15:13:57  InnoDB: Error: page 2619 log sequence number 2455296303
  83. InnoDB: is in the future! Current system log sequence number 2455246113.
  84. InnoDB: Your database may be corrupt or you may have copied the InnoDB
  85. InnoDB: tablespace but not the InnoDB log files. See
  86. InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
  87. InnoDB: for more information.
  88. 141005 15:13:57  InnoDB: Error: page 2587 log sequence number 2455321908
  89. InnoDB: is in the future! Current system log sequence number 2455246113.
  90. InnoDB: Your database may be corrupt or you may have copied the InnoDB
  91. InnoDB: tablespace but not the InnoDB log files. See
  92. InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
  93. InnoDB: for more information.
  94. 141005 15:13:57  InnoDB: Error: page 2603 log sequence number 2455336696
  95. InnoDB: is in the future! Current system log sequence number 2455246113.
  96. InnoDB: Your database may be corrupt or you may have copied the InnoDB
  97. InnoDB: tablespace but not the InnoDB log files. See
  98. InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
  99. InnoDB: for more information.
  100. 141005 15:13:57  InnoDB: Error: page 1590 log sequence number 2455362122
  101. InnoDB: is in the future! Current system log sequence number 2455246113.
  102. InnoDB: Your database may be corrupt or you may have copied the InnoDB
  103. InnoDB: tablespace but not the InnoDB log files. See
  104. InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
  105. InnoDB: for more information.
  106. 141005 15:13:57  InnoDB: Error: page 2563 log sequence number 2455373946
  107. InnoDB: is in the future! Current system log sequence number 2455246113.
  108. InnoDB: Your database may be corrupt or you may have copied the InnoDB
  109. InnoDB: tablespace but not the InnoDB log files. See
  110. InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
  111. InnoDB: for more information.
  112. 141005 15:13:57  InnoDB: Error: page 2107 log sequence number 2455411915
  113. InnoDB: is in the future! Current system log sequence number 2455246113.
  114. InnoDB: Your database may be corrupt or you may have copied the InnoDB
  115. InnoDB: tablespace but not the InnoDB log files. See
  116. InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
  117. InnoDB: for more information.
  118. 141005 15:13:57  InnoDB: Error: page 2607 log sequence number 2455425623
  119. InnoDB: is in the future! Current system log sequence number 2455246113.
  120. InnoDB: Your database may be corrupt or you may have copied the InnoDB
  121. InnoDB: tablespace but not the InnoDB log files. See
  122. InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
  123. InnoDB: for more information.
  124. 141005 15:13:57  InnoDB: Error: page 2608 log sequence number 2455425851
  125. InnoDB: is in the future! Current system log sequence number 2455246113.
  126. InnoDB: Your database may be corrupt or you may have copied the InnoDB
  127. InnoDB: tablespace but not the InnoDB log files. See
  128. InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
  129. InnoDB: for more information.
  130. 141005 15:13:57  InnoDB: Error: page 2590 log sequence number 2455426095
  131. InnoDB: is in the future! Current system log sequence number 2455246113.
  132. InnoDB: Your database may be corrupt or you may have copied the InnoDB
  133. InnoDB: tablespace but not the InnoDB log files. See
  134. InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
  135. InnoDB: for more information.
  136. 141005 15:13:57  InnoDB: Error: page 256 log sequence number 2455426323
  137. InnoDB: is in the future! Current system log sequence number 2455246113.
  138. InnoDB: Your database may be corrupt or you may have copied the InnoDB
  139. InnoDB: tablespace but not the InnoDB log files. See
  140. InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
  141. InnoDB: for more information.
  142. 141005 15:13:57  InnoDB: Error: page 1645 log sequence number 2455426323
  143. InnoDB: is in the future! Current system log sequence number 2455246113.
  144. InnoDB: Your database may be corrupt or you may have copied the InnoDB
  145. InnoDB: tablespace but not the InnoDB log files. See
  146. InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
  147. InnoDB: for more information.
  148. 141005 15:13:57  InnoDB: Error: page 257 log sequence number 2455438973
  149. InnoDB: is in the future! Current system log sequence number 2455246113.
  150. InnoDB: Your database may be corrupt or you may have copied the InnoDB
  151. InnoDB: tablespace but not the InnoDB log files. See
  152. InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
  153. InnoDB: for more information.
  154. 141005 15:13:57  InnoDB: Error: page 2545 log sequence number 2455438973
  155. InnoDB: is in the future! Current system log sequence number 2455246113.
  156. InnoDB: Your database may be corrupt or you may have copied the InnoDB
  157. InnoDB: tablespace but not the InnoDB log files. See
  158. InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
  159. InnoDB: for more information.
  160. 141005 15:13:57  InnoDB: Error: page 260 log sequence number 2455450797
  161. InnoDB: is in the future! Current system log sequence number 2455246113.
  162. InnoDB: Your database may be corrupt or you may have copied the InnoDB
  163. InnoDB: tablespace but not the InnoDB log files. See
  164. InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
  165. InnoDB: for more information.
  166. 141005 15:13:57  InnoDB: Error: page 261 log sequence number 2455464261
  167. InnoDB: is in the future! Current system log sequence number 2455246113.
  168. InnoDB: Your database may be corrupt or you may have copied the InnoDB
  169. InnoDB: tablespace but not the InnoDB log files. See
  170. InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
  171. InnoDB: for more information.
  172. 141005 15:13:57  InnoDB: Error: page 2546 log sequence number 2455464261
  173. InnoDB: is in the future! Current system log sequence number 2455246113.
  174. InnoDB: Your database may be corrupt or you may have copied the InnoDB
  175. InnoDB: tablespace but not the InnoDB log files. See
  176. InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
  177. InnoDB: for more information.
  178. 141005 15:13:57  InnoDB: Error: page 263 log sequence number 2455464505
  179. InnoDB: is in the future! Current system log sequence number 2455246113.
  180. InnoDB: Your database may be corrupt or you may have copied the InnoDB
  181. InnoDB: tablespace but not the InnoDB log files. See
  182. InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
  183. InnoDB: for more information.
  184. 141005 15:13:57  InnoDB: Error: page 1594 log sequence number 2455464505
  185. InnoDB: is in the future! Current system log sequence number 2455246113.
  186. InnoDB: Your database may be corrupt or you may have copied the InnoDB
  187. InnoDB: tablespace but not the InnoDB log files. See
  188. InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
  189. InnoDB: for more information.
  190. 141005 15:13:57  InnoDB: Error: page 268 log sequence number 2455464733
  191. InnoDB: is in the future! Current system log sequence number 2455246113.
  192. InnoDB: Your database may be corrupt or you may have copied the InnoDB
  193. InnoDB: tablespace but not the InnoDB log files. See
  194. InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
  195. InnoDB: for more information.
  196. 141005 15:13:57  InnoDB: Error: page 2593 log sequence number 2455464733
  197. InnoDB: is in the future! Current system log sequence number 2455246113.
  198. InnoDB: Your database may be corrupt or you may have copied the InnoDB
  199. InnoDB: tablespace but not the InnoDB log files. See
  200. InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
  201. InnoDB: for more information.
  202. 141005 15:13:57  InnoDB: Error: page 271 log sequence number 2455465105
  203. InnoDB: is in the future! Current system log sequence number 2455246113.
  204. InnoDB: Your database may be corrupt or you may have copied the InnoDB
  205. InnoDB: tablespace but not the InnoDB log files. See
  206. InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
  207. InnoDB: for more information.
  208. 141005 15:13:57  InnoDB: Error: page 2623 log sequence number 2455465105
  209. InnoDB: is in the future! Current system log sequence number 2455246113.
  210. InnoDB: Your database may be corrupt or you may have copied the InnoDB
  211. InnoDB: tablespace but not the InnoDB log files. See
  212. InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
  213. InnoDB: for more information.
  214. 141005 15:13:57  InnoDB: Error: page 274 log sequence number 2455477855
  215. InnoDB: is in the future! Current system log sequence number 2455246113.
  216. InnoDB: Your database may be corrupt or you may have copied the InnoDB
  217. InnoDB: tablespace but not the InnoDB log files. See
  218. InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
  219. InnoDB: for more information.
  220. 141005 15:13:57  InnoDB: Error: page 275 log sequence number 2455478083
  221. InnoDB: is in the future! Current system log sequence number 2455246113.
  222. InnoDB: Your database may be corrupt or you may have copied the InnoDB
  223. InnoDB: tablespace but not the InnoDB log files. See
  224. InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
  225. InnoDB: for more information.
  226. 141005 15:13:57  InnoDB: Error: page 2509 log sequence number 2455478083
  227. InnoDB: is in the future! Current system log sequence number 2455246113.
  228. InnoDB: Your database may be corrupt or you may have copied the InnoDB
  229. InnoDB: tablespace but not the InnoDB log files. See
  230. InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
  231. InnoDB: for more information.
  232. 141005 15:13:57  InnoDB: Error: page 276 log sequence number 2455479059
  233. InnoDB: is in the future! Current system log sequence number 2455246113.
  234. InnoDB: Your database may be corrupt or you may have copied the InnoDB
  235. InnoDB: tablespace but not the InnoDB log files. See
  236. InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
  237. InnoDB: for more information.
  238. 141005 15:13:57  InnoDB: Error: page 2547 log sequence number 2455479059
  239. InnoDB: is in the future! Current system log sequence number 2455246113.
  240. InnoDB: Your database may be corrupt or you may have copied the InnoDB
  241. InnoDB: tablespace but not the InnoDB log files. See
  242. InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
  243. InnoDB: for more information.
  244. 141005 15:13:57  InnoDB: Error: page 278 log sequence number 2455490875
  245. InnoDB: is in the future! Current system log sequence number 2455246113.
  246. InnoDB: Your database may be corrupt or you may have copied the InnoDB
  247. InnoDB: tablespace but not the InnoDB log files. See
  248. InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
  249. InnoDB: for more information.
  250. 141005 15:13:57  InnoDB: Error: page 1738 log sequence number 2455490875
  251. InnoDB: is in the future! Current system log sequence number 2455246113.
  252. InnoDB: Your database may be corrupt or you may have copied the InnoDB
  253. InnoDB: tablespace but not the InnoDB log files. See
  254. InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
  255. InnoDB: for more information.
  256. 141005 15:13:57  InnoDB: Error: page 280 log sequence number 2455503447
  257. InnoDB: is in the future! Current system log sequence number 2455246113.
  258. InnoDB: Your database may be corrupt or you may have copied the InnoDB
  259. InnoDB: tablespace but not the InnoDB log files. See
  260. InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
  261. InnoDB: for more information.
  262. 141005 15:13:57  InnoDB: Error: page 2548 log sequence number 2455503447
  263. InnoDB: is in the future! Current system log sequence number 2455246113.
  264. InnoDB: Your database may be corrupt or you may have copied the InnoDB
  265. InnoDB: tablespace but not the InnoDB log files. See
  266. InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
  267. InnoDB: for more information.
  268. 141005 15:13:57  InnoDB: Error: page 281 log sequence number 2455516196
  269. InnoDB: is in the future! Current system log sequence number 2455246113.
  270. InnoDB: Your database may be corrupt or you may have copied the InnoDB
  271. InnoDB: tablespace but not the InnoDB log files. See
  272. InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
  273. InnoDB: for more information.
  274. 141005 15:13:57  InnoDB: Error: page 284 log sequence number 2455529799
  275. InnoDB: is in the future! Current system log sequence number 2455246113.
  276. InnoDB: Your database may be corrupt or you may have copied the InnoDB
  277. InnoDB: tablespace but not the InnoDB log files. See
  278. InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
  279. InnoDB: for more information.
  280. 141005 15:13:57  InnoDB: Error: page 2549 log sequence number 2455529799
  281. InnoDB: is in the future! Current system log sequence number 2455246113.
  282. InnoDB: Your database may be corrupt or you may have copied the InnoDB
  283. InnoDB: tablespace but not the InnoDB log files. See
  284. InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
  285. InnoDB: for more information.
  286. 141005 15:13:57  InnoDB: Error: page 285 log sequence number 2455541596
  287. InnoDB: is in the future! Current system log sequence number 2455246113.
  288. InnoDB: Your database may be corrupt or you may have copied the InnoDB
  289. InnoDB: tablespace but not the InnoDB log files. See
  290. InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
  291. InnoDB: for more information.
  292. 141005 15:13:57  InnoDB: Error: page 287 log sequence number 2455553419
  293. InnoDB: is in the future! Current system log sequence number 2455246113.
  294. InnoDB: Your database may be corrupt or you may have copied the InnoDB
  295. InnoDB: tablespace but not the InnoDB log files. See
  296. InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
  297. InnoDB: for more information.
  298. 141005 15:13:57  InnoDB: Error: page 2580 log sequence number 2455553419
  299. InnoDB: is in the future! Current system log sequence number 2455246113.
  300. InnoDB: Your database may be corrupt or you may have copied the InnoDB
  301. InnoDB: tablespace but not the InnoDB log files. See
  302. InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
  303. InnoDB: for more information.
  304. 141005 15:13:57  InnoDB: Error: page 288 log sequence number 2455566275
  305. InnoDB: is in the future! Current system log sequence number 2455246113.
  306. InnoDB: Your database may be corrupt or you may have copied the InnoDB
  307. InnoDB: tablespace but not the InnoDB log files. See
  308. InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
  309. InnoDB: for more information.
  310. 141005 15:13:57  InnoDB: Error: page 289 log sequence number 2455579006
  311. InnoDB: is in the future! Current system log sequence number 2455246113.
  312. InnoDB: Your database may be corrupt or you may have copied the InnoDB
  313. InnoDB: tablespace but not the InnoDB log files. See
  314. InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
  315. InnoDB: for more information.
  316. 141005 15:13:57  InnoDB: Error: page 290 log sequence number 2455592486
  317. InnoDB: is in the future! Current system log sequence number 2455246113.
  318. InnoDB: Your database may be corrupt or you may have copied the InnoDB
  319. InnoDB: tablespace but not the InnoDB log files. See
  320. InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
  321. InnoDB: for more information.
  322. 141005 15:13:57  InnoDB: Error: page 2551 log sequence number 2455592486
  323. InnoDB: is in the future! Current system log sequence number 2455246113.
  324. InnoDB: Your database may be corrupt or you may have copied the InnoDB
  325. InnoDB: tablespace but not the InnoDB log files. See
  326. InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
  327. InnoDB: for more information.
  328. 141005 15:13:57  InnoDB: Error: page 291 log sequence number 2455592713
  329. InnoDB: is in the future! Current system log sequence number 2455246113.
  330. InnoDB: Your database may be corrupt or you may have copied the InnoDB
  331. InnoDB: tablespace but not the InnoDB log files. See
  332. InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
  333. InnoDB: for more information.
  334. 141005 15:13:57  InnoDB: Error: page 2514 log sequence number 2455592713
  335. InnoDB: is in the future! Current system log sequence number 2455246113.
  336. InnoDB: Your database may be corrupt or you may have copied the InnoDB
  337. InnoDB: tablespace but not the InnoDB log files. See
  338. InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
  339. InnoDB: for more information.
  340. 141005 15:13:57  InnoDB: Error: page 292 log sequence number 2455606177
  341. InnoDB: is in the future! Current system log sequence number 2455246113.
  342. InnoDB: Your database may be corrupt or you may have copied the InnoDB
  343. InnoDB: tablespace but not the InnoDB log files. See
  344. InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
  345. InnoDB: for more information.
  346. 141005 15:13:57  InnoDB: Error: page 2552 log sequence number 2455606177
  347. InnoDB: is in the future! Current system log sequence number 2455246113.
  348. InnoDB: Your database may be corrupt or you may have copied the InnoDB
  349. InnoDB: tablespace but not the InnoDB log files. See
  350. InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
  351. InnoDB: for more information.
  352. 141005 15:13:57  InnoDB: Error: page 295 log sequence number 2455619787
  353. InnoDB: is in the future! Current system log sequence number 2455246113.
  354. InnoDB: Your database may be corrupt or you may have copied the InnoDB
  355. InnoDB: tablespace but not the InnoDB log files. See
  356. InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
  357. InnoDB: for more information.
  358. 141005 15:13:57  InnoDB: Error: page 2553 log sequence number 2455619787
  359. InnoDB: is in the future! Current system log sequence number 2455246113.
  360. InnoDB: Your database may be corrupt or you may have copied the InnoDB
  361. InnoDB: tablespace but not the InnoDB log files. See
  362. InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
  363. InnoDB: for more information.
  364. 141005 15:13:57  InnoDB: Error: page 296 log sequence number 2455620892
  365. InnoDB: is in the future! Current system log sequence number 2455246113.
  366. InnoDB: Your database may be corrupt or you may have copied the InnoDB
  367. InnoDB: tablespace but not the InnoDB log files. See
  368. InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
  369. InnoDB: for more information.
  370. 141005 15:13:57  InnoDB: Error: page 2554 log sequence number 2455620892
  371. InnoDB: is in the future! Current system log sequence number 2455246113.
  372. InnoDB: Your database may be corrupt or you may have copied the InnoDB
  373. InnoDB: tablespace but not the InnoDB log files. See
  374. InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
  375. InnoDB: for more information.
  376. InnoDB: 3 transaction(s) which must be rolled back or cleaned up
  377. InnoDB: in total 3 row operations to undo
  378. InnoDB: Trx id counter is F1F00
  379. 141005 15:13:57  InnoDB: Error: page 0 log sequence number 2455620555
  380. InnoDB: is in the future! Current system log sequence number 2455246113.
  381. InnoDB: Your database may be corrupt or you may have copied the InnoDB
  382. InnoDB: tablespace but not the InnoDB log files. See
  383. InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
  384. InnoDB: for more information.
  385. InnoDB: Cleaning up trx with id F1CC9
  386. InnoDB: Cleaning up trx with id F1CBC
  387. InnoDB: Cleaning up trx with id F1CAC
  388. 141005 15:13:57  InnoDB: Waiting for the background threads to start
  389. 141005 15:13:58 InnoDB: 5.5.38 started; log sequence number 2455246113
  390. 141005 15:13:58  InnoDB: Assertion failure in thread 140442187269888 in file fut0lst.ic line 83
  391. InnoDB: Failing assertion: addr.page == FIL_NULL || addr.boffset >= FIL_PAGE_DATA
  392. InnoDB: We intentionally generate a memory trap.
  393. InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
  394. InnoDB: If you get repeated assertion failures or crashes, even
  395. InnoDB: immediately after the mysqld startup, there may be
  396. InnoDB: corruption in the InnoDB tablespace. Please refer to
  397. InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
  398. InnoDB: about forcing recovery.
  399. 12:13:58 UTC - mysqld got signal 6 ;
  400. This could be because you hit a bug. It is also possible that this binary
  401. or one of the libraries it was linked against is corrupt, improperly built,
  402. or misconfigured. This error can also be caused by malfunctioning hardware.
  403. We will try our best to scrape up some info that will hopefully help
  404. diagnose the problem, but since we have already crashed,
  405. something is definitely wrong and this may fail.
Advertisement
Add Comment
Please, Sign In to add comment