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.
I have similar problem. MariaDB is installed, works fine, but I cannot “stop” or “restart” it.
Although I have requested service stop, MariaDB is still “running” in the background and seems to me - ignores anything further :)
This is my
output:
root@mysql-master:~# systemctl status mysql.service
● mysql.service - LSB: Start and stop the mysql database server daemon
Loaded: loaded (/etc/init.d/mysql; bad; vendor preset: enabled)
Active: failed (Result: exit-code) since Tue 2018-02-27 11:50:59 UTC; 4min 57s ago
Docs: man:systemd-sysv-generator(8)
Process: 22040 ExecStop=/etc/init.d/mysql stop (code=exited, status=1/FAILURE)
Process: 21767 ExecStart=/etc/init.d/mysql start (code=exited, status=0/SUCCESS)
Tasks: 27
Memory: 394.3M
CPU: 3.161s
CGroup: /system.slice/mysql.service
├─21795 /bin/bash /usr/bin/mysqld_safe
├─21936 /usr/sbin/mysqld --basedir=/usr --datadir=/var/lib/mysql --plugin-dir=/usr/lib/mysql/plugin --user=mysql --skip-log-error --pid-file=/var/run/mysqld/mysqld.pid --socket=/var/run/mysqld/mys
└─21937 logger -t mysqld -p daemon error
Feb 27 11:50:59 mysql-master systemd[1]: Stopping LSB: Start and stop the mysql database server daemon...
Feb 27 11:50:59 mysql-master mysql[22040]: * Stopping MariaDB database server mysqld
Feb 27 11:50:59 mysql-master mysql[22040]: ...fail!
Feb 27 11:50:59 mysql-master systemd[1]: mysql.service: Control process exited, code=exited status=1
Feb 27 11:50:59 mysql-master systemd[1]: Stopped LSB: Start and stop the mysql database server daemon.
Feb 27 11:50:59 mysql-master systemd[1]: mysql.service: Unit entered failed state.
Feb 27 11:50:59 mysql-master systemd[1]: mysql.service: Failed with result 'exit-code'.
Feb 27 11:51:59 mysql-master systemd[1]: Stopped LSB: Start and stop the mysql database server daemon.
Feb 27 11:53:43 mysql-master systemd[1]: Stopped LSB: Start and stop the mysql database server daemon.
Feb 27 11:53:45 mysql-master systemd[1]: Stopped LSB: Start and stop the mysql database server daemon.
lines 1-24/24 (END)
@hansen @jtittle Ok guys, I resized my droplet to 1Gb and now everything seems to be ok (and website also seems to go faster).
I also activated an alert if RAM consume is greater than 70% for above 10 minutes.
Do you suggest me some other tool to install or run some optimisation to avoid RAM usage problems?
Is 1Gb droplet suitable for a wordpress site with average traffic of maybe is required the 2Gb solution?
Thanks again for your help guys, I really appreciated it :)
Can you run and post tail -30 /var/log/mysql/error.log?
Just need to get a few more lines of the crash. You need to run it after MySQL stopped.
I suspect you’re running out of RAM, but the log will tell us.