I recently upgraded from the previous LTS Ubuntu to Precise and now mysql refuses to start. It complains of the following when I attempt to start it:
╰$ sudo service mysql restart
stop: Unknown instance:
start: Job failed to start
And this shows in "/var/log/mysql/error.log":
120415 23:01:09 [Note] Plugin 'InnoDB' is disabled.
120415 23:01:09 [Note] Plugin 'FEDERATED' is disabled.
120415 23:01:09 [ERROR] Unknown/unsupported storage engine: InnoDB
120415 23:01:09 [ERROR] Aborting
120415 23:01:09 [Note] /usr/sbin/mysqld: Shutdown complete
I've checked permissions on all the mysql directories to make sure it had ownership and I also renamed the previou ib_logs so that it could remake them. I'm just getting no where with this issue right now, after looking at google results for 2 hours.
After checking the logs I found the following error:
I removed these files:
at
/var/lib/mysql
This resolved my problem after restart.
If you really need
skip-innodb
(use case: low memory footprint), then of course you don't have to comment it out. However, if InnoDB is the default storage engine, the server will fail to start until you tell it which storage engine to use instead, e.g.default-storage-engine=myisam
for MyISAM.So, try this:
If you're using MySQL 5.6+ and want to disable InnoDB, don't forget "--default-tmp-storage" or it won't work:
http://dev.mysql.com/doc/refman/5.6/en/innodb-parameters.html#option_mysqld_ignore-builtin-innodb
You can add this to your my.cnf:
just to make sure it'll work.
Check your mysql error log.
If your log says (like mine did):
You don't have enough memory to use the default buffer size of 128M
Edit the config file /etc/mysql/my.cnf adding a line to specify a smaller innodb_buffer_pool_size.
Save the config file, and start mysql
Try 2 more things. 1. Lower the innodb buffer pool size. 2. Edit mysql initial script and add --innodb option.
I wonder also if your package is buggy. Could you try a different minor version?
Also, I assume your mysql server got upgraded as well? Maybe that version is broken? Precise is not final yet.
I got this error when I deleted the location I use for
tmpdir
. If you've recently changed yourtmpdir
, you might want to check that it's a valid, writable location.