MySQL Fails After Update

MySQL/MariaDB may fail to start after an update to versions 10.1.42, 10.2.28, or 10.3.18. An update will be required to resolve this issue, as these versions are out of date.

This article will cover how to confirm if a problem version is in use and the update process on VPS+.

An example of the error message is as follows.

# service mysql restart
Restarting mysql (via systemctl): Job for mariadb.service failed because a fatal signal was delivered to the control process. See "systemctl status mariadb.service" and "journalctl -xe" for details.
[FAILED]


# systemctl status mariadb.service
● mariadb.service - MariaDB 10.2.28 database server
Loaded: loaded (/usr/lib/systemd/system/mariadb.service; enabled; vendor preset: disabled)
Drop-In: /etc/systemd/system/mariadb.service.d
└─migrated-from-my.cnf-settings.conf
Active: activating (auto-restart) (Result: signal) since Wed 2019-11-06 02:29:42 PST; 4s ago
Docs: man:mysqld(8)
https://mariadb.com/kb/en/library/systemd/
Process: 22226 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS --basedir=/usr $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=killed, signal=ABRT)
Process: 22156 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= || VAR=`/usr/bin/galera_recovery`; [ $? -eq 0 ] && systemctl set-environment _WSREP_START_POSITION=$VAR || exit 1 (code=exited, status=0/SUCCESS)
Process: 22155 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
Main PID: 22226 (code=killed, signal=ABRT)

Resolve MySQL Failure on Problem Versions

1. SSH into the server as root
2. Force yum to re-check the MariaDB repository by invalidating repository caches

   yum clean expire-cache

3. Run a system update to resolve the issue and force MariaDB to update
   

   yum update

4. Confirm MariaDB-server is no longer on a problematic version with

   yum info MariaDB-server