Skip to main content

Innodb Error

Comments

4 comments

  • YasIT
    I does not use skip-innodb and add line innodb_force_recovery = 4 successfully restart and all site was runing... but in error log .err : 2014-06-12 19:00:15 5920 [ERROR] InnoDB: Failed to find tablespace for table '"darya_chating"."db1_etchat_config"' in the cache. Attempting to load the tablespace with space id 238062. 2014-06-12 19:00:16 5920 [ERROR] /usr/sbin/mysqld: Table './bbpicir_bbpic/nuke_session' is marked as crashed and should be repaired 2014-06-12 19:00:16 5920 [ERROR] /usr/sbin/mysqld: Table './bbpicir_bbpic/nuke_session' is marked as crashed and should be repaired 2014-06-12 19:00:16 5920 [ERROR] /usr/sbin/mysqld: Table './bbpicir_bbpic/nuke_session' is marked as crashed and should be repaired 2014-06-12 19:00:16 5920 [ERROR] InnoDB: Failed to find tablespace for table '"darya_chating"."db1_etchat_user"' in the cache. Attempting to load the tablespace with space id 240993. 2014-06-12 19:00:16 5920 [ERROR] InnoDB: Failed to find tablespace for table '"darya_chating"."cod"' in the cache. Attempting to load the tablespace with space id 234879. 2014-06-12 19:00:16 5920 [ERROR] /usr/sbin/mysqld: Table './takmelo_6868/nuke_antiflood' is marked as crashed and should be repaired 2014-06-12 19:00:16 5920 [ERROR] /usr/sbin/mysqld: Table './takmelo_6868/nuke_antiflood' is marked as crashed and should be repaired 2014-06-12 19:00:16 5920 [ERROR] /usr/sbin/mysqld: Table './takmelo_6868/nuke_antiflood' is marked as crashed and should be repaired 2014-06-12 19:00:17 5920 [ERROR] /usr/sbin/mysqld: Table './para_chat/zse8p_TABLE_STATISTICS_RAW' is marked as crashed and should be repaired 2014-06-12 19:00:17 5920 [ERROR] /usr/sbin/mysqld: Table './para_chat/zse8p_TABLE_STATISTICS_RAW' is marked as crashed and should be repaired 2014-06-12 19:00:18 5920 [ERROR] /usr/sbin/mysqld: Table './tikmusic_nuke836/nuke_stories' is marked as crashed and should be repaired 2014-06-12 19:00:19 5920 [ERROR] /usr/sbin/mysqld: Table './tazohoor_FaDB/jos_session' is marked as crashed and should be repaired 2014-06-12 19:00:19 5920 [ERROR] /usr/sbin/mysqld: Table './tazohoor_FaDB/jos_session' is marked as crashed and should be repaired 2014-06-12 19:00:19 5920 [ERROR] /usr/sbin/mysqld: Table './tazohoor_FaDB/jos_session' is marked as crashed and should be repaired 2014-06-12 19:00:19 5920 [ERROR] /usr/sbin/mysqld: Table './tazohoor_FaDB/jos_session' is marked as crashed and should be repaired 2014-06-12 19:00:19 5920 [ERROR] /usr/sbin/mysqld: Table './tazohoor_FaDB/jos_session' is marked as crashed and should be repaired 2014-06-12 19:00:21 5920 [ERROR] /usr/sbin/mysqld: Table './takmelo_6868/nuke_antiflood' is marked as crashed and should be repaired 2014-06-12 19:00:21 5920 [ERROR] /usr/sbin/mysqld: Table './takmelo_6868/nuke_antiflood' is marked as crashed and should be repaired 2014-06-12 19:00:21 5920 [ERROR] /usr/sbin/mysqld: Table './takmelo_6868/nuke_antiflood' is marked as crashed and should be repaired 2014-06-12 19:00:22 5920 [ERROR] /usr/sbin/mysqld: Table './tikmusic_nuke836/nuke_stories' is marked as crashed and should be repaired 2014-06-12 19:00:23 5920 [ERROR] /usr/sbin/mysqld: Table './design_vb/vsavilxh_guests' is marked as crashed and should be repaired 2014-06-12 19:00:23 5920 [ERROR] /usr/sbin/mysqld: Table './design_vb/vsavilxh_guests' is marked as crashed and should be repaired 2014-06-12 19:00:23 5920 [ERROR] /usr/sbin/mysqld: Table './design_vb/vsavilxh_guests' is marked as crashed and should be repaired 2014-06-12 19:00:23 5920 [ERROR] /usr/sbin/mysqld: Table './partoodo_partoo/wp_TABLE_STATISTICS' is marked as crashed and should be repaired 2014-06-12 19:00:23 5920 [ERROR] /usr/sbin/mysqld: Table './partoodo_partoo/wp_TABLE_STATISTICS' is marked as crashed and should be repaired 2014-06-12 19:00:23 5920 [ERROR] /usr/sbin/mysqld: Table './partoodo_partoo/wp_TABLE_STATISTICS' is marked as crashed and should be repaired 2014-06-12 19:00:23 5920 [ERROR] /usr/sbin/mysqld: Table './partoodo_partoo/wp_TABLE_STATISTICS' is marked as crashed and should be repaired 2014-06-12 19:00:23 5920 [ERROR] /usr/sbin/mysqld: Table './partoodo_partoo/wp_TABLE_STATISTICS' is marked as crashed and should be repaired 2014-06-12 19:00:23 5920 [ERROR] /usr/sbin/mysqld: Table './partoodo_partoo/wp_TABLE_STATISTICS' is marked as crashed and should be repaired 2014-06-12 19:00:23 5920 [ERROR] /usr/sbin/mysqld: Table './partoodo_partoo/wp_TABLE_STATISTICS' is marked as crashed and should be repaired 2014-06-12 19:00:23 5920 [ERROR] /usr/sbin/mysqld: Table './partoodo_partoo/wp_TABLE_STATISTICS' is marked as crashed and should be repaired 2014-06-12 19:00:23 5920 [ERROR] /usr/sbin/mysqld: Table './partoodo_partoo/wp_TABLE_STATISTICS' is marked as crashed and should be repaired 2014-06-12 19:00:23 5920 [ERROR] /usr/sbin/mysqld: Table './partoodo_partoo/wp_TABLE_STATISTICS' is marked as crashed and should be repaired 2014-06-12 19:00:23 5920 [ERROR] /usr/sbin/mysqld: Table './partoodo_partoo/wp_TABLE_STATISTICS' is marked as crashed and should be repaired 2014-06-12 19:00:23 5920 [ERROR] /usr/sbin/mysqld: Table './partoodo_partoo/wp_TABLE_STATISTICS' is marked as crashed and should be repaired 2014-06-12 19:00:23 5920 [ERROR] /usr/sbin/mysqld: Table './partoodo_partoo/wp_TABLE_STATISTICS' is marked as crashed and should be repaired 2014-06-12 19:00:23 5920 [ERROR] /usr/sbin/mysqld: Table './partoodo_partoo/wp_TABLE_STATISTICS' is marked as crashed and should be repaired 2014-06-12 19:00:23 5920 [ERROR] /usr/sbin/mysqld: Table './partoodo_partoo/wp_TABLE_STATISTICS' is marked as crashed and should be repaired 2014-06-12 19:00:23 5920 [ERROR] /usr/sbin/mysqld: Table './partoodo_partoo/wp_TABLE_STATISTICS' is marked as crashed and should be repaired 2014-06-12 19:00:23 5920 [ERROR] /usr/sbin/mysqld: Table './partoodo_partoo/wp_TABLE_STATISTICS' is marked as crashed and should be repaired 2014-06-12 19:00:23 5920 [ERROR] /usr/sbin/mysqld: Table './partoodo_partoo/wp_TABLE_STATISTICS' is marked as crashed and should be repaired 2014-06-12 19:00:23 5920 [ERROR] /usr/sbin/mysqld: Table './partoodo_partoo/wp_TABLE_STATISTICS' is marked as crashed and should be repaired 2014-06-12 19:00:23 5920 [ERROR] /usr/sbin/mysqld: Table './partoodo_partoo/wp_TABLE_STATISTICS' is marked as crashed and should be repaired 2014-06-12 19:00:23 5920 [ERROR] /usr/sbin/mysqld: Table './partoodo_partoo/wp_TABLE_STATISTICS' is marked as crashed and should be repaired 2014-06-12 19:00:23 5920 [ERROR] /usr/sbin/mysqld: Table './partoodo_partoo/wp_TABLE_STATISTICS' is marked as crashed and should be repaired 2014-06-12 19:00:23 5920 [ERROR] /usr/sbin/mysqld: Table './partoodo_partoo/wp_TABLE_STATISTICS' is marked as crashed and should be repaired 2014-06-12 19:00:23 5920 [ERROR] /usr/sbin/mysqld: Table './partoodo_partoo/wp_TABLE_STATISTICS' is marked as crashed and should be repaired 2014-06-12 19:00:23 5920 [ERROR] /usr/sbin/mysqld: Table './design_vb/vsavilxh_guests' is marked as crashed and should be repaired 2014-06-12 19:00:24 5920 [ERROR] InnoDB: Failed to find tablespace for table '"ecommerc_magento"."eav_entity_type"' in the cache. Attempting to load the tablespace with space id 67255. 2014-06-12 19:00:24 5920 [ERROR] InnoDB: Failed to find tablespace for table '"ecommerc_magento"."catalog_category_entity"' in the cache. Attempting to load the tablespace with space id 67098. 2014-06-12 19:00:24 5920 [ERROR] InnoDB: Failed to find tablespace for table '"ecommerc_magento"."eav_attribute"' in the cache. Attempting to load the tablespace with space id 67242. 2014-06-12 19:00:24 5920 [ERROR] InnoDB: Failed to find tablespace for table '"ecommerc_magento"."catalog_eav_attribute"' in the cache. Attempting to load the tablespace with space id 67110. 2014-06-12 19:00:24 5920 [ERROR] InnoDB: Failed to find tablespace for table '"ecommerc_magento"."eav_entity_attribute"' in the cache. Attempting to load the tablespace with space id 67249. 2014-06-12 19:00:24 5920 [ERROR] InnoDB: Failed to find tablespace for table '"ecommerc_magento"."eav_attribute_label"' in the cache. Attempting to load the tablespace with space id 67244. 2014-06-12 19:00:24 5920 [ERROR] InnoDB: Failed to find tablespace for table '"ecommerc_magento"."catalog_category_entity_varchar"' in the cache. Attempting to load the tablespace with space id 67103. 2014-06-12 19:00:24 5920 [ERROR] InnoDB: Failed to find tablespace for table '"ecommerc_magento"."catalog_category_entity_int"' in the cache. Attempting to load the tablespace with space id 67101. 2014-06-12 19:00:24 5920 [ERROR] InnoDB: Failed to find tablespace for table '"ecommerc_magento"."catalog_category_entity_text"' in the cache. Attempting to load the tablespace with space id 67102. 2014-06-12 19:00:24 5920 [ERROR] InnoDB: Failed to find tablespace for table '"ecommerc_magento"."catalog_category_entity_datetime"' in the cache. Attempting to load the tablespace with space id 67099. 2014-06-12 19:00:24 5920 [ERROR] InnoDB: Failed to find tablespace for table '"ecommerc_magento"."catalog_category_entity_decimal"' in the cache. Attempting to load the tablespace with space id 67100.
    How to fix this problem well?
    0
  • cPanelMichael
    Hello :) The following document is a good place to start (adjust the URL based on the version of MySQL installed on your system): [url=http://dev.mysql.com/doc/refman/5.5/en/rebuilding-tables.html]MySQL :: MySQL 5.5 Reference Manual :: 2.11.4 Rebuilding or Repairing Tables or Indexes Thank you.
    0
  • YasIT
    I've many databases in my server and many innodb! How to fix this problem step by step? Please help.
    0
  • cPanelMichael
    The logs you provided indicate crashed tables for some databases. You can typically repair those tables using the "mysqlcheck --repair" command referenced in the document from my last response. InnoDB corruption involves more in-depth solutions. There are not necessarily step by step instructions because it depends on the nature of the corruption. That being said, the document I referenced does go into detail and provide links to additional documentation for repairing InnoDB. Keep in mind that database corruption falls outside our scope of support, so you may want to consult with a qualified system administrator or database specialist for assistance. Thank you.
    0

Please sign in to leave a comment.