-
Notifications
You must be signed in to change notification settings - Fork 47
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
Not working on RHEL 7 based system #32
Comments
Update:
|
Found the issue:
have to set the exact same number for the backup applications my.cnf file $ vim /etc/my.cnf
#added
innodb_log_file_size=50331648 Now the server started. |
I've edited your posts to review the format. As discussed in Gitter, I should review how to support systemctl. And besides, mariadb or percona-server while where at it. I think I'll let the user manage the stop/start of the database service, I'll think about it. |
Ran into the same issue with xtrabackup/innobackupex in Centos 7. |
Found out, while trying to restore a backup, that the script is not able to run. Most likely because the command called for stopping the mysql service is wrong.
It should look like this: systemctl restart mariadb
After the change of command_executor.py at line 67
The backup seems to run fine:
HOWEVER:
Somewhy this did not restart the mariadb service. If I try to start it manually it gives me the stranges error I've ever seen connected to mariadb:
The text was updated successfully, but these errors were encountered: