Results 1 to 4 of 4

Thread: MySQL failing to launch on localhost

  1. #1
    Join Date
    Oct 2013

    MySQL failing to launch on localhost

    Hello everyone, I'm new here and I have a major development issue that's really time crucial, so any advice is much appreciated.

    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. There seems to be a major sql problem, I wonder if the issue is poor 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 my theme I chose, 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?

    The log is too many characters to post in this post so here is a link to the file:


  2. #2
    Join Date
    Aug 2004
    Looks like this pretty much gives you the info on what the problem is and possible fixes:
    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.
    "Well done....Consciousness to sarcasm in five seconds!" ~ Terry Pratchett, Night Watch

    How to Ask Questions the Smart Way (not affiliated with this site, but well worth reading)

    My Blog
    cwrBlog: simple, no-database PHP blogging framework

  3. #3
    Join Date
    Sep 2013
    Try this:

    Check the log files for MySQL, in this directory: C:\xampp\mysql\data.

    Also check if no other program or service uses the default MySql port. You can do this by using this command:

    netstat -an | findstr "3306"

    If anything shows up the default mysql port is in use and make sure that there is no other versions of MYSQL installed in your system.

    Hope this helps.
    strad solutionswww.stradsolutions.com

  4. #4
    Join Date
    Oct 2013
    Thank you guys, I'm going to look into those options.

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
HTML5 Development Center