Site Restoration

#33781 Kickstart restoration failure

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

n/a

CMS Type

Other

CMS Version

n/a

Backup Tool Version

n/a

Kickstart version

n/a

Latest post by on Monday, 26 October 2020 01:17 CDT

Thursday, 24 September 2020 15:59 CDT

virusys

During restoration of an Akeeba backup, the file restoration went extremely slowly. The database restoration did not proceed at all - I get the following error:

     Database restoration

     An error occurred while restoring the database. The error message can be found below. Click on the × button at the top right of this dialog message to close it and return to the database restoration page.

     HTTP Request Error

     HTTP Status: 504 (error)

     Internal status: error

     XHR ReadyState: 4

     Raw server response:

     Gateway Timeout

     The gateway did not receive a timely response from the upstream server or application.

     Additionally, a 504 Gateway Timeout error was encountered while trying to use an ErrorDocument to handle the request.

The DB appears to be fine. 

Do you have any thoughts? My site is currently down.

Edited by virusys on 2020-09-24 15:59 CDT

Friday, 25 September 2020 02:05 CDT

nicholas

Please note that Kickstart extracts the backup archive. Your database is restored by ANGIE, the restoration script which is part of your backup archive. Your problem is in ANGIE, not Kickstart.

This message comes from your server. It literally means that your web server thinks that PHP is taking too long to run.

The solution depends on when you get the message.

If you get the message immediately after starting to restore your database, without the progress bar having moved at all, you need to check the database connection information. If you enter the wrong information it is possible that PHP "hangs" trying to connect to the database server which causes the 504 Gateway Timeout error.

If this happens during the restoration of the database, after the progress bar has moved a little, you can try changing the timing settings. In the Database Restoration page, before you click the Next button, go all the way to the bottom. There's a Fine Tuning section. Set the Maximum Execution Time to 2 and the Throttle Time to 1000.

Please note that if you are on SiteGround the problem comes from their hosting platform. These issues started in early September. They were so bad and there was no commitment to resolve them that we had to urgently transfer our site from SiteGround to Rochen. If you are on SiteGround you will have to tell them about these issue and ask them to be fixed or consider looking for a host where the server doesn't randomly kill PHP processes. This not only makes restoring sites problematic, it is causing errors with otherwise functional sites throwing this error randomly at a rate that varies between making the site unreliable to making it practically inaccessible for everyone (that's the point we reached when we decided to move to a different host). SiteGround used to be a very good host but they have chosen to follow the direction of a mediocre, WordPress-only host lately.

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!

Monday, 26 October 2020 01:17 CDT

System Task

system

This ticket has been automatically closed. All tickets which have been inactive for a long time are automatically closed. If you believe that this ticket was closed in error, please contact us.

Edited by on 2020-10-26 01:17 CDT

Support