Posting in the Magento forums has been disabled pending the implementation of a new and improved forum solution which should better serve the community.

For new questions please post at magento.stackexchange.com, the community-run support site for the Magento community. We will be providing updates on the new forum solution soon. For questions or concerns please email community@magento.com.

Magento Forum

Successful Upgrade from 1.4 to 1.7 but has minimal problems
 
marionnex
Member
 
Total Posts:  38
Joined:  2012-03-30
 

Hello to all..

I am writing here because I need some help.. Please :(

I have a client who has a magento 1.4 website.
The website has more than 5K items, 7K customers and almost 2K orders that includes test orders.

The live/current website is fully customized from the front page to product pages.
The client wanted to upgrade the site to 1.7.0.2 and so here are the things I did.

First, I have copied the dump SQL from phpmyadmin and uploaded it to my own hosting account.
By the way, I have a VPS so I can simply do whatever I want there.
Then I have registered a .tk domain for the test site.

After importing the 4GB dump SQL, I have downloaded the archive 1.4.0.1 magento installation and have installed it for the test.
I have upgraded the site through shell from 1.4.0.1 to 1.4.2 as I cannot upgrade directly to 1.7 due to database structure changes.

Then after the successful upgrade to 1.4.2.0, I logged in to the admin area and checked is everything is ok.
It seemed that it was good. Everything was fine so I can go ahead and upgrade to 1.7.
So I logged in to the downloader (http://www.domain/downloader) and upgraded everything.
Check for updates > Commit changes

After upgrade, I changed file permissions as I was not able to visit the site after.
After the successful upgrade, everything seem to be ok except for these problems.

1.) I cannot reindex Product Prices for some reason, it just doesn’t reindex. I don’t know any turn around for this but I know I need to reindex it.

2.) The site always gets a 504 gateway error and the log says, “SQL has gone away”.
Basically I know what 504 means however I tried maximizing the packet and timeout on php.ini but I still get the same thing. I cannot visit the site anymore. I can visit the admin and the downloader page but not the site frontend.

These are just two problems I have encountered.. Just these…
Please help me. If more info is needed, I’d be more than happy to add it here..

Please help,,,

 
Magento Community Magento Community
Magento Community
Magento Community
 
GoMageTeam
Guru
 
Avatar
Total Posts:  356
Joined:  2013-01-13
Warsaw, Poland
 

Hello,

You need to update Magento to the version 1.4.2.0, but you should not use the Magento connect for it. You need to replace Magento files from the original archive or upgrade using SSH.
Then you should update Magento to the version 1.5.1.0.
Then you should update Magento to the version 1.6.1.
After these actions you should update Magento to the version 1.6.2.
And only after these actions, which have been mentioned above, you should update Magento to the version 1.7.0.2.
After each step you need to clear all the session files and cache and do the database reindex.
You can do the upgrade using the console or SSH:

chmod 700 ./mage
./mage mage-setup .
./
mage install community Mage_Downloader --force
./mage install community Mage_All_Latest --force

chmod 700 
./mage
./mage sync-pear
./mage list-installed
./mage list-upgrades
./mage install http://connect20.magentocommerce.com/community Mage_All_Latest --force
chmod 700 ./mage
./mage config-set preferred_state beta
./mage list-installed
./mage list-upgrades
If you have any problems with reindex after upgrading Magento from version 1.6.1 to version 1.6.2, you should use this link in order to get more information how to solve the problems:

http://indieswebs.com/blog/common-issues-and-their-solution-while-upgrading-magento-version-from-1-6-1-to-1-6-2/

You wrote that your database had a weight of 4Gb. It is a big weight. Most likely it is full of the logs . You can clear them using this SQL request’s:

