Droplet keeps running out of memory, no longer loading

My droplet keeps running out of memory instantly after restarting mysql. I can no longer access my WordPress site at all, I was previously seeing the Error establishing connection to database screen.

I followed this post:

I saw the following in the access logs: grep xmlrpc /var/log/apache2/access.log - - [15/Mar/2022:07:30:23 +0000] “GET /xmlrpcs.php?daksldlkdsadas=1 HTTP/1.1” 404 24956 “” “wp_is_mobile” - - [15/Mar/2022:14:26:04 +0000] “POST /xmlrpc.php HTTP/1.1” 301 5773 “” “The Incutio XML-RPC PHP Library – WordPress/5.4.10”

I updated the config to block xmlrpc traffic but that hasn’t solved anything. If anyone has any suggestions that would be appreciated because I’ve hit a wall!

Submit an answer
Answer a question...

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.

Site Moderator
Site Moderator badge
July 9, 2022

Hello there,

This crash is most likely due to your system running out of memory. I’d suggest that you add a swap file to give yourself a bit more of a buffer. Check out this tutorial:

How To Add Swap on Ubuntu 18.04

What you can also do is to 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 worry-free MySQL hosting and focus on your application, I would recommend trying out the DigitalOcean Managed Databases:


Hope that this helps!