-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Authelia fails to run migrations on empty database #7324
Comments
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
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. |
Tried |
Performing |
Version
v4.38.8
Deployment Method
Docker
Reverse Proxy
Traefik
Reverse Proxy Version
No response
Description
After updating authelia, I received an error about running one of the migrations (
11 to 15
, iirc), so since I don't have anything important in the authelia DB, (only one totp authenticator set up for one user), i just dropped all tables in the DB (only removing the duplicate index from the webauthn table didn't work, as it was constantly re-created). But now, with an empty DB, I'm getting the below error.Reproduction
I'm using this
ansible
role to set-up my docker containers: (create_db sets up a database in a mariadb server which is itself started in another role, there is also one for the redis container)Expectations
No response
Configuration (Authelia)
Build Information
Logs (Authelia)
Logs (Proxy / Application)
No response
Documentation
No response
Pre-Submission Checklist
I agree to follow the Code of Conduct
This is a bug report and not a support request
I have read the security policy and this bug report is not a security issue or security related issue
I have either included the complete configuration file or I am sure it's unrelated to the configuration
I have either included the complete debug / trace logs or the output of the build-info command if the logs are not relevant
I have provided all of the required information in full with the only alteration being reasonable sanitization in accordance with the Troubleshooting Sanitization reference guide
I have checked for related proxy or application logs and included them if available
I have checked for related issues and checked the documentation
The text was updated successfully, but these errors were encountered: