Guest User


a guest
Sep 8th, 2015
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
  1. InnoDB: End of page dump
  2. 150908 23:04:33 InnoDB: Page checksum 4068774198, prior-to-4.0.14-form checksum 2865448789
  3. InnoDB: stored checksum 4068774198, prior-to-4.0.14-form stored checksum 3309707613
  4. InnoDB: Page lsn 0 1823820451, low 4 bytes of lsn at page end 1823271692
  5. InnoDB: Page number (if stored to page already) 5,
  6. InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
  7. InnoDB: Page may be a transaction system page
  8. InnoDB: Database page corruption on disk or a failed
  9. InnoDB: file read of page 5.
  10. InnoDB: You may have to recover from a backup.
  11. InnoDB: It is also possible that your operating
  12. InnoDB: system has corrupted its own file cache
  13. InnoDB: and rebooting your computer removes the
  14. InnoDB: error.
  15. InnoDB: If the corrupt page is an index page
  16. InnoDB: you can also try to fix the corruption
  17. InnoDB: by dumping, dropping, and reimporting
  18. InnoDB: the corrupt table. You can use CHECK
  19. InnoDB: TABLE to scan your table for corruption.
  20. InnoDB: See also
  21. InnoDB: about forcing recovery.
  22. InnoDB: Ending processing because of a corrupt database page.
  23. 150908 23:04:33 InnoDB: Assertion failure in thread 140327967921984 in file buf0buf.c line 3620
  24. InnoDB: We intentionally generate a memory trap.
  25. InnoDB: Submit a detailed bug report to
  26. InnoDB: If you get repeated assertion failures or crashes, even
  27. InnoDB: immediately after the mysqld startup, there may be
  28. InnoDB: corruption in the InnoDB tablespace. Please refer to
  29. InnoDB:
  30. InnoDB: about forcing recovery.
  31. 23:04:33 UTC - mysqld got signal 6 ;
  32. This could be because you hit a bug. It is also possible that this binary
  33. or one of the libraries it was linked against is corrupt, improperly built,
  34. or misconfigured. This error can also be caused by malfunctioning hardware.
  35. We will try our best to scrape up some info that will hopefully help
  36. diagnose the problem, but since we have already crashed,
  37. something is definitely wrong and this may fail.
  39. key_buffer_size=134217728
  40. read_buffer_size=131072
  41. max_used_connections=0
  42. max_threads=151
  43. thread_count=0
  44. connection_count=0
  45. It is possible that mysqld could use up to
  46. key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 461388 K bytes of memory
  47. Hope that's ok; if not, decrease some variables in the equation.
  49. Thread pointer: 0x0
  50. Attempting backtrace. You can use the following information to find out
  51. where mysqld died. If you see no messages after this, something went
  52. terribly wrong...
  53. stack_bottom = 0 thread_stack 0x30000
  54. /usr/sbin/mysqld(my_print_stacktrace+0x29)[0x7fa0a704dd79]
  55. /usr/sbin/mysqld(handle_fatal_signal+0x483)[0x7fa0a6f12923]
  56. /lib/x86_64-linux-gnu/[0x7fa0a5c5acb0]
  57. /lib/x86_64-linux-gnu/[0x7fa0a52c60d5]
  58. /lib/x86_64-linux-gnu/[0x7fa0a52c983b]
  59. /usr/sbin/mysqld(+0x64bbc1)[0x7fa0a713dbc1]
  60. /usr/sbin/mysqld(+0x657438)[0x7fa0a7149438]
  61. /usr/sbin/mysqld(+0x657ddc)[0x7fa0a7149ddc]
  62. /usr/sbin/mysqld(+0x6477f0)[0x7fa0a71397f0]
  63. /usr/sbin/mysqld(+0x619afc)[0x7fa0a710bafc]
  64. /usr/sbin/mysqld(+0x61bd1c)[0x7fa0a710dd1c]
  65. /usr/sbin/mysqld(+0x607aea)[0x7fa0a70f9aea]
  66. /usr/sbin/mysqld(+0x5d1399)[0x7fa0a70c3399]
  67. /usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x41)[0x7fa0a6f14ff1]
  68. /usr/sbin/mysqld(+0x30ecb1)[0x7fa0a6e00cb1]
  69. /usr/sbin/mysqld(_Z11plugin_initPiPPci+0xad4)[0x7fa0a6e043d4]
  70. /usr/sbin/mysqld(+0x2852b6)[0x7fa0a6d772b6]
  71. /usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x624)[0x7fa0a6d7ad24]
  72. /lib/x86_64-linux-gnu/[0x7fa0a52b176d]
  73. /usr/sbin/mysqld(+0x27eb29)[0x7fa0a6d70b29]
  74. The manual page at contains
  75. information that should help you find out what is causing the crash.
RAW Paste Data

Adblocker detected! Please consider disabling it...

We've detected AdBlock Plus or some other adblocking software preventing from fully loading.

We don't have any obnoxious sound, or popup ads, we actively block these annoying types of ads!

Please add to your ad blocker whitelist or disable your adblocking software.