Support

Site Restoration

#33160 HTTP Status: 500 (Internal Server Error) on Restoring the Database

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 Tuesday, 07 July 2020 17:17 CDT

Friday, 05 June 2020 12:07 CDT

potion
When I try and use kickstart (7) to restore a site to a newserver running on DirectAdmin 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: 500 (Internal Server Error)
Internal status: error
XHR ReadyState: 4
Raw server response:

I have ensured that the password has no special characters, and I have switched between MySQLi and MySQL(PDO) and in both occurrences it gives the above error message.

Prior to the error message I get the popup window indicating the size of the database 10.8Mb and nothing else. I did read in a support forum that if you changed in fine tuning the Max execution time for 1 and the throttle time 4000 (msec) - this showed more information in the popup window with varying results 22% completed 2.8Mb restored 16 minutes - then the error message.

I’m not sure what the original values were in the “fine tuning area” - I think 5 and 250 But what would you recommend? What would be a very slow setting to bypass the hosting providers security monitoring.

Thanks

Saturday, 06 June 2020 03:44 CDT

potion
Further updates on this is that the hosting company had limited the "Input/Output Usage. DB usage included" to 5Mbs which it exceeded (I'm only guessing as the graph seemed to indicate this).

I tried with a restoration of a site using the same Joomla and Kickstart versions but the database was only 4Mb and it worked.

My question is knowing that some hosting providers will have 'limits' applied would it not be a good implementation on Kickstart to have a "GO SLOW" option where it would 30 minutes to restore a site; this being a possible quicker option than manually trying to export large tables to manually import them later.

Sunday, 07 June 2020 10:41 CDT

nicholas
MySQL does not have a limit of bandwidth but it can be set up with a limit on the number of queries in a certain period of time, typically measured and set up as queries per hour.

Your host is setting that limit to very low values that make it impractical to restore a site. Probably they're running a limit of a few hundred to low thousands (e.g. 1,000 to 2,000) queries per hour which is OK if you expect to have less than 50 page views per hour. I would call that an unrealistic limit. You can serve more pages over a Raspberry Pi 4 and a domestic ADSL connection.

The reason why we don't support servers that restrictive is that you're essentially asking us to run less than one query per second. A virgin Joomla 3.9 installation with just the sample data would take over 3 hours to restore. Anything more useful than that, such as your site, would take over a day. We consider this to be unrealistic and unusable. Sure, we can write the code. But does it even make sense?

I'd wager that you're far better off moving to a decent host that's not stuck with database limits that were already too restrictive before the final episode of Friends aired in the USA.

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!

Tuesday, 07 July 2020 17: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-07-07 17:17 CDT

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!