Authelia fails to run migrations on empty database about authelia

[glime-ai]

Please note this response was created using generative AI leveraging previously available information from the repository. This information may be helpful however it is our strong recommendation that you carefully consider the information before blindly applying it.

---

Based on the detailed logs and configuration you provided, it appears that the error you're encountering during the Authelia startup is related to a failed database migration from schema version 6 to 7. The specific error message indicates a problem with the MySQL database: "Error 1728 (HY000): Cannot load from mysql.proc. The table is probably corrupted."

This error suggests that there might be corruption in the MySQL system tables, specifically mysql.proc, which is used to store stored procedures and functions. Here are a few steps you can take to resolve this issue:

1. Check and Repair MySQL Tables: You can use the MySQL CHECK TABLE and REPAIR TABLE commands to check for corruption and attempt to repair it. For the mysql.proc table, you can run:

   CHECK TABLE mysql.proc;
   REPAIR TABLE mysql.proc;

2. Restore from Backup: If you have a backup of your MySQL database, consider restoring from the backup before the corruption occurred.

3. Reinitialize the Database: Since you mentioned that you don't have anything important in the Authelia database and already tried dropping all tables, you might consider reinitializing the database entirely. Make sure to drop the entire database and recreate it, rather than just dropping the tables, to ensure all system tables are correctly recreated.

4. Upgrade MySQL: If you're running an older version of MySQL, consider upgrading to a newer version. Sometimes, bugs related to system table corruption are resolved in newer versions.

5. Check MySQL Logs: Look into the MySQL error logs for any additional messages that might give more insight into what caused the corruption and how to prevent it in the future.

6. Re-run Authelia with a Clean Setup: After addressing the database issues, ensure that your Authelia configuration is correct and try running Authelia again. Make sure that the database connection settings in your configuration.yml are correct and that Authelia has the necessary permissions to access and modify the database.

If the problem persists after trying these steps, you might need to delve deeper into the specific configurations of your MySQL server or consider getting professional support for MySQL.

This comment was generated by Glime.

[m00nwtchr]

Tried 1. and 3., don't have a backup for this particular database, and I'm already running latest mariadb. (recently upgraded, if that could cause any issues)

[james-d-elliott]

Performing mysql_upgrade is not optional with MySQL/MariaDB when changing versions, it must be performed every time you upgrade it, as per their documentation. This is not a bug, it's a corrupt MySQL/MariaDB installation. See our docs for more information on why this isn't supported.