My CentOS 7 server recently crashed by having a hard drive unplugged while it was running and now MariaDB won't start and I'm not getting any error logs.
Everything else on the server seems to be running fine and running
xfs_repair (similar to
fsck for xfs) on the disk didn't help. Here's specifically what errors I'm getting:
$ sudo systemctl start mariadb Job for mariadb.service failed because the control process exited with error code. See "systemctl status mariadb.service" and "journalctl -xe" for details. $ sudo systemctl -l status mariadb ● mariadb.service - MariaDB database server Loaded: loaded (/usr/lib/systemd/system/mariadb.service; disabled; vendor preset: disabled) Active: failed (Result: exit-code) since Sun 2018-07-29 19:34:03 MDT; 1min 22s ago Process: 21579 ExecStartPost=/usr/libexec/mariadb-wait-ready $MAINPID (code=exited, status=1/FAILURE) Process: 21577 ExecStart=/usr/bin/mysqld_safe --basedir=/usr (code=exited, status=0/SUCCESS) Process: 27150 ExecStartPre=/usr/libexec/mariadb-prepare-db-dir %n (code=exited, status=1/FAILURE) Main PID: 21577 (code=exited, status=0/SUCCESS) Jul 29 19:34:03 giivaserver systemd: Starting MariaDB database server... Jul 29 19:34:03 giivaserver mariadb-prepare-db-dir: Database MariaDB is not initialized, but the directory /var/lib/mysql is not empty, so initialization cannot be done. Jul 29 19:34:03 giivaserver mariadb-prepare-db-dir: Make sure the /var/lib/mysql is empty before running mariadb-prepare-db-dir. Jul 29 19:34:03 giivaserver systemd: mariadb.service: control process exited, code=exited status=1 Jul 29 19:34:03 giivaserver systemd: Failed to start MariaDB database server. Jul 29 19:34:03 giivaserver systemd: Unit mariadb.service entered failed state. Jul 29 19:34:03 giivaserver systemd: mariadb.service failed.
As far as I can tell, I'm getting no information back about what is happening or why it can't start. There are also no error log files anywhere that I could find.
[mysqld] datadir=/var/lib/mysql socket=/var/lib/mysql/mysql.sock # Disabling symbolic-links is recommended to prevent assorted security risks symbolic-links=0 # Settings user and group are ignored when systemd is used. # If you need to run mysqld under a different user or group, # customize your systemd unit file for mariadb according to the # instructions in http://fedoraproject.org/wiki/Systemd [mysqld_safe] log-error=/var/log/mariadb/mariadb.log pid-file=/var/run/mariadb/mariadb.pid # # include all files from the config directory # !includedir /etc/my.cnf.d
There are no files at all in my
/var/run/mariadb/ folders. I also don't have a host-name.err (giivaserver.err in my case) in either
/var/log/mysql as described on the official article What to Do if MariaDB Doesn't Start.
I tried putting
innodb_force_recovery = 1 incrementing from 1 to 5 under
[mysqld] in my
my.cnf and it didn't affect anything.
I also tried backing up and renaming my
/var/lib/mysql folder and rerunning
mysql_install_db as some online said deleting it could help, but that made no difference.
I have tried everything I can think of to this point and can't find any feedback from my system as to why MariaDB won't start.
The contents of my /var/lib/mysql folder after renaming the original:
drwx------. 6 mysql mysql 122 Jul 29 19:03 . drwxr-xr-x. 61 root root 4096 Jul 29 19:03 .. -rw-rw----. 1 mysql mysql 16384 Jul 29 19:02 aria_log.00000001 -rw-rw----. 1 mysql mysql 52 Jul 29 19:02 aria_log_control drwx------. 2 mysql mysql 4096 Jul 29 19:02 mysql drwxr-xr-x. 8 mysql mysql 232 Jul 29 18:58 mysqlBAK drwx------. 2 mysql mysql 4096 Jul 29 19:02 performance_schema drwx------. 2 mysql mysql 6 Jul 29 19:02 test