TRUNCATE dataflow_batch_import;
TRUNCATE log_customer;
TRUNCATE log_quote;
TRUNCATE log_summary;
TRUNCATE log_summary_type;
TRUNCATE log_url;
TRUNCATE log_url_info;
TRUNCATE log_visitor;
TRUNCATE log_visitor_info;
TRUNCATE log_visitor_online;
TRUNCATE report_viewed_product_index;
TRUNCATE report_compared_product_index;
TRUNCATE report_event;

You should not do the backup using phpMyAdmin or any other clients of the databases. You should do it using the console (mysqldump utility) or using Magento: System->Tools->Backups

 
Magento Community Magento Community
Magento Community
Magento Community
 
marionnex
Member
 
Total Posts:  38
Joined:  2012-03-30
 
GoMageTeam - 07 March 2013 07:31 AM

Hello,

You need to update Magento to the version 1.4.2.0, but you should not use the Magento connect for it. You need to replace Magento files from the original archive or upgrade using SSH.
Then you should update Magento to the version 1.5.1.0.
Then you should update Magento to the version 1.6.1.
After these actions you should update Magento to the version 1.6.2.
And only after these actions, which have been mentioned above, you should update Magento to the version 1.7.0.2.
After each step you need to clear all the session files and cache and do the database reindex.
You can do the upgrade using the console or SSH:

chmod 700 ./mage
./mage mage-setup .
./
mage install community Mage_Downloader --force
./mage install community Mage_All_Latest --force

chmod 700 
./mage
./mage sync-pear
./mage list-installed
./mage list-upgrades
./mage install http://connect20.magentocommerce.com/community Mage_All_Latest --force
chmod 700 ./mage
./mage config-set preferred_state beta
./mage list-installed
./mage list-upgrades
If you have any problems with reindex after upgrading Magento from version 1.6.1 to version 1.6.2, you should use this link in order to get more information how to solve the problems:

http://indieswebs.com/blog/common-issues-and-their-solution-while-upgrading-magento-version-from-1-6-1-to-1-6-2/

You wrote that your database had a weight of 4Gb. It is a big weight. Most likely it is full of the logs . You can clear them using this SQL request’s:

TRUNCATE dataflow_batch_import;
TRUNCATE log_customer;
TRUNCATE log_quote;
TRUNCATE log_summary;
TRUNCATE log_summary_type;
TRUNCATE log_url;
TRUNCATE log_url_info;
TRUNCATE log_visitor;
TRUNCATE log_visitor_info;
TRUNCATE log_visitor_online;
TRUNCATE report_viewed_product_index;
TRUNCATE report_compared_product_index;
TRUNCATE report_event;

You should not do the backup using phpMyAdmin or any other clients of the databases. You should do it using the console (mysqldump utility) or using Magento: System->Tools->Backups

Thank you for your response… I really do appreciate it. I will bookmark this page as it’s already 12AM here in my country but will start working again after 6 hours. I just need to rest.

I will do your above instructions.

By the way, the problem I had was I didn’t know how to upgrade 1 version at a time.
The method I used was 1.4.0.1>1.4.2.0>1.7.0.2 ( I didn’t know how to not skip other versions but thanks you your advise. Will do this first thing in the morning.

Here is what I exactly/normally (Which I am willing to change)
chmod +x lib/PEAR
./pear mage-setup
./pear upgrade -f magento-core/Mage_All_Latest-stable

chmod 550 ./mage
./mage mage-setup
./mage sync

(UPGRADED TO 1.4.2)
Oh and I also do this if I get 500 internal server error
find . -type d -exec chmod 755 {} \;
find . -type f -exec chmod 644 {} \;

Then I upgrade to 1.7 using:
./mage upgrade-all --force

Then
rm -rf var/cache/* var/session/* var/locks/*
php shell/indexer.php reindexall

After 2 sec, Everything goes SQL has Gone Away..
For every Page..

So I want to thank you for your response. I will do exactly what you have written above…
Will also update for anything I get.

 
Magento Community Magento Community
Magento Community
Magento Community
Magento Community
Magento Community
Back to top