This is a warning about a critical bug in MariaDB 5.5.43 and 10.0.18 that may affect some users during a major version upgrade. Shortly after the releases of both MariaDB 5.5.43 and 10.0.18, a significant problem was discovered. The problem occurs when upgrading between major versions, such as from MariaDB 5.5 to MariaDB 10.0, or when migrating from another product, such as from MySQL 5.6 to MariaDB 10.0. When mysql_upgrade is executed as part of such a migration/upgrade it invokes the REPAIR VIEW statement, which can cause the server to crash. The issue is triggered by view definitions that cause an on-disk (instead of in-memory) temporary table to be used. This occurs most commonly when a view selects from an underlying table with one or more TEXT or BLOB or BINARY or VARBINARY columns. The error was introduced as part of the fix for MDEV-6916 and the fix is tracked in MDEV-8115. - https://mariadb.atlassian.net/browse/MDEV-6916 - https://mariadb.atlassian.net/browse/MDEV-8115 Because of this issue, you should *NOT* perform a major version upgrade, or migration from another product, to MariaDB 5.5.43 or MariaDB 10.0.18 but instead wait for MariaDB 5.5.44 and 10.0.19 (now released). Minor upgrades, such as from MariaDB 5.5.42 to MariaDB 5.5.43, are not affected by this issue. It is also worth mentioning that if you are a MariaDB Enterprise subscriber you can safely ignore this message. Thanks to the additional testing and certification processes for MariaDB Enterprise, and its delayed release schedule which allows for additional community testing, MariaDB Enterprise releases are not affected by this bug. Thank you and sorry for the inconvenience, The MariaDB team -- MariaDB Website - http://mariadb.org Twitter - http://twitter.com/mariadb Google+ - http://google.com/+mariadb Facebook - http://fb.com/MariaDB.dbms Knowledge Base - http://mariadb.com/kb