-
Notifications
You must be signed in to change notification settings - Fork 529
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
Incorrect key file for table 'pro_accounts_auto_signin'; try to repair it
during bin/run.sh
#25
Comments
Same problem for me ... It happens during :
Full Traceback is :
and
|
@Nabellaleen — what OS are you trying to install on? I never did figure this out, but I'm curious if it is a cross-OS issue or not. Are you using MySQL or MariaDB? |
Yeah, sorry to have not be more precise. I am on Fedora, with MariaDB "aliased" in mysql. Maybe a bug specific to RedHat-like distribution, seeing you are on CentOS ? |
Same in RHEL5 + MariaDB |
i assume this is only a problem with newer MariaDB versions. 10.0.21-MariaDB fails, 5.5.44-MariaDB and 5.6.26-MySQL work without any issues. you are gonna have to drop all tables in the DB before starting again or it'll just fail at renaming the table pro_users that has already been renamed |
I installed it on MacOS and everything worked fine |
I can confirm this error with mariadb:10.0.21. Using mysql helped here. @X41 Is there any information when your patch will propagate to upstream? I'm using the custom fork at https://github.com/TransforMap/hackpad and feel quite tempted to cherry-pick your contribution. |
there is no pull request because i suck at git and github tbh and i'm too lazy to check how it's done. if someone could tell me how it's done real quick i'll do it, feel free to just cherry-pick it till then |
I've been generally following this guide for installing
hackpad
on CentOS to install it on my Fedora box. Everything seems fine except for getting aIncorrect key file for table 'pro_accounts_auto_signin'; try to repair it
error duringbin/run.sh
.Everything I've read seems to indicate this is either a probably with not enough disk space or with a corrupted table, but I have both plenty of free space and trying to repair that table doesn't work.
Thoughts?
The text was updated successfully, but these errors were encountered: