Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

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!
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.
Hello all,
When facing with an MySQL issue on your Droplet. Here’s a quick guide to help you troubleshoot the problem:
Check MySQL logs for errors:
Inspect the MySQL error logs for any issues or failures that may have occurred. Usually you can find the log at /var/log/mysql/error.log. If there are any specific error messages, you can further act upon them
Check system logs for process termination:
Sometimes, the MySQL process may be killed by the system due to resource constraints. To check if this happened, inspect the system logs:
- grep -E 'oom|kill' /var/log/syslog
- grep -E 'oom|kill' /var/log/kern.log
If you find such messages, it’s an indication that your Droplet is running out of resources, and you may need to upgrade your Droplet or optimize your MySQL configuration.
Configure swap space:
If your Droplet is running out of memory, configuring swap space can help alleviate the issue. Swap space acts as a temporary storage location for data when your system runs out of RAM.
You can find more about how to add SWAP to your Droplet here:
https://www.digitalocean.com/community/tutorial_collections/how-to-add-swap-space
Hope that helps!