Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Today Mysql Innodb Data files maxed out. I was attempted to clear out files in order to reduce the size. This my be completely unrelated to the issue, but I thought it would be worth mentioning.

I restarted the computer and now Mysql is refusing all outside connections. Their are no errors in the error log. However, if I disable Innodb it works, but the Innodb is disabled. I need the Innodb working, and the server accepting connections.

"Can't connect to MySQL server on '' (111) [2003]" 111 meaning that its refusing the connections.

share|improve this question

If it's refusing the connections, then (short of firewall shenanigans not in evidence) then MySQL isn't running. More specifically, given the whole InnoDB/non-InnoDB startup difference, trying to use InnoDB is causing a failure to start. Your MySQL logs will tell you exactly why, but if you've been fiddling with InnoDB data files, I'd say there's a chance you might be restoring from backups in the near future.

share|improve this answer
There are no errors in the log though. When I change it and break it there are, but when I start it up normally there is no error. I actually need help, please do not down vote it. – Iscariot Aug 14 '11 at 4:08

Just guessing, but playing with your innodb file manually is causing MySQL to fail to startup (which is why it does when you disable innodb in the config).

My MySQL skills are not great, but my guess is you've hosed your database, and are going to need to restore from a backup. You might be able to force an innodb recovery ( )

In the future I'd read the docs before you touch anything with MySQL, especially it's data files, manually. Here's a nice little section that will be helpful in the future Adding, Removing, or Resizing InnoDB Data and Log Files

share|improve this answer

I would try:

  1. Check the file system messages by running "dmesg | tail" , checking for a corrupted file system journal.

  2. If journal is bad, run the command "tune2fs -j [device name]"

share|improve this answer
up vote 0 down vote accepted

If you have this issue leave it alone and give it time. It takes quite a while for it to load the database and you will be able to use something to remove some of the database information in order to return it to a working status.

You may also be able to dump the database and work on it that way.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.