MySQL crashing now and then. Can u help me with log?

Posted August 31, 2014 3k views

Hello, I’m facing some MySQL crashes. I’m on a Ubuntu 12.04.5 LTS X64 (The most basic droplet) and using “SELECT VERSION();” I got MySQL version 5.5.38-0ubuntu0.12.04.1

I have Zpanel installed, because for now I don’t have that many customers to use something as good as Cpanel. I have 3 sites on that server, my newest.

I don’t know what’s causing this crashes and maybe you guys could help out seeing the log. Can you? Please?

Log file:

1 comment
  • My best advice would be to separate all your sites in different droplets and different droplets to host databases as well, instead of jamming everything in the same space.

    At the end of the day, you pay the same and have a more tidy work.

    If you read the first lines in the log it says InnoDB engine is not supported. Perhaps some table is created to use InnoDB.

    To show installed MySQL Engines:

    To show how a particular table is created:
    use my_database;
    SHOW CREATE TABLE my_table;


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.

Submit an Answer
2 answers

Fuc* me! That’s why I do need to learn more about MySQL I don’t figured out nothing you said about it.

I’m planning to put each service (email, DB’s, Apache) into separated droplets as you advice. But actually I’m on Zpanel and this system is almost abandoned in favor of Sentora. So I can’t get support by now to split up these services into different droplets using Zpanel (Now Sentora). I’ll wait for official Sentora release.

I did resize my 512MB to 1GB (10$ bucks plan). But I still experiencing some crashes. I’m doing stress tests with and my droplet crashes about 20 simultaneous visitors. It seems that Apache is taking as much as RAM as MySQL.
For now I’ll add swap into my 1GB droplet and see if it helps at all.

Hello, @jntslvdrt

I will recommend you to examine the MySQL error_log as well, because this is likely to give you a more verbose error and point you in the right direction to see what exactly is causing the issue here.

The location of the error_log should be:

/var/log/mysqld.log or /var/log/mysql/error.log

If you’re unable to locate the errorlog in this two locations you can double check your my.cnf file and see if the errorlog is saved somewhere else.

What you can do is to examine the last logged entries in the log using tail

You can use either:

tail -f /var/log/mysqld.log and tail -f /var/log/mysql/error.log


tail -n 100 /var/log/mysqld.log and tail -n 100 /var/log/mysql/error.log

You can share the output of the log here so we can have a look.

You can also create a simple bash script to check if MySQL is running and if not to restart it.


# Check if MySQL is running
sudo service mysql status > /dev/null 2>&1

# Restart the MySQL service if it's not running.
if [ $? != 0 ]; then
    sudo service mysql restart

Run this script every 5 minutes using a cron job like this one:

 */5 * * * * /home/user/scripts/ > /dev/null 2>&1

Hope that this helps!