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.
Did NOT help me tho
root@DB1:~# sudo service mysql stop root@DB1:~# service mysql status ● mysql.service - LSB: Start and stop the mysql database server daemon Loaded: loaded (/etc/init.d/mysql) Active: inactive (dead) since Tue 2018-05-29 19:15:22 UTC; 6s ago Process: 15956 ExecStop=/etc/init.d/mysql stop (code=exited, status=0/SUCCESS) Process: 15420 ExecStart=/etc/init.d/mysql start (code=exited, status=0/SUCCESS)
May 29 19:13:24 DB1 mysql[15420]: Starting MySQL database server: mysqld … May 29 19:13:24 DB1 mysql[15420]: Checking for tables which need an upgrade, are corrupt or were May 29 19:13:24 DB1 mysql[15420]: not closed cleanly… May 29 19:13:24 DB1 systemd[1]: Started LSB: Start and stop the mysql database server daemon. May 29 19:13:24 DB1 /etc/mysql/debian-start[15847]: Upgrading MySQL tables if necessary. May 29 19:13:24 DB1 /etc/mysql/debian-start[15861]: Checking for insecure root accounts. May 29 19:13:24 DB1 /etc/mysql/debian-start[15866]: Triggering myisam-recover for all MyISAM tables May 29 19:15:21 DB1 systemd[1]: Stopping LSB: Start and stop the mysql database server daemon… May 29 19:15:22 DB1 mysql[15956]: Stopping MySQL database server: mysqld. May 29 19:15:22 DB1 systemd[1]: Stopped LSB: Start and stop the mysql database server daemon. root@DB1:~# sudo nano /etc/mysql/my.cnf root@DB1:~# service mysql start Job for mysql.service failed. See ‘systemctl status mysql.service’ and ‘journalctl -xn’ for details. root@DB1:~#