Support

Site Restoration

#41313 An error while extracting the backup file with kick start

Posted in ‘Site restoration’
This is a public ticket

Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.

Environment Information

PHP version
8.3.8
CMS Type
WordPress
CMS Version
6.6.2
Backup Tool Version
Akeeba back pro 8.1.2
Kickstart version
kickstart pro 8.0.6

Latest post by nicholas on Thursday, 14 November 2024 06:03 CST

taksejimo

The backup files were created with akeeba backup pro 8.1.2.  Then the backup files were uploaded to the restore folder and extract process was started.

An error occurred while extracting the backup file with kick start pro 8.0.6.

I retried to create backup files, upload and extract process. The same error happend.

Please teach me what is wrong and how to resolve.

Regards, T.Sejimo

 

nicholas
Akeeba Staff
Manager

It looks like your backup archive is corrupt. You may be able to extract the archive if you enable the "Ignore most errors" option in Kickstart.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

taksejimo

Following your advice, I enabled "Ignore most errors" option in Kickstart.  Still kickstart failed in the middle of extract process.

Then I uninstalled akeeba backup 8.2.7 and re-installed it. After Configuration Wizard run, I found the following message on the Home page, "We have detected that one or more tables with the enpwp1_ak_ prefix are broken. Akeeba Backup for WordPress will not work properly. Please ask your host to repair these tables and then click here to let Akeeba Backup for WordPress update its database tables".

According to the above message, one or more tables with the enpwp1_ak_ prefix must be repaired. However I am not sure how to repair them.
Please teach me how to repair them or let me know the documentation for the repair.  

Regards, T. Sejimo

nicholas
Akeeba Staff
Manager

I believe that something might not have gone right during uninstallation.

First, disable the plugin. Then uninstall it. Check if all tables with the enpwp1_ak_ prefix have been removed. Then, install the plugin again. Then activate it.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

taksejimo

Following the advice, I disabled and uninstalled akeeba backup plugin. Then I confirmed no enpwp1_ak_ prefix on the detabase.

I installed akeeba backup plugin again and started back up process. AJAX loading error occurred about 30 minutes later.

Please tell me what should be done.

Regards, T.Sejimo

nicholas
Akeeba Staff
Manager

The instructions I gave you were to fix the database tables problems.

To help you with a backup issue I need you to ZIP and attach the backup log file. If there is no backup log file and/or no backup record please do tell me because that's a completely different issue which requires a different approach.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

taksejimo

AJAX loading error has gone because of setting max excetiontime:300->420 on php.ini and adding define('WP_MEMORY_LIMIT', '512M')MEMORY_LIMIT', '512M') on wp-config.php.

 Akeeba backup process finished with no error. However extracting files of kickstart failed again due to invalid header in archive files, part 5. 

All the errors so far have the same cause and occured in the same location: PART 5.

I attached the error message PNG, akeeba configuration PDF and Kickstart configuration PDF.

Is any parameter for akeeba backup configuration wrong?

Is there something wrong with my kickstart configuration?

Does any operation of akeeba back up and kickstart have any problem?

Please tell me how to solve or bypass the problem.

Regards, T. Sejimo

 

 

nicholas
Akeeba Staff
Manager

I really need that backup log file. 

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

taksejimo

Unfortunately no log files on akeeba backup and kickstart.

I found an explanation that akeeba Backup 8.2.7: Could not work with MySQL 5.x and MariaDB 10.x on CHANGELOG.php.  The akeeba backup version I use is 5.7.

Is it correct? If so, tell me which akeeba backup version work with Mysql5.7. I'm planning to upgrade mysql 5.7 to 8.0 by restoring it with kickstart.

Regards, T.Sejimo.

 

nicholas
Akeeba Staff
Manager

Start by updating Akeeba Backup.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

taksejimo

Since it proved akeeba backup pro 8.2.7 does not support mysql 5.7,I used akeeba backup pro 8.1.2 and kickstart pro 8.0.4. Akeeba backup finished with no error. However Kickstart failed with invalid header in archive file and no log file.

Akeeba backup pro 8.1.2 seems not support mysql 5.7.

Which version of akeeba backup core or pro support mysql 5.7? 

How to get it? 

Thanks in advance for your support.      T.Sejimo

nicholas
Akeeba Staff
Manager

The entirety of the CHANGELOG for Akeeba Backup for WordPress 8.2.7 is as follows:

Changelog

Critical bugs and important changes

  • Could not work with MySQL 5.x and MariaDB 10.x

If it isn't blatantly obvious by its name, a CHANGELOG “is a log or record of all notable changes made to a project”. It describes the important changes made since the previous version.

As it is blatantly obvious by this changelog, there was a bug in Akeeba Backup for WordPress 8.2.6 which broke compatibility with MySQL 5.x and MariaDB 10.x. Since WE VERY OBVIOUSLY STILL SUPPORT MYSQL 5.7 IN AKEEBA BACKUP FOR WORDPRESS 8.X this was considered a critical bug, it was fixed urgently, and triggered the immediate release of 8.2.7.

As it is blatantly obvious, Akeeba Backup for WordPress 8.2.7 is compatible with MySQL 5.7.

As it is blatantly obvious, all versions of Akeeba Backup for WordPress in the 8.x range are compatible with MySQL 5.7, bar from the buggy version 8.2.6 which was immediately retracted and replaced with the fixed version 8.2.7.

Finally, do remember that I am the author of this software and have been maintaining it the last 18 years. When I tell you to update, I expect you to follow my instructions and update. I do not want you to debate whether you should update. As noted in our Terms of Service, doing that automatically results in us closing your ticket and refusing any further assistance on the issue.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Support Information

Working hours: We are open Monday to Friday, 9am to 7pm Cyprus timezone (EET / EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets outside of our working hours, but we cannot respond to them until we're back at the office.

Support policy: We would like to kindly inform you that when using our support you have already agreed to the Support Policy which is part of our Terms of Service. Thank you for your understanding and for helping us help you!