Question

Since restoring from a backup mySQL won't start

Hello there,

I have a Ubuntu 12.04.3 LTS (GNU/Linux 3.8.0-29-generic x86_64) droplet which I ballsed up by attempting to upgrade Ubuntu.

So I restored it to a backup from 1 week ago. However, I can’t for the life of me seem to get mySQL to start. After restoring mySQL comes up for a matter of minutes and then dies refusing to start again.

Looking in syslog, it seems to die when this comes up:

Apr 3 23:47:25 localhost kernel: [ 360.410338] type=1400 audit(1428101245.773:24): apparmor=“STATUS” operation=“profile_replace” name=“/usr/sbin/mysqld” pid=2456 comm=“apparmor_parser”

Trying service mysql start come back with this:

start: Job failed to start

Does anyone have any idea what might be happening please?

Show comments

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

Edit your /etc/mysql/mysql.conf.d/mysqld.cnf

Find and change the bind-address = … to the IP of your droplet.

This issue happened to me once I created a new droplet from a backup. In the MySQL config file, the IP was from the old droplet.

To be honest I can’t remember what I did (as it was a few months ago now) but I managed to get dumps of the databases and then just fired up a new server to use only for my databases with a secure connection running between the web server and new database server. A better way to do it plus I set up regular database backups to avoid the issue happening again.