API tools faq
paste
Guest User

Untitled

a guest
Oct 15th, 2015
102
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 44.95 KB | None | 0 0
raw download clone embed print report
  1. 151015 15:32:00 [Note] InnoDB: Using mutexes to ref count buffer pool pages
  2. 151015 15:32:00 [Note] InnoDB: The InnoDB memory heap is disabled
  3. 151015 15:32:00 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
  4. 151015 15:32:00 [Note] InnoDB: Memory barrier is not used
  5. 151015 15:32:00 [Note] InnoDB: Compressed tables use zlib 1.2.8
  6. 151015 15:32:00 [Note] InnoDB: Using Linux native AIO
  7. 151015 15:32:00 [Note] InnoDB: Using CPU crc32 instructions
  8. 151015 15:32:00 [Note] InnoDB: Initializing buffer pool, size = 128.0M
  9. 151015 15:32:00 [Note] InnoDB: Completed initialization of buffer pool
  10. 151015 15:32:00 [Note] InnoDB: Highest supported file format is Barracuda.
  11. 151015 15:32:00 [Note] InnoDB: Log scan progressed past the checkpoint lsn 6406721
  12. 151015 15:32:00 [Note] InnoDB: Database was not shutdown normally!
  13. 151015 15:32:00 [Note] InnoDB: Starting crash recovery.
  14. 151015 15:32:00 [Note] InnoDB: Reading tablespace information from the .ibd files...
  15. 151015 15:32:00 [Note] InnoDB: Restoring possible half-written data pages
  16. 151015 15:32:00 [Note] InnoDB: from the doublewrite buffer...
  17. InnoDB: Doing recovery: scanned up to log sequence number 6406741
  18. 151015 15:32:00 [ERROR] InnoDB: Table zabbix/actions in the InnoDB data dictionary has tablespace id 246, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  19. InnoDB: Please refer to
  20. InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  21. InnoDB: for how to resolve the issue.
  22. 151015 15:32:00 [ERROR] InnoDB: Table zabbix/alerts in the InnoDB data dictionary has tablespace id 293, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  23. InnoDB: Please refer to
  24. InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  25. InnoDB: for how to resolve the issue.
  26. 151015 15:32:00 [ERROR] InnoDB: Table zabbix/applications in the InnoDB data dictionary has tablespace id 233, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  27. InnoDB: Please refer to
  28. InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  29. InnoDB: for how to resolve the issue.
  30. 151015 15:32:00 [ERROR] InnoDB: Table zabbix/conditions in the InnoDB data dictionary has tablespace id 257, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  31. InnoDB: Please refer to
  32. InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  33. InnoDB: for how to resolve the issue.
  34. 151015 15:32:00 [ERROR] InnoDB: Table zabbix/config in the InnoDB data dictionary has tablespace id 258, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  35. InnoDB: Please refer to
  36. InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  37. InnoDB: for how to resolve the issue.
  38. 151015 15:32:00 [ERROR] InnoDB: Table zabbix/dchecks in the InnoDB data dictionary has tablespace id 232, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  39. InnoDB: Please refer to
  40. InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  41. InnoDB: for how to resolve the issue.
  42. 151015 15:32:00 [ERROR] InnoDB: Table zabbix/drules in the InnoDB data dictionary has tablespace id 231, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  43. InnoDB: Please refer to
  44. InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  45. InnoDB: for how to resolve the issue.
  46. 151015 15:32:00 [ERROR] InnoDB: Table zabbix/expressions in the InnoDB data dictionary has tablespace id 289, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  47. InnoDB: Please refer to
  48. InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  49. InnoDB: for how to resolve the issue.
  50. 151015 15:32:00 [ERROR] InnoDB: Table zabbix/functions in the InnoDB data dictionary has tablespace id 261, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  51. InnoDB: Please refer to
  52. InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  53. InnoDB: for how to resolve the issue.
  54. 151015 15:32:00 [ERROR] InnoDB: Table zabbix/globalmacro in the InnoDB data dictionary has tablespace id 265, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  55. InnoDB: Please refer to
  56. InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  57. InnoDB: for how to resolve the issue.
  58. 151015 15:32:00 [ERROR] InnoDB: Table zabbix/graph_theme in the InnoDB data dictionary has tablespace id 264, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  59. InnoDB: Please refer to
  60. InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  61. InnoDB: for how to resolve the issue.
  62. 151015 15:32:00 [ERROR] InnoDB: Table zabbix/graphs in the InnoDB data dictionary has tablespace id 262, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  63. InnoDB: Please refer to
  64. InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  65. InnoDB: for how to resolve the issue.
  66. 151015 15:32:00 [ERROR] InnoDB: Table zabbix/graphs_items in the InnoDB data dictionary has tablespace id 263, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  67. InnoDB: Please refer to
  68. InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  69. InnoDB: for how to resolve the issue.
  70. 151015 15:32:00 [ERROR] InnoDB: Table zabbix/group_discovery in the InnoDB data dictionary has tablespace id 226, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  71. InnoDB: Please refer to
  72. InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  73. InnoDB: for how to resolve the issue.
  74. 151015 15:32:00 [ERROR] InnoDB: Table zabbix/group_prototype in the InnoDB data dictionary has tablespace id 225, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  75. InnoDB: Please refer to
  76. InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  77. InnoDB: for how to resolve the issue.
  78. 151015 15:32:00 [ERROR] InnoDB: Table zabbix/groups in the InnoDB data dictionary has tablespace id 224, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  79. InnoDB: Please refer to
  80. InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  81. InnoDB: for how to resolve the issue.
  82. 151015 15:32:00 [ERROR] InnoDB: Table zabbix/history in the InnoDB data dictionary has tablespace id 294, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  83. InnoDB: Please refer to
  84. InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  85. InnoDB: for how to resolve the issue.
  86. 151015 15:32:00 [ERROR] InnoDB: Table zabbix/hostmacro in the InnoDB data dictionary has tablespace id 266, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  87. InnoDB: Please refer to
  88. InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  89. InnoDB: for how to resolve the issue.
  90. 151015 15:32:00 [ERROR] InnoDB: Table zabbix/hosts in the InnoDB data dictionary has tablespace id 223, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  91. InnoDB: Please refer to
  92. InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  93. InnoDB: for how to resolve the issue.
  94. 151015 15:32:00 [ERROR] InnoDB: Table zabbix/hosts_groups in the InnoDB data dictionary has tablespace id 267, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  95. InnoDB: Please refer to
  96. InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  97. InnoDB: for how to resolve the issue.
  98. 151015 15:32:00 [ERROR] InnoDB: Table zabbix/hosts_templates in the InnoDB data dictionary has tablespace id 268, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  99. InnoDB: Please refer to
  100. InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  101. InnoDB: for how to resolve the issue.
  102. 151015 15:32:00 [ERROR] InnoDB: Table zabbix/httpstep in the InnoDB data dictionary has tablespace id 235, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  103. InnoDB: Please refer to
  104. InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  105. InnoDB: for how to resolve the issue.
  106. 151015 15:32:00 [ERROR] InnoDB: Table zabbix/httpstepitem in the InnoDB data dictionary has tablespace id 239, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  107. InnoDB: Please refer to
  108. InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  109. InnoDB: for how to resolve the issue.
  110. 151015 15:32:00 [ERROR] InnoDB: Table zabbix/httptest in the InnoDB data dictionary has tablespace id 234, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  111. InnoDB: Please refer to
  112. InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  113. InnoDB: for how to resolve the issue.
  114. 151015 15:32:00 [ERROR] InnoDB: Table zabbix/httptestitem in the InnoDB data dictionary has tablespace id 240, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  115. InnoDB: Please refer to
  116. InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  117. InnoDB: for how to resolve the issue.
  118. 151015 15:32:00 [ERROR] InnoDB: Table zabbix/icon_map in the InnoDB data dictionary has tablespace id 276, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  119. InnoDB: Please refer to
  120. InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  121. InnoDB: for how to resolve the issue.
  122. 151015 15:32:00 [ERROR] InnoDB: Table zabbix/icon_mapping in the InnoDB data dictionary has tablespace id 277, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  123. InnoDB: Please refer to
  124. InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  125. InnoDB: for how to resolve the issue.
  126. 151015 15:32:00 [ERROR] InnoDB: Table zabbix/ids in the InnoDB data dictionary has tablespace id 292, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  127. InnoDB: Please refer to
  128. InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  129. InnoDB: for how to resolve the issue.
  130. 151015 15:32:00 [ERROR] InnoDB: Table zabbix/interface in the InnoDB data dictionary has tablespace id 236, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  131. InnoDB: Please refer to
  132. InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  133. InnoDB: for how to resolve the issue.
  134. 151015 15:32:00 [ERROR] InnoDB: Table zabbix/items in the InnoDB data dictionary has tablespace id 238, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  135. InnoDB: Please refer to
  136. InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  137. InnoDB: for how to resolve the issue.
  138. 151015 15:32:00 [ERROR] InnoDB: Table zabbix/items_applications in the InnoDB data dictionary has tablespace id 269, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  139. InnoDB: Please refer to
  140. InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  141. InnoDB: for how to resolve the issue.
  142. 151015 15:32:00 [ERROR] InnoDB: Table zabbix/maintenances in the InnoDB data dictionary has tablespace id 222, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  143. InnoDB: Please refer to
  144. InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  145. InnoDB: for how to resolve the issue.
  146. 151015 15:32:00 [ERROR] InnoDB: Table zabbix/maintenances_groups in the InnoDB data dictionary has tablespace id 285, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  147. InnoDB: Please refer to
  148. InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  149. InnoDB: for how to resolve the issue.
  150. 151015 15:32:00 [ERROR] InnoDB: Table zabbix/maintenances_hosts in the InnoDB data dictionary has tablespace id 284, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  151. InnoDB: Please refer to
  152. InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  153. InnoDB: for how to resolve the issue.
  154. 151015 15:32:00 [ERROR] InnoDB: Table zabbix/maintenances_windows in the InnoDB data dictionary has tablespace id 287, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  155. InnoDB: Please refer to
  156. InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  157. InnoDB: for how to resolve the issue.
  158. 151015 15:32:00 [ERROR] InnoDB: Table zabbix/mappings in the InnoDB data dictionary has tablespace id 270, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  159. InnoDB: Please refer to
  160. InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  161. InnoDB: for how to resolve the issue.
  162. 151015 15:32:00 [ERROR] InnoDB: Table zabbix/media in the InnoDB data dictionary has tablespace id 271, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  163. InnoDB: Please refer to
  164. InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  165. InnoDB: for how to resolve the issue.
  166. 151015 15:32:00 [ERROR] InnoDB: Table zabbix/media_type in the InnoDB data dictionary has tablespace id 241, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  167. InnoDB: Please refer to
  168. InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  169. InnoDB: for how to resolve the issue.
  170. 151015 15:32:00 [ERROR] InnoDB: Table zabbix/node_cksum in the InnoDB data dictionary has tablespace id 291, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  171. InnoDB: Please refer to
  172. InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  173. InnoDB: for how to resolve the issue.
  174. 151015 15:32:00 [ERROR] InnoDB: Table zabbix/nodes in the InnoDB data dictionary has tablespace id 290, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  175. InnoDB: Please refer to
  176. InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  177. InnoDB: for how to resolve the issue.
  178. 151015 15:32:00 [ERROR] InnoDB: Table zabbix/opcommand in the InnoDB data dictionary has tablespace id 251, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  179. InnoDB: Please refer to
  180. InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  181. InnoDB: for how to resolve the issue.
  182. 151015 15:32:00 [ERROR] InnoDB: Table zabbix/opcommand_grp in the InnoDB data dictionary has tablespace id 253, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  183. InnoDB: Please refer to
  184. InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  185. InnoDB: for how to resolve the issue.
  186. 151015 15:32:00 [ERROR] InnoDB: Table zabbix/opcommand_hst in the InnoDB data dictionary has tablespace id 252, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  187. InnoDB: Please refer to
  188. InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  189. InnoDB: for how to resolve the issue.
  190. 151015 15:32:00 [ERROR] InnoDB: Table zabbix/opconditions in the InnoDB data dictionary has tablespace id 256, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  191. InnoDB: Please refer to
  192. InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  193. InnoDB: for how to resolve the issue.
  194. 151015 15:32:00 [ERROR] InnoDB: Table zabbix/operations in the InnoDB data dictionary has tablespace id 247, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  195. InnoDB: Please refer to
  196. InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  197. InnoDB: for how to resolve the issue.
  198. 151015 15:32:00 [ERROR] InnoDB: Table zabbix/opgroup in the InnoDB data dictionary has tablespace id 254, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  199. InnoDB: Please refer to
  200. InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  201. InnoDB: for how to resolve the issue.
  202. 151015 15:32:00 [ERROR] InnoDB: Table zabbix/opmessage in the InnoDB data dictionary has tablespace id 248, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  203. InnoDB: Please refer to
  204. InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  205. InnoDB: for how to resolve the issue.
  206. 151015 15:32:00 [ERROR] InnoDB: Table zabbix/opmessage_grp in the InnoDB data dictionary has tablespace id 249, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  207. InnoDB: Please refer to
  208. InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  209. InnoDB: for how to resolve the issue.
  210. 151015 15:32:00 [ERROR] InnoDB: Table zabbix/opmessage_usr in the InnoDB data dictionary has tablespace id 250, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  211. InnoDB: Please refer to
  212. InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  213. InnoDB: for how to resolve the issue.
  214. 151015 15:32:00 [ERROR] InnoDB: Table zabbix/optemplate in the InnoDB data dictionary has tablespace id 255, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  215. InnoDB: Please refer to
  216. InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  217. InnoDB: for how to resolve the issue.
  218. 151015 15:32:00 [ERROR] InnoDB: Table zabbix/regexps in the InnoDB data dictionary has tablespace id 288, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  219. InnoDB: Please refer to
  220. InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  221. InnoDB: for how to resolve the issue.
  222. 151015 15:32:00 [ERROR] InnoDB: Table zabbix/rights in the InnoDB data dictionary has tablespace id 272, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  223. InnoDB: Please refer to
  224. InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  225. InnoDB: for how to resolve the issue.
  226. 151015 15:32:00 [ERROR] InnoDB: Table zabbix/screens in the InnoDB data dictionary has tablespace id 227, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  227. InnoDB: Please refer to
  228. InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  229. InnoDB: for how to resolve the issue.
  230. 151015 15:32:00 [ERROR] InnoDB: Table zabbix/screens_items in the InnoDB data dictionary has tablespace id 228, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  231. InnoDB: Please refer to
  232. InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  233. InnoDB: for how to resolve the issue.
  234. 151015 15:32:00 [ERROR] InnoDB: Table zabbix/scripts in the InnoDB data dictionary has tablespace id 245, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  235. InnoDB: Please refer to
  236. InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  237. InnoDB: for how to resolve the issue.
  238. 151015 15:32:00 [ERROR] InnoDB: Table zabbix/services in the InnoDB data dictionary has tablespace id 273, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  239. InnoDB: Please refer to
  240. InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  241. InnoDB: for how to resolve the issue.
  242. 151015 15:32:00 [ERROR] InnoDB: Table zabbix/services_links in the InnoDB data dictionary has tablespace id 274, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  243. InnoDB: Please refer to
  244. InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  245. InnoDB: for how to resolve the issue.
  246. 151015 15:32:00 [ERROR] InnoDB: Table zabbix/services_times in the InnoDB data dictionary has tablespace id 275, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  247. InnoDB: Please refer to
  248. InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  249. InnoDB: for how to resolve the issue.
  250. 151015 15:32:00 [ERROR] InnoDB: Table zabbix/slides in the InnoDB data dictionary has tablespace id 230, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  251. InnoDB: Please refer to
  252. InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  253. InnoDB: for how to resolve the issue.
  254. 151015 15:32:00 [ERROR] InnoDB: Table zabbix/slideshows in the InnoDB data dictionary has tablespace id 229, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  255. InnoDB: Please refer to
  256. InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  257. InnoDB: for how to resolve the issue.
  258. 151015 15:32:00 [ERROR] InnoDB: Table zabbix/sysmap_element_url in the InnoDB data dictionary has tablespace id 282, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  259. InnoDB: Please refer to
  260. InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  261. InnoDB: for how to resolve the issue.
  262. 151015 15:32:00 [ERROR] InnoDB: Table zabbix/sysmap_url in the InnoDB data dictionary has tablespace id 283, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  263. InnoDB: Please refer to
  264. InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  265. InnoDB: for how to resolve the issue.
  266. 151015 15:32:00 [ERROR] InnoDB: Table zabbix/sysmaps in the InnoDB data dictionary has tablespace id 278, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  267. InnoDB: Please refer to
  268. InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  269. InnoDB: for how to resolve the issue.
  270. 151015 15:32:00 [ERROR] InnoDB: Table zabbix/sysmaps_elements in the InnoDB data dictionary has tablespace id 279, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  271. InnoDB: Please refer to
  272. InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  273. InnoDB: for how to resolve the issue.
  274. 151015 15:32:00 [ERROR] InnoDB: Table zabbix/sysmaps_link_triggers in the InnoDB data dictionary has tablespace id 281, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  275. InnoDB: Please refer to
  276. InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  277. InnoDB: for how to resolve the issue.
  278. 151015 15:32:00 [ERROR] InnoDB: Table zabbix/sysmaps_links in the InnoDB data dictionary has tablespace id 280, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  279. InnoDB: Please refer to
  280. InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  281. InnoDB: for how to resolve the issue.
  282. 151015 15:32:00 [ERROR] InnoDB: Table zabbix/timeperiods in the InnoDB data dictionary has tablespace id 286, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  283. InnoDB: Please refer to
  284. InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  285. InnoDB: for how to resolve the issue.
  286. 151015 15:32:00 [ERROR] InnoDB: Table zabbix/trigger_depends in the InnoDB data dictionary has tablespace id 260, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  287. InnoDB: Please refer to
  288. InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  289. InnoDB: for how to resolve the issue.
  290. 151015 15:32:00 [ERROR] InnoDB: Table zabbix/triggers in the InnoDB data dictionary has tablespace id 259, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  291. InnoDB: Please refer to
  292. InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  293. InnoDB: for how to resolve the issue.
  294. 151015 15:32:00 [ERROR] InnoDB: Table zabbix/users in the InnoDB data dictionary has tablespace id 242, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  295. InnoDB: Please refer to
  296. InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  297. InnoDB: for how to resolve the issue.
  298. 151015 15:32:00 [ERROR] InnoDB: Table zabbix/users_groups in the InnoDB data dictionary has tablespace id 244, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  299. InnoDB: Please refer to
  300. InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  301. InnoDB: for how to resolve the issue.
  302. 151015 15:32:00 [ERROR] InnoDB: Table zabbix/usrgrp in the InnoDB data dictionary has tablespace id 243, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  303. InnoDB: Please refer to
  304. InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  305. InnoDB: for how to resolve the issue.
  306. 151015 15:32:00 [ERROR] InnoDB: Table zabbix/valuemaps in the InnoDB data dictionary has tablespace id 237, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
  307. InnoDB: Please refer to
  308. InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
  309. InnoDB: for how to resolve the issue.
  310. 151015 15:32:00 [Note] InnoDB: 128 rollback segment(s) are active.
  311. 151015 15:32:00 [Note] InnoDB: Waiting for purge to start
  312. 151015 15:32:00 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.25-73.1 started; log sequence number 6406741
  313. 151015 15:32:00 [Note] CONNECT: Version 1.03.0007 July 05, 2015
  314. Thu Oct 15 15:32:00 2015 TokuFT recovery starting in env /var/lib/mysql/
  315. Thu Oct 15 15:32:00 2015 TokuFT recovery scanning backward from 1487835377
  316. Thu Oct 15 15:32:01 2015 TokuFT recovery bw_end_checkpoint at 1487827053 timestamp 1444875900902776 xid 1487826725 (bw_newer)
  317. Thu Oct 15 15:32:01 2015 TokuFT recovery bw_begin_checkpoint at 1487826725 timestamp 1444875899062403 (bw_between)
  318. Thu Oct 15 15:32:01 2015 TokuFT recovery turning around at begin checkpoint 1487826725 time 1840373
  319. Thu Oct 15 15:32:01 2015 TokuFT recovery starts scanning forward to 1487835377 from 1487826725 left 8652 (fw_between)
  320. /var/tmp/portage/dev-db/mariadb-10.0.21/work/mysql/storage/tokudb/ft-index/ft/serialize/ft-serialize.cc:724 toku_deserialize_ft_from: Assertion `checkpoint_count_1 == checkpoint_count_0 + 1' failed (errno=13)
  321. : Permission denied
  322. Backtrace: (Note: toku_do_assert=0x0x324c9d704a0)
  323. /usr/lib64/mysql/plugin/ha_tokudb.so(_Z19db_env_do_backtraceP8_IO_FILE+0x3d)[0x324c9d7024d]
  324. /usr/lib64/mysql/plugin/ha_tokudb.so(+0x166405)[0x324c9d70405]
  325. /usr/lib64/mysql/plugin/ha_tokudb.so(_Z14toku_do_assertiPKcS0_S0_ii+0x0)[0x324c9d704a0]
  326. /usr/lib64/mysql/plugin/ha_tokudb.so(_Z24toku_deserialize_ft_fromi10__toku_lsnPP2ft+0x3be)[0x324c9d15bae]
  327. /usr/lib64/mysql/plugin/ha_tokudb.so(_Z35toku_read_ft_and_store_in_cachefileP9ft_handleP9cachefile10__toku_lsnPP2ft+0xa6)[0x324c9ca8036]
  328. /usr/lib64/mysql/plugin/ha_tokudb.so(_Z28toku_ft_handle_open_recoveryP9ft_handlePKciiP10cachetableP7tokutxn7FILENUM10__toku_lsn+0x219)[0x324c9cea419]
  329. /usr/lib64/mysql/plugin/ha_tokudb.so(+0x10ebd3)[0x324c9d18bd3]
  330. /usr/lib64/mysql/plugin/ha_tokudb.so(+0x111908)[0x324c9d1b908]
  331. /usr/lib64/mysql/plugin/ha_tokudb.so(_Z14tokuft_recoverP13__toku_db_envPFvS0_P7tokutxnEPFvS0_P10cachetableEP10tokuloggerPKcSC_PFiP9__toku_dbPK10__toku_dbtSH_EPFiSE_SH_SH_SH_PFvSH_PvESK_EPFiSE_SE_P9DBT_ARRAYSQ_SH_SH_EPFiSE_SE_SQ_SH_SH_Em+0x261)[0x324c9d1c621]
  332. /usr/lib64/mysql/plugin/ha_tokudb.so(+0x7f190)[0x324c9c89190]
  333. /usr/lib64/mysql/plugin/ha_tokudb.so(+0x5efa1)[0x324c9c68fa1]
  334. /usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x82)[0x6f8224f132]
  335. /usr/sbin/mysqld(+0x425ab5)[0x6f820e4ab5]
  336. /usr/sbin/mysqld(_Z11plugin_initPiPPci+0xc60)[0x6f820e5ed0]
  337. /usr/sbin/mysqld(+0x37f775)[0x6f8203e775]
  338. /usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x487)[0x6f82042d27]
  339. /lib64/libc.so.6(__libc_start_main+0x11b)[0x324dd22ce9b]
  340. /usr/sbin/mysqld(+0x377843)[0x6f82036843]
  341. Engine status function not available
  342. Memory usage:
  343. Arena 0:
  344. system bytes = 0
  345. in use bytes = 0
  346. Total (incl. mmap):
  347. system bytes = 0
  348. in use bytes = 0
  349. max mmap regions = 0
  350. max mmap bytes = 0
  351. 151015 15:32:01 [ERROR] mysqld got signal 6 ;
  352. This could be because you hit a bug. It is also possible that this binary
  353. or one of the libraries it was linked against is corrupt, improperly built,
  354. or misconfigured. This error can also be caused by malfunctioning hardware.
  355.  
  356. To report this bug, see http://kb.askmonty.org/en/reporting-bugs
  357.  
  358. We will try our best to scrape up some info that will hopefully help
  359. diagnose the problem, but since we have already crashed,
  360. something is definitely wrong and this may fail.
  361.  
  362. Server version: 10.0.21-MariaDB
  363. key_buffer_size=16777216
  364. read_buffer_size=262144
  365. max_used_connections=0
  366. max_threads=52
  367. thread_count=0
  368. It is possible that mysqld could use up to
  369. key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 57327 K bytes of memory
  370. Hope that's ok; if not, decrease some variables in the equation.
  371.  
  372. Thread pointer: 0x0x0
  373. Attempting backtrace. You can use the following information to find out
  374. where mysqld died. If you see no messages after this, something went
  375. terribly wrong...
  376. stack_bottom = 0x0 thread_stack 0x48000
  377. /usr/sbin/mysqld(my_print_stacktrace+0x49)[0x6f827a5da9]
  378. /usr/sbin/mysqld(handle_fatal_signal+0x477)[0x6f8224c317]
  379. /lib64/libpthread.so.0(+0x11080)[0x324de700080]
  380. /lib64/libc.so.6(gsignal+0x4e)[0x324dd241ade]
  381. /lib64/libc.so.6(abort+0x181)[0x324dd2432e1]
  382. /usr/lib64/mysql/plugin/ha_tokudb.so(+0x16640a)[0x324c9d7040a]
  383. /usr/lib64/mysql/plugin/ha_tokudb.so(_Z14toku_do_assertiPKcS0_S0_ii+0x0)[0x324c9d704a0]
  384. /usr/lib64/mysql/plugin/ha_tokudb.so(_Z24toku_deserialize_ft_fromi10__toku_lsnPP2ft+0x3be)[0x324c9d15bae]
  385. /usr/lib64/mysql/plugin/ha_tokudb.so(_Z35toku_read_ft_and_store_in_cachefileP9ft_handleP9cachefile10__toku_lsnPP2ft+0xa6)[0x324c9ca8036]
  386. /usr/lib64/mysql/plugin/ha_tokudb.so(_Z28toku_ft_handle_open_recoveryP9ft_handlePKciiP10cachetableP7tokutxn7FILENUM10__toku_lsn+0x219)[0x324c9cea419]
  387. /usr/lib64/mysql/plugin/ha_tokudb.so(+0x10ebd3)[0x324c9d18bd3]
  388. /usr/lib64/mysql/plugin/ha_tokudb.so(+0x111908)[0x324c9d1b908]
  389. /usr/lib64/mysql/plugin/ha_tokudb.so(_Z14tokuft_recoverP13__toku_db_envPFvS0_P7tokutxnEPFvS0_P10cachetableEP10tokuloggerPKcSC_PFiP9__toku_dbPK10__toku_dbtSH_EPFiSE_SH_SH_SH_PFvSH_PvESK_EPFiSE_SE_P9DBT_ARRAYSQ_SH_SH_EPFiSE_SE_SQ_SH_SH_Em+0x261)[0x324c9d1c621]
  390. /usr/lib64/mysql/plugin/ha_tokudb.so(+0x7f190)[0x324c9c89190]
  391. /usr/lib64/mysql/plugin/ha_tokudb.so(+0x5efa1)[0x324c9c68fa1]
  392. /usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x82)[0x6f8224f132]
  393. /usr/sbin/mysqld(+0x425ab5)[0x6f820e4ab5]
  394. /usr/sbin/mysqld(_Z11plugin_initPiPPci+0xc60)[0x6f820e5ed0]
  395. /usr/sbin/mysqld(+0x37f775)[0x6f8203e775]
  396. /usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x487)[0x6f82042d27]
  397. /lib64/libc.so.6(__libc_start_main+0x11b)[0x324dd22ce9b]
  398. /usr/sbin/mysqld(+0x377843)[0x6f82036843]
  399. The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
  400. information that should help you find out what is causing the crash.
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!