MySQL Error: Stops Frequently - InnoDB Error

February 22, 2016 2.2k views
Apache MySQL Ubuntu

Hi there,

The problem I have that my database stops frequently.

MySQL error log says:

InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.

Droplet details:

  • Ubuntu 14.04
  • Apache
  • Was builded from a snapshot
  • Using WordPress

Any idea how to fix it?

Thanks

3 comments
  • Did the system where you made the snapshot from work OK, or did you do something to that system to make mysql not fail too frequently?

  • First I made a droplet > than I made a snapshot > this droplet was deleted & re-builded from snapshot > I transferred the snapshot to other location (From: SFO1 to LON1) to create more droplets

    I have this issue on all my droplets using this snapshot.

  • @DigitalFish - OK. Hopefully when you shutdown the droplet to make the snapshot, the mysql daemon cleaned up properly. So, the immediate problem is to determine if there is a secondary method that is starting the mysql daemon, or if it is just trying to restart prior to shutting down properly. Try the following

    service mysql stop
    # look at the log files to make sure it did stop or was already stopped
    # confirm it is stopped
    service mysql status
    # restart it
    service mysql start
    # look at the log files to see if the same error appears
    # confirm that is has started
    service mysql status
    
1 Answer

This question was answered by @gndo:

@DigitalFish - OK. Hopefully when you shutdown the droplet to make the snapshot, the mysql daemon cleaned up properly. So, the immediate problem is to determine if there is a secondary method that is starting the mysql daemon, or if it is just trying to restart prior to shutting down properly. Try the following

service mysql stop
# look at the log files to make sure it did stop or was already stopped
# confirm it is stopped
service mysql status
# restart it
service mysql start
# look at the log files to see if the same error appears
# confirm that is has started
service mysql status

View the original comment

Have another answer? Share your knowledge.