API tools faq
paste
MarkDh

Mysql.log

MarkDh
Oct 20th, 2015
99
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 12.87 KB | None | 0 0
raw download clone embed print report
  1. Oct 20 12:27:43 dev3 mysqld: or misconfigured. This error can also be caused by malfunctioning hardware.
  2. Oct 20 12:27:43 dev3 mysqld:
  3. Oct 20 12:27:43 dev3 mysqld: To report this bug, see http://kb.askmonty.org/en/reporting-bugs
  4. Oct 20 12:27:43 dev3 mysqld:
  5. Oct 20 12:27:43 dev3 mysqld: We will try our best to scrape up some info that will hopefully help
  6. Oct 20 12:27:43 dev3 mysqld: diagnose the problem, but since we have already crashed,
  7. Oct 20 12:27:43 dev3 mysqld: something is definitely wrong and this may fail.
  8. Oct 20 12:27:43 dev3 mysqld:
  9. Oct 20 12:27:43 dev3 mysqld: Server version: 10.1.8-MariaDB-1~trusty-log
  10. Oct 20 12:27:43 dev3 mysqld: key_buffer_size=134217728
  11. Oct 20 12:27:43 dev3 mysqld: read_buffer_size=2097152
  12. Oct 20 12:27:43 dev3 mysqld: max_used_connections=0
  13. Oct 20 12:27:43 dev3 mysqld: max_threads=102
  14. Oct 20 12:27:43 dev3 mysqld: thread_count=1
  15. Oct 20 12:27:43 dev3 mysqld: It is possible that mysqld could use up to
  16. Oct 20 12:27:43 dev3 mysqld: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 759822 K bytes of memory
  17. Oct 20 12:27:43 dev3 mysqld: Hope that's ok; if not, decrease some variables in the equation.
  18. Oct 20 12:27:43 dev3 mysqld:
  19. Oct 20 12:27:43 dev3 mysqld: Thread pointer: 0x0x0
  20. Oct 20 12:27:43 dev3 mysqld: Attempting backtrace. You can use the following information to find out
  21. Oct 20 12:27:43 dev3 mysqld: where mysqld died. If you see no messages after this, something went
  22. Oct 20 12:27:43 dev3 mysqld: terribly wrong...
  23. Oct 20 12:27:43 dev3 mysqld: stack_bottom = 0x0 thread_stack 0x48000
  24. Oct 20 12:27:43 dev3 mysqld: /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x7effa10fc29e]
  25. Oct 20 12:27:43 dev3 mysqld: /usr/sbin/mysqld(handle_fatal_signal+0x38d)[0x7effa0c2c8ad]
  26. Oct 20 12:27:43 dev3 mysqld: /lib/x86_64-linux-gnu/libpthread.so.0(+0x10340)[0x7eff9f18d340]
  27. Oct 20 12:27:43 dev3 mysqld: /usr/sbin/mysqld(+0x8dc6d4)[0x7effa0f626d4]
  28. Oct 20 12:27:43 dev3 mysqld: /usr/sbin/mysqld(+0x8ab36d)[0x7effa0f3136d]
  29. Oct 20 12:27:43 dev3 mysqld: /usr/sbin/mysqld(+0x872767)[0x7effa0ef8767]
  30. Oct 20 12:27:43 dev3 mysqld: /usr/sbin/mysqld(+0x8d90ee)[0x7effa0f5f0ee]
  31. Oct 20 12:27:43 dev3 mysqld: /usr/sbin/mysqld(+0x8c703f)[0x7effa0f4d03f]
  32. Oct 20 12:27:43 dev3 mysqld: /lib/x86_64-linux-gnu/libpthread.so.0(+0x8182)[0x7eff9f185182]
  33. Oct 20 12:27:43 dev3 mysqld: /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7eff9e8a847d]
  34. Oct 20 12:27:43 dev3 mysqld: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
  35. Oct 20 12:27:43 dev3 mysqld: information that should help you find out what is causing the crash.
  36. Oct 20 12:27:43 dev3 mysqld_safe: Number of processes running now: 0
  37. Oct 20 12:27:43 dev3 mysqld_safe: mysqld restarted
  38. Oct 20 12:27:44 dev3 mysqld: 2015-10-20 12:27:44 140062180739008 [Note] /usr/sbin/mysqld (mysqld 10.1.8-MariaDB-1~trusty-log) starting as process 25693 ...
  39. Oct 20 12:27:44 dev3 mysqld: 2015-10-20 12:27:44 140062180739008 [Warning] An old style --language or -lc-message-dir value with language specific part detected: /usr/share/mysql/english/
  40. Oct 20 12:27:44 dev3 mysqld: 2015-10-20 12:27:44 140062180739008 [Warning] Use --lc-messages-dir without language specific part instead.
  41. Oct 20 12:27:44 dev3 mysqld: 2015-10-20 12:27:44 140062180739008 [Note] Using unique option prefix 'myisam_recover' is error-prone and can break in the future. Please use the full name 'myisam-recover-options' instead.
  42. Oct 20 12:27:44 dev3 mysqld: 2015-10-20 12:27:44 140062180739008 [Note] InnoDB: Using mutexes to ref count buffer pool pages
  43. Oct 20 12:27:44 dev3 mysqld: 2015-10-20 12:27:44 140062180739008 [Note] InnoDB: The InnoDB memory heap is disabled
  44. Oct 20 12:27:44 dev3 mysqld: 2015-10-20 12:27:44 140062180739008 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
  45. Oct 20 12:27:44 dev3 mysqld: 2015-10-20 12:27:44 140062180739008 [Note] InnoDB: Memory barrier is not used
  46. Oct 20 12:27:44 dev3 mysqld: 2015-10-20 12:27:44 140062180739008 [Note] InnoDB: Compressed tables use zlib 1.2.8
  47. Oct 20 12:27:44 dev3 mysqld: 2015-10-20 12:27:44 140062180739008 [Note] InnoDB: Using Linux native AIO
  48. Oct 20 12:27:44 dev3 mysqld: 2015-10-20 12:27:44 140062180739008 [Note] InnoDB: Using CPU crc32 instructions
  49. Oct 20 12:27:44 dev3 mysqld: 2015-10-20 12:27:44 140062180739008 [Note] InnoDB: Initializing buffer pool, size = 256.0M
  50. Oct 20 12:27:44 dev3 mysqld: 2015-10-20 12:27:44 140062180739008 [Note] InnoDB: Completed initialization of buffer pool
  51. Oct 20 12:27:44 dev3 mysqld: 2015-10-20 12:27:44 140062180739008 [Note] InnoDB: Highest supported file format is Barracuda.
  52. Oct 20 12:27:44 dev3 mysqld: 2015-10-20 12:27:44 140062180739008 [Note] InnoDB: The log sequence numbers 145284412518 and 145284412518 in ibdata files do not match the log sequence number 145284414266 in the ib_logfiles!
  53. Oct 20 12:27:44 dev3 mysqld: 2015-10-20 12:27:44 140062180739008 [Note] InnoDB: Database was not shutdown normally!
  54. Oct 20 12:27:44 dev3 mysqld: 2015-10-20 12:27:44 140062180739008 [Note] InnoDB: Starting crash recovery.
  55. Oct 20 12:27:44 dev3 mysqld: 2015-10-20 12:27:44 140062180739008 [Note] InnoDB: Reading tablespace information from the .ibd files...
  56. Oct 20 12:27:45 dev3 mysqld: 2015-10-20 12:27:45 140062180739008 [Note] InnoDB: Restoring possible half-written data pages
  57. Oct 20 12:27:45 dev3 mysqld: 2015-10-20 12:27:45 140062180739008 [Note] InnoDB: from the doublewrite buffer...
  58. xOct 20 12:27:47 dev3 mysqld: InnoDB: Last MySQL binlog file position 0 6785962, file name ./ec2-db1-bin.000002
  59. Oct 20 12:27:47 dev3 mysqld: 2015-10-20 12:27:47 140062180739008 [Note] InnoDB: 128 rollback segment(s) are active.
  60. Oct 20 12:27:47 dev3 mysqld: 2015-10-20 12:27:47 140062180739008 [Note] InnoDB: Waiting for purge to start
  61. Oct 20 12:27:47 dev3 mysqld: 2015-10-20 12:27:47 140062180739008 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.26-74.0 started; log sequence number 145284414266
  62. xOct 20 12:27:47 dev3 mysqld: 2015-10-20 12:27:47 140061257471744 [Note] InnoDB: Dumping buffer pool(s) not yet started
  63. Oct 20 12:27:47 dev3 mysqld: 2015-10-20 12:27:47 140062180739008 [Note] Plugin 'FEEDBACK' is disabled.
  64. Oct 20 12:27:47 dev3 mysqld: 2015-10-20 12:27:47 140062180739008 [Note] Recovering after a crash using ec2-db1-bin
  65. Oct 20 12:27:47 dev3 mysqld: 2015-10-20 12:27:47 140062180739008 [Note] Starting crash recovery...
  66. Oct 20 12:27:47 dev3 mysqld: 2015-10-20 12:27:47 140062180739008 [Note] Crash recovery finished.
  67. Oct 20 12:27:47 dev3 mysqld: 2015-10-20 12:27:47 7f62c47eb700 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
  68. Oct 20 12:27:47 dev3 mysqld: 2015-10-20 12:27:47 7f62c47eb700 InnoDB: Error: Fetch of persistent statistics requested for table "mysql"."gtid_slave_pos" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
  69. Oct 20 12:27:48 dev3 mysqld: 2015-10-20 12:27:48 140062180739008 [Note] Server socket created on IP: '127.0.0.1'.
  70. Oct 20 12:27:48 dev3 mysqld: 2015-10-20 12:27:48 140062180739008 [Note] Event Scheduler: Loaded 2 events
  71. Oct 20 12:27:48 dev3 mysqld: 2015-10-20 12:27:48 140062179563264 [Note] Event Scheduler: scheduler thread started with id 2
  72. Oct 20 12:27:48 dev3 mysqld: 2015-10-20 12:27:48 140062180739008 [Note] Reading of all Master_info entries succeded
  73. Oct 20 12:27:48 dev3 mysqld: 2015-10-20 12:27:48 140062180739008 [Note] Added new Master_info '' to hash table
  74. Oct 20 12:27:48 dev3 mysqld: 2015-10-20 12:27:48 140062180739008 [Note] /usr/sbin/mysqld: ready for connections.
  75. Oct 20 12:27:48 dev3 mysqld: Version: '10.1.8-MariaDB-1~trusty-log' socket: '/var/run/mysqld/mysqld.sock' port: 3306 mariadb.org binary distribution
  76. Oct 20 12:27:48 dev3 mysqld: 151020 12:27:48 [ERROR] mysqld got signal 11 ;
  77. Oct 20 12:27:48 dev3 mysqld: This could be because you hit a bug. It is also possible that this binary
  78. Oct 20 12:27:48 dev3 mysqld: or one of the libraries it was linked against is corrupt, improperly built,
  79. Oct 20 12:27:48 dev3 mysqld: or misconfigured. This error can also be caused by malfunctioning hardware.
  80. Oct 20 12:27:48 dev3 mysqld:
  81. Oct 20 12:27:48 dev3 mysqld: To report this bug, see http://kb.askmonty.org/en/reporting-bugs
  82. Oct 20 12:27:48 dev3 mysqld:
  83. Oct 20 12:27:48 dev3 mysqld: We will try our best to scrape up some info that will hopefully help
  84. Oct 20 12:27:48 dev3 mysqld: diagnose the problem, but since we have already crashed,
  85. Oct 20 12:27:48 dev3 mysqld: something is definitely wrong and this may fail.
  86. Oct 20 12:27:48 dev3 mysqld:
  87. Oct 20 12:27:48 dev3 mysqld: Server version: 10.1.8-MariaDB-1~trusty-log
  88. Oct 20 12:27:48 dev3 mysqld: key_buffer_size=134217728
  89. Oct 20 12:27:48 dev3 mysqld: read_buffer_size=2097152
  90. Oct 20 12:27:48 dev3 mysqld: max_used_connections=0
  91. Oct 20 12:27:48 dev3 mysqld: max_threads=102
  92. Oct 20 12:27:48 dev3 mysqld: thread_count=1
  93. Oct 20 12:27:48 dev3 mysqld: It is possible that mysqld could use up to
  94. Oct 20 12:27:48 dev3 mysqld: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 759822 K bytes of memory
  95. Oct 20 12:27:48 dev3 mysqld: Hope that's ok; if not, decrease some variables in the equation.
  96. Oct 20 12:27:48 dev3 mysqld:
  97. Oct 20 12:27:48 dev3 mysqld: Thread pointer: 0x0x0
  98. Oct 20 12:27:48 dev3 mysqld: Attempting backtrace. You can use the following information to find out
  99. Oct 20 12:27:48 dev3 mysqld: where mysqld died. If you see no messages after this, something went
  100. Oct 20 12:27:48 dev3 mysqld: terribly wrong...
  101. Oct 20 12:27:48 dev3 mysqld: stack_bottom = 0x0 thread_stack 0x48000
  102. Oct 20 12:27:48 dev3 mysqld: /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x7f62c41d329e]
  103. Oct 20 12:27:48 dev3 mysqld: /usr/sbin/mysqld(handle_fatal_signal+0x38d)[0x7f62c3d038ad]
  104. Oct 20 12:27:48 dev3 mysqld: /lib/x86_64-linux-gnu/libpthread.so.0(+0x10340)[0x7f62c2264340]
  105. Oct 20 12:27:48 dev3 mysqld: /usr/sbin/mysqld(+0x8dc6d4)[0x7f62c40396d4]
  106. Oct 20 12:27:48 dev3 mysqld: /usr/sbin/mysqld(+0x8ab36d)[0x7f62c400836d]
  107. Oct 20 12:27:48 dev3 mysqld: /usr/sbin/mysqld(+0x872767)[0x7f62c3fcf767]
  108. Oct 20 12:27:48 dev3 mysqld: /usr/sbin/mysqld(+0x8d90ee)[0x7f62c40360ee]
  109. Oct 20 12:27:48 dev3 mysqld: /usr/sbin/mysqld(+0x8c703f)[0x7f62c402403f]
  110. Oct 20 12:27:48 dev3 mysqld: /lib/x86_64-linux-gnu/libpthread.so.0(+0x8182)[0x7f62c225c182]
  111. Oct 20 12:27:48 dev3 mysqld: /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f62c197f47d]
  112. Oct 20 12:27:48 dev3 mysqld: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
  113. Oct 20 12:27:48 dev3 mysqld: information that should help you find out what is causing the crash.
  114. Oct 20 12:27:48 dev3 mysqld_safe: Number of processes running now: 0
  115. Oct 20 12:27:48 dev3 mysqld_safe: mysqld restarted
  116. Oct 20 12:27:48 dev3 mysqld: 2015-10-20 12:27:48 140718140659648 [Note] /usr/sbin/mysqld (mysqld 10.1.8-MariaDB-1~trusty-log) starting as process 25788 ...
  117. Oct 20 12:27:48 dev3 mysqld: 2015-10-20 12:27:48 140718140659648 [Warning] An old style --language or -lc-message-dir value with language specific part detected: /usr/share/mysql/english/
  118. Oct 20 12:27:48 dev3 mysqld: 2015-10-20 12:27:48 140718140659648 [Warning] Use --lc-messages-dir without language specific part instead.
  119. Oct 20 12:27:48 dev3 mysqld: 2015-10-20 12:27:48 140718140659648 [Note] Using unique option prefix 'myisam_recover' is error-prone and can break in the future. Please use the full name 'myisam-recover-options' instead.
  120. Oct 20 12:27:48 dev3 mysqld: 2015-10-20 12:27:48 140718140659648 [Note] InnoDB: Using mutexes to ref count buffer pool pages
  121. Oct 20 12:27:48 dev3 mysqld: 2015-10-20 12:27:48 140718140659648 [Note] InnoDB: The InnoDB memory heap is disabled
  122. Oct 20 12:27:48 dev3 mysqld: 2015-10-20 12:27:48 140718140659648 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
  123. Oct 20 12:27:48 dev3 mysqld: 2015-10-20 12:27:48 140718140659648 [Note] InnoDB: Memory barrier is not used
  124. Oct 20 12:27:48 dev3 mysqld: 2015-10-20 12:27:48 140718140659648 [Note] InnoDB: Compressed tables use zlib 1.2.8
  125. Oct 20 12:27:48 dev3 mysqld: 2015-10-20 12:27:48 140718140659648 [Note] InnoDB: Using Linux native AIO
  126. Oct 20 12:27:48 dev3 mysqld: 2015-10-20 12:27:48 140718140659648 [Note] InnoDB: Using CPU crc32 instructions
  127. Oct 20 12:27:48 dev3 mysqld: 2015-10-20 12:27:48 140718140659648 [Note] InnoDB: Initializing buffer pool, size = 256.0M
  128. Oct 20 12:27:48 dev3 mysqld: 2015-10-20 12:27:48 140718140659648 [Note] InnoDB: Completed initialization of buffer pool
  129. Oct 20 12:27:48 dev3 mysqld: 2015-10-20 12:27:48 140718140659648 [Note] InnoDB: Highest supported file format is Barracuda.
  130. Oct 20 12:27:48 dev3 mysqld: 2015-10-20 12:27:48 140718140659648 [Note] InnoDB: The log sequence numbers 145284412518 and 145284412518 in ibdata files do not match the log sequence number 145284414276 in the ib_logfiles!
  131. Oct 20 12:27:48 dev3 mysqld: 2015-10-20 12:27:48 140718140659648 [Note] InnoDB: Database was not shutdown normally!
  132. Oct 20 12:27:48 dev3 mysqld: 2015-10-20 12:27:48 140718140659648 [Note] InnoDB: Starting crash recovery.
Advertisement
Add Comment
Please, Sign In to add comment
Public Pastes
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!