Database upgrade failed - have to restore shop

[ajs6116]

Hi all,

 

I tried to upgrade my shop and got the follow error:

 

All files upgraded. Now upgrading database...
[Ajax / Server Error for action upgradeDb] textStatus: "error " errorThrown:"Internal Server Error " jqXHR: " "

 

Anyone have any ideas as to what this error means.

 

I tried to rollback the changes. My back office seems to work ok but my front office I get 404s on all my pages except the main landing page.

 

Has any had these errors?  Seem like I will stuck at 1.6.0.9 with no way to keep up with future upgrades.

 

Any help would be greatly appreciated.

 

Thanks,

 

Art

[madmartian]

Did you solve this problem? I am having the same issue, going from 1.6.0 to 1.6.1, which shouldn't be a stretch:

 

All files upgraded. Now upgrading database...

[Ajax / Server Error for action upgradeDb] textStatus: "error " errorThrown:"Internal Server Error " jqXHR: " "

 

and when I try to rollback I get it again:

 

Database restoration file 000027 done. 32 file(s) left...

[Ajax / Server Error for action restoreDb] textStatus: "error " errorThrown:" " jqXHR: " "

 

thus completely destroying my shop. Luckily I made a manual backup.

[ajs6116]

Nope... but I did see someone else with the same problem said that it is a permissions issue, related to some Apache rules.

 

Check this thread:

 

https://www.prestashop.com/forums/topic/271134-solved-upgrade-fatal-error-internal-server-error-jqxhr/

[madmartian]

I believe I have solved the database upgrade failure problem. I tried to do a database backup through MySQL on my hosting control panel (not through PrestaShop). I did a backup and restore to a new DB and ended up with only 99 of the 252 tables. I tried it a second time with the same results. It was not giving an error message but was possibly timing out. I increased the timeouts (and a few other limits) in the ini files and the problem went away - and the 1-click upgrade worked flawlessly. 

 

This is overkill, but one of these things fixed the problem.

 

First, there are three ini files, so to be safe I made the same changes in all three files. Those files are:

 

php.ini

php5.ini

.user.ini

 

All are in the HTML root (not the prestashop folder). You likely only need to do this in one place, but I did not want to keep experimenting and don't have the knowledge to know which one to use, so I used all three and made them match.    These are the lines I either updated or added:

 

upload_max_filesize = 640M

post_max_size = 640M

max_file_uploads = 200

memory_limit = 320M

max_input_vars = 3000

max_input_time = 600

max_execution_time = 600

set_time_limit = 600

 

It was likely one of the time limit settings, but I increased the size limits as well so I wouldn't have to keep experimenting. Feel free to chime in if any of these are a bad idea. Note that I previously had the timeouts at 300 (5 minutes) and changed them to 600 (10 minutes).

[musicmaster]

Yes, size is often a problem when moving old databases. If you can't solve it with php.ini you can usually solve it by deleting statistics files (usually most of the size) and not exporting all tables at the same time.