MySQL Crashing -512MB Droplet + Sentora -Support Barracuda file format

Posted May 2, 2017 3.2k views
MySQLUbuntu 16.04

Hi everyone
I have a droplet with 512MB RAM and Ubuntu 16. I am runinng Sentora control panel. After install worpress I notice that MySql start to stop regularity. Then I try to solve this reducing the buffer pool size to 32MB but MySQL steel crashing. In the log I find something about Barracuda file format. I need a solucion. Here is a log error.

170502 7:38:13 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
170502 7:38:13 [Note] Plugin ‘FEDERATED’ is disabled.
170502 7:38:13 InnoDB: The InnoDB memory heap is disabled
170502 7:38:13 InnoDB: Mutexes and rwlocks use GCC atomic builtins
170502 7:38:13 InnoDB: Compressed tables use zlib 1.2.8
170502 7:38:13 InnoDB: Using Linux native AIO
170502 7:38:13 InnoDB: Initializing buffer pool, size = 32.0M
170502 7:38:13 InnoDB: Completed initialization of buffer pool
170502 7:38:13 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib
170502 7:38:13 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files…
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer…
170502 7:38:13 InnoDB: Waiting for the background threads to start
170502 7:38:14 InnoDB: 5.5.54 started; log sequence number 577003798
170502 7:38:14 [Note] Server hostname (bind-address): '’; port: 3306
170502 7:38:14 [Note] - '’ resolves to '’;
170502 7:38:14 [Note] Server socket created on IP: '’.
170502 7:38:14 [Note] Event Scheduler: Loaded 0 events
170502 7:38:14 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.54-0ubuntu0.14.04.1’ socket: ’/var/run/mysqld/mysqld.sock’ port: 3306 (Ubuntu)

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


MySQL is most likely crashing due to insufficient RAM. 512MB isn’t much when you’re running both a control panel and full stack (Apache or NGINX, MySQL or MariaDB, PHP, etc).

When it comes to control panels, I normally recommend at least 1GB of RAM, though 2GB is ideal as you need RAM not only for the services you’re running, but any processes that the control panel runs, as well as for your site.

Hello there,

What you could do is use the MySQLTuner script.

The MySQLTuner is a script written in Perl and allows you to quickly test your MySQL configuration and it gives you suggestions for adjustments to increase performance and stability.

According to the official GitHub page, it supports 300 indicators for MySQL/MariaDB/Percona Server in this last version.

To run the script you could do the following:

  • SSH to your Droplet
  • Download the script:
wget -O
  • Then execute it:

The script would run multiple checks against your MySQL instance, all checks done by MySQLTuner are documented here.

Also as stated in the official documentation, it is still extremely important for you to fully understand each change you make to a MySQL database server. If you don’t understand portions of the script’s output, or if you don’t understand the recommendations, you should consult a knowledgeable DBA or system administrator that you trust.

As a good practice make sure to always test your changes on staging environments before implementing them on your production database.

On the same note, if you want to have a worry-free MySQL hosting and focus on your application, I would recommend trying out the DigitalOcean Managed Databases:

Hope that this helps!