Jump to content

Please help! Shop down! Upgrade failed! Rollback failed!


Recommended Posts

My shop is completely hosed. Upgrade from 1.6.0.x to 1.6.1.0 failed - and then the rollback failed:

 

All files upgraded. Now upgrading database...

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

 

and when I tried to rollback I got 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. I get a messed up ui I can log in to, but after login I get error 500. I copied back the manual backup I made but I get a blank white screen! No ui at all. What is my best option at this point? I am thinking maybe just reinstalling 1.6.0.x from scratch and restoring the database, but how do I determine what sub-version I had? 1.6.0.? Or is there a way I can manually roll back without installing from scratch?

Link to comment
Share on other sites

Did you allow the upgrade module to make a backup of your site? In that case the files should still be there under www.yourshop.com/admin/autoupgrade/backup in a zip file

 

The database is a bit more complicated: it consists of a lot of bz2 files in a subdirectory of this directory. They are compressed sql files. I am not sure what is the best way to restore from this your old database.

 

The file and directory names will tell you what was the version of the old installation.

 

My suggestion is: make a backup of this backup directory before you start experimenting.

Link to comment
Share on other sites

I was able to restore the shop folder. However, with the database down I get a white screen for the back office and an error 500 for the front office. Restoring the database is a bit more problematic as I need the database password. Is there a way to find this in the prestashop config files? I can reset the password, but that won't help since prestashop has to know the password.

Link to comment
Share on other sites

Ok, so I am back up and running. I was able to restore from the Prestshop DB backup by logging in to Myphpadmin for the database (through my host control panel - db password was in the setting.inc.php file), dropping all tables, and importing the largest of the 3 files (they all had the same modified date but once I had the interface running again I see they are from 3 different days). The shop is now functional again. Note that I had created a DB backup through the Prestashop UI before starting the upgrade - this was not from the upgrade process.

 

Clearly the "1-click upgrade" has a serious issue. Is Prestashop working to solve this problem? It has come up before and the cause has been a syntax error in one of their scripts. It's been fixed in previous releases, but clearly the 1.6.1.0 release has a syntax error again - one that causes both update and rollback to fail, at least in some circumstances.

Edited by madmartian (see edit history)
Link to comment
Share on other sites

  • 3 weeks later...

I am having a problem after upgrading. But more complicated root cause, I believe. After upgrading some of the modules were no longer visible on the site. After much messing around to try getting them back I decided to roll-back to a previous back up, and thought I could then upgrade again. I was locked out of the admn page My host helped get me back on. But it rolled back to what seemed to be a template. Only a about 4 of my items were on the site, with the template (Apple products) descriptions. In the Products section of the back office, 300+ items are showing — just the images and code. No titles, no prices, no descriptions.

 

Does anyone know how to get this information back? I can not find it in Public HTML folder. I can not find any older back ups other than from the day the problem began on August 24. My host support told me it appears that sections of the database are completely gone.

 

Any advice is greatly appreciated.

Link to comment
Share on other sites

  • 4 months later...

I am having a problem after upgrading. But more complicated root cause, I believe. After upgrading some of the modules were no longer visible on the site. After much messing around to try getting them back I decided to roll-back to a previous back up, and thought I could then upgrade again. I was locked out of the admn page My host helped get me back on. But it rolled back to what seemed to be a template. Only a about 4 of my items were on the site, with the template (Apple products) descriptions. In the Products section of the back office, 300+ items are showing — just the images and code. No titles, no prices, no descriptions.

 

Does anyone know how to get this information back? I can not find it in Public HTML folder. I can not find any older back ups other than from the day the problem began on August 24. My host support told me it appears that sections of the database are completely gone.

 

Any advice is greatly appreciated.

 

You really should start a new thread. No one will find this buried here in an unrelated thread.

Link to comment
Share on other sites

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).

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...