Upstream issue with MariaDB

[PPLdude]

Some whacky Wednesday sh*t

Known Issues Status Page - cPanel version 84

Known Issues Status Page This thread includes status updates for known technical issues. Reminder: cPanel & WHM version 84 was introduced to the RELEASE update tier on 2019.10.29. Please reply to this thread if you encounter technical issues after updating your server to this version. You can...

forums.cpanel.net

MariaDB published an update on November 5th, 2019 that can cause MariaDB to fail upon startup on cPanel & WHM servers. We've identified this as an upstream issue with MariaDB (MDEV-19073) affecting the following MariaDB versions:

10.1.42
10.2.28
10.3.19
10.4.9

The following error message is visible in the MariaDB startup output on affected systems:

InnoDB: Failing assertion: table->can_be_evicted

MariaDB is aware of the issue and working to solve it. We'll update this post with more information on the status of MariaDB case MDEV-19073 as it becomes available.

The only known workaround at this time is to perform a downgrade of the MariaDB RPM packages. While there are no supported methods of downgrading MariaDB using cPanel & WHM, you or your system administrator can manually perform this downgrade using the following command:

yum downgrade MariaDB-server MariaDB-common MariaDB-shared MariaDB-client MariaDB-compat MariaDB-devel

 

[Murmaider]

This is an absolute pain and is not only affecting cpanel servers, it's also affect Plesk and DirectAdmin servers (or any server than runs an upgrade on their mariadb). The biggest issue we've seens when mariadb upgrades, it breaks full text indexes and causes row size issues to be printed in the mysql error log.

There are a few ways to fix this, however these Warnings weren't a thing before the upgrade and persist even after the downgrade is done.

 

[PPLdude]

[MDEV-20987] InnoDB fails to start when fts table has FK relation - Jira

jira.mariadb.org

Upstream has provided a fix