Symptoms
-
MariaDB fails to start with:
# systemctl start mariadb
Job for mariadb.service failed because a fatal signal was delivered causing the control process to dump core. See “systemctl status mariadb.service” and “journalctl -xe” for details.
# 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: core-dump) since Wed 2019-11-06 10:58:12 CST; 4s ago -
MariaDB 10.1-10.3 has been recently updated to version 10.1.42 / 10.2.28 / 10.3.19:
-
on CentOS/RHEL-based distributions
# grep -i Maria /var/log/yum.log
Nov 06 03:46:20 Updated: MariaDB-common-10.1.42-1.el7.centos.x86_64
Nov 06 03:46:22 Updated: MariaDB-client-10.1.42-1.el7.centos.x86_64
Nov 06 03:46:38 Updated: MariaDB-server-10.1.42-1.el7.centos.x86_64
Nov 06 03:46:38 Updated: MariaDB-shared-10.1.42-1.el7.centos.x86_64 -
on Debian/Ubuntu-based distributions
# grep mariadb /var/log/dpkg.log | grep upgrade
2019-11-06 06:25:34 upgrade mariadb-common:all 10.2.27+maria~xenial 10.2.28+maria~xenial
2019-11-06 06:25:34 upgrade mariadb-client-core-10.2:amd64 10.2.27+maria~xenial 10.2.28+maria~xenial
2019-11-06 06:26:05 upgrade mariadb-server-10.2:amd64 10.2.27+maria~xenial 10.2.28+maria~xenial
2019-11-06 06:26:08 upgrade mariadb-client-10.2:amd64 10.2.27+maria~xenial 10.2.28+maria~xenial
2019-11-06 06:26:09 upgrade mariadb-server-core-10.2:amd64 10.2.27+maria~xenial 10.2.28+maria~xenial
-
-
The following entries can be found in
/var/log/mariadb.log
or output of “journalctl -u mariadb”InnoDB: Assertion failure in file /home/buildbot/buildbot/padding_for_CPACK_RPM_BUILD_SOURCE_DIRS_PREFIX/mariadb-10.X.XX/storage/innobase/dict/dict0dict.cc line 1467
InnoDB: Failing assertion: table->can_be_evicted -
Plesk interface is not available with the following error in a web-browser:
PLESK_INFO: SQLSTATE[HY000] [2002] No such file or directory
Cause
The issue is caused by the latest MariaDB update and confirmed as MariaDB bug MDEV-20987. The bug has already been fixed in MariaDB versions 10.1.43, 10.2.29, 10.3.20, 10.4.10, which have been released on November the 8th.
This issue affects the following versions of the MariaDB SQL Server:
- 10.1.42
- 10.2.28
- 10.3.19
- 10.4.9 (Not supported by Plesk)
Resolution
The next packages update is already available, so if the server has been affected, install the lastest MariaDB updates:
-
Log into Plesk
-
Go to Tools & Settings > System Updates
-
Search for “MariaDB”
-
Choose all the packages and click Update
Alternatively, updates can be installed via CLI:
For CentOS/RHEL
-
Connect to the server via SSH
-
Update MariaDB packages:
# yum -y update MariaDB-server MariaDB-common MariaDB-shared MariaDB-client MariaDB-compat MariaDB-devel
In case the issue persists apply either of the solutions from the article How to fix InnoDB corruption cases for the MySQL databases on Plesk for Linux?
For Debian/Ubuntu
-
Connect to the server via SSH.
-
Update MariaDB packages:
# apt-get update MariaDB-server MariaDB-common MariaDB-shared MariaDB-client MariaDB-compat MariaDB-devel
In case the issue persists apply either of the solutions from the article How to fix InnoDB corruption cases for the MySQL databases on Plesk for Linux?