Today my hosting company decided to patch their systems due to Meltdown/Spectre and restart all servers.
I had my CentOS 7.2 server running for 280 days with no problems of any kind at all.
But now I can't use my website anymore, it says "Error establishing a database connection". When I try to log in to phpMyAdmin with my usual credentials, which I haven't changed at all, it says "Cannot log in to the MySQL server" without accompanied error number #1045, which it tells usually.
/var/log/mariadb/mariadb.log I found the following:
170329 18:41:40 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.5.44-MariaDB' socket: '/var/lib/mysql/mysql.sock' port: 3306 MariaDB Server 180108 14:25:52 [Note] /usr/libexec/mysqld: Normal shutdown 180108 14:25:54 [Note] Event Scheduler: Purging the queue. 0 events 180108 14:26:16 InnoDB: Starting shutdown... 180108 14:26:42 InnoDB: Shutdown completed; log sequence number 233621773 180108 14:26:44 [Note] /usr/libexec/mysqld: Shutdown complete
You see the last activity was on 29.03.2017, in between everything ran smooth, and today InnoDB and MySQL have been shutdown normally. But there are no signs of an attempted start.
When I type in "
systemctl start mariadb" it yields an error which I analyzed via "
systemctl status mariadb":
Process: 3738 ExecStartPost=/usr/libexec/mariadb-wait-ready $MAINPID (code=exited, status=1/FAILURE) Process: 3737 ExecStart=/usr/bin/mysqld_safe --basedir=/usr (code=exited, status=1/FAILURE)
I'm very confused as to what happened and hope you can shed some light on this problem.
mariadb.logfile. Try to start it manually, without using a
servicesystemd call, etc. This page may be of use - mariadb.com/kb/en/library/what-to-do-if-mariadb-doesnt-start
mysql --user=yourusername --password=yourpassword db_name
/etc/init.d/mysql statusor on a redhat machine
service mysqld status, if you have installed mysqladmin
mysqladmin -u root -p status. Regardless with method you use one of them would output a human readable error code.