-
AuthorPosts
-
October 21st, 2013 at 16:37 #13128Sam Assoum
I am not a very educated developer, I really only know html and css, and have made a few sites using wordpress. I have started on a new project for work, and as I always have, I started the design on my localhost using xampp and wordpress (it’s not example.com). There seems to be a major sql problem, I wonder if the issue is coding in the theme, but keep in mind after this happened the first time (and I lost all my sql info) I deleted and uninstalled everything and restarted, only to find the issue happening again.
The issue:
I installed xampp and wordpress, using localhost as my working domain, did about 10 hours of web design customizing the theme, shutdown the pc, went to sleep. The next day when I start up xampp, apache starts, filezilla starts, and mysql fails. I have the error log but i can’t make any sense of any of it due to my lack of knowledge. Obviously with the sql down I can’t access my site hosted on my localhost. What is the issue? Any ideas?
I was told the key to the issue is this section of the sql error log:
InnoDB: Error: could not open single-table tablespace file .\wordpress\wp_terms.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.October 24th, 2013 at 20:26 #13183ZedCryout Creations mastermindThe theme does not communicate with the MySQL database so it cannot cause corruption.
Sorry, but you’ll have to look some place else for the cause of this – hard disk corruption, memory errors, MySQL version bug, PHP errors, incorrect MySQL shutdown…
Why don’t you try working on a subfolder/subdomain of a hosted website (via FTP)?
If you like our creations, help us share by rating them on WordPress.org.
Please check the available documentation and search the forums before starting a topic. -
AuthorPosts
The topic ‘MySQL failing?’ is closed to new replies.