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.
Can you post the output of:
tail -20 /var/lib/mysql/mysql-error.log
If that file does not exit, check /var/log for another log file for MySQL, such as:
/var/log/mysql/error.log
… or similar. You can also try running:
systemctl status mysql
… if there’s a systemd script handling the service.
Hi @jtittle!
Thanks for replying so fast.
tail -20 /var/lib/mysql/mysql-error.log did not exist.
However /var/log/mysql/error.log did with the following:
root@percona:/etc/mysql# tail -20 /var/log/mysql/error.log
2017-06-08 07:10:01 8915 [Note] Shutting down plugin 'XTRADB_INTERNAL_HASH_TABLES'
2017-06-08 07:10:01 8915 [Note] Shutting down plugin 'XTRADB_READ_VIEW'
2017-06-08 07:10:01 8915 [Note] Shutting down plugin 'InnoDB'
2017-06-08 07:10:01 8915 [Note] InnoDB: FTS optimize thread exiting.
2017-06-08 07:10:01 8915 [Note] InnoDB: Starting shutdown...
2017-06-08 07:10:03 8915 [Note] InnoDB: Shutdown completed; log sequence number 37752745
2017-06-08 07:10:03 8915 [Note] Shutting down plugin 'ARCHIVE'
2017-06-08 07:10:03 8915 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
2017-06-08 07:10:03 8915 [Note] Shutting down plugin 'BLACKHOLE'
2017-06-08 07:10:03 8915 [Note] Shutting down plugin 'MEMORY'
2017-06-08 07:10:03 8915 [Note] Shutting down plugin 'MRG_MYISAM'
2017-06-08 07:10:03 8915 [Note] Shutting down plugin 'MyISAM'
2017-06-08 07:10:03 8915 [Note] Shutting down plugin 'CSV'
2017-06-08 07:10:03 8915 [Note] Shutting down plugin 'sha256_password'
2017-06-08 07:10:03 8915 [Note] Shutting down plugin 'mysql_old_password'
2017-06-08 07:10:03 8915 [Note] Shutting down plugin 'mysql_native_password'
2017-06-08 07:10:03 8915 [Note] Shutting down plugin 'binlog'
2017-06-08 07:10:03 8915 [Note] /usr/sbin/mysqld: Shutdown complete
systemctl status mysql gives:
root@percona:/etc/mysql# systemctl status mysql
● mysql.service - LSB: Start and stop the mysql (Percona Server) daemon
Loaded: loaded (/etc/init.d/mysql; bad; vendor preset: enabled)
Active: failed (Result: exit-code) since Thu 2017-06-08 07:13:38 UTC; 1min 45s ago
Docs: man:systemd-sysv-generator(8)
Process: 9026 ExecStop=/etc/init.d/mysql stop (code=exited, status=0/SUCCESS)
Process: 9143 ExecStart=/etc/init.d/mysql start (code=exited, status=1/FAILURE)
Jun 08 07:13:38 percona systemd[1]: Starting LSB: Start and stop the mysql (Percona Server) daemon...
Jun 08 07:13:38 percona mysql[9143]: df: /var/lib/mysql//.: No such file or directory
Jun 08 07:13:38 percona mysql[9143]: * /etc/init.d/mysql: ERROR: The partition with /var/lib/mysql/ is too full!
Jun 08 07:13:38 percona systemd[1]: mysql.service: Control process exited, code=exited status=1
Jun 08 07:13:38 percona systemd[1]: Failed to start LSB: Start and stop the mysql (Percona Server) daemon.
Jun 08 07:13:38 percona systemd[1]: mysql.service: Unit entered failed state.
Jun 08 07:13:38 percona systemd[1]: mysql.service: Failed with result 'exit-code'.
When i try to start i get the following:
root@percona:/etc/mysql# service mysql start
Job for mysql.service failed because the control process exited with error code. See "systemctl status mysql.service" and "journalctl -xe" for details.