Upgrade Problem: 5.4.2.2 to latest
Permalink
I download the latest update and place it in updates/
I go to Sitewide Settings/Update in the Dashboard and press Update
After ~1 second the page becomes:
Some details that may be related:
* Unless I provide the update it does not say any are available
* We host the server ourselves, the LAMP stack works fine for all usage (see http://www.mysite.com)
* I have tried the "manual method" of simply replacing the concrete/ folder; the same error occurs
I go to Sitewide Settings/Update in the Dashboard and press Update
After ~1 second the page becomes:
An Unexpected Error occurred while upgrading: #0 /var/lib/wwwrun/www.mysite.com/htdocs/updates/concrete5.6.2.1/concrete/libraries/3rdparty/adodb/adodb.inc.php(1074): adodb_throw('mysqlt', 'EXECUTE', 1142, 'INDEX command d...', 'DROP INDEX arIs...', false, Object(ADODB_mysqlt)) #1 /var/lib/wwwrun/www.mysite.com/htdocs/updates/concrete5.6.2.1/concrete/libraries/3rdparty/adodb/adodb.inc.php(1049): ADOConnection->_Execute('DROP INDEX arIs...', false) #2 /var/lib/wwwrun/www.mysite.com/htdocs/updates/concrete5.6.2.1/concrete/libraries/3rdparty/adodb/adodb-datadict.inc.php(378): ADOConnection->Execute('DROP INDEX arIs...') #3 /var/lib/wwwrun/www.mysite.com/htdocs/updates/concrete5.6.2.1/concrete/libraries/3rdparty/adodb/adodb-xmlschema03.inc.php(1737): ADODB_DataDict->ExecuteSQLArray(Array, false) #4 /var/lib/wwwrun/www.mysite.com/htdocs/updates/concrete5.6.2.1/concrete/core/models/package.php(206): adoSchema->ExecuteSchema() #5 /var/lib/wwwrun/www.mysite.com/htdocs/updates/concrete5.6.2.1/concrete/helpers/concrete/upgrade/version_550.php(219): Concrete5_Model_Package::installDB('/var/lib/wwwrun...') #6 /var/lib/wwwrun/www.mysite.com/htdocs/updates/concrete5.6.2.1/concrete/core/controllers/single_pages/upgrade.php(243): ConcreteUpgradeVersion550Helper->prepare(Object(UpgradeController)) #7 /var/lib/wwwrun/www.mysite.com/htdocs/updates/concrete5.6.2.1/concrete/core/controllers/single_pages/upgrade.php(44): Concrete5_Controller_Upgrade->do_upgrade() #8 [internal function]: Concrete5_Controller_Upgrade->view('tools', 'required', 'upgrade') #9 /var/lib/wwwrun/www.mysite.com/htdocs/updates/concrete5.6.2.1/concrete/core/libraries/controller.php(264): call_user_func_array(Array, Array) #10 /var/lib/wwwrun/www.mysite.com/htdocs/updates/concrete5.6.2.1/concrete/core/libraries/controller.php(234): Concrete5_Library_Controller->runTask('view', Array) #11 /var/lib/wwwrun/www.mysite.com/htdocs/updates/concrete5.6.2.1/concrete/core/libraries/view.php(783): Concrete5_Library_Controller->setupAndRun() #12 /var/lib/wwwrun/www.mysite.com/htdocs/updates/concrete5.6.2.1/concrete/tools/upgrade.php(6): Concrete5_Library_View->render('/upgrade') #13 /var/lib/wwwrun/www.mysite.com/htdocs/updates/concrete5.6.2.1/concrete/startup/tools_upgrade_check.php(9): include('/var/lib/wwwrun...') #14 /var/lib/wwwrun/www.mysite.com/htdocs/updates/concrete5.6.2.1/concrete/dispatcher.php(105): require('/var/lib/wwwrun...') #15 /var/lib/wwwrun/www.mysite.com/htdocs/concrete/startup/updated_core_check.php(6): require('/var/lib/wwwrun...') #16 /var/lib/wwwrun/www.mysite.com/htdocs/concrete/dispatcher.php(14): require('/var/lib/wwwrun...') #17 /var/lib/wwwrun/www.mysite.com/htdocs/index.php(2): require('/var/lib/wwwrun...') #18 {main}
Some details that may be related:
* Unless I provide the update it does not say any are available
* We host the server ourselves, the LAMP stack works fine for all usage (see http://www.mysite.com)
* I have tried the "manual method" of simply replacing the concrete/ folder; the same error occurs
Ah!
Yeah that would do that.
Yeah that would do that.
Just to enhance this answer a bit more, in terms of the update jumps, I find it's best to go:
- Upgrade to latest 5.4 version (which is 5.4.2.2)
- Then upgrade to latest 5.5 version (which is 5.5.2.1)
- Then upgrade to latest 5.6 version
I think this is what Sheldon was meaning, but the version numbers he used aren't 100% right. I've done lots of upgrades lately to 5.6, stepping up from both from 5.4 and 5.5, and I find it works really well.
- Upgrade to latest 5.4 version (which is 5.4.2.2)
- Then upgrade to latest 5.5 version (which is 5.5.2.1)
- Then upgrade to latest 5.6 version
I think this is what Sheldon was meaning, but the version numbers he used aren't 100% right. I've done lots of upgrades lately to 5.6, stepping up from both from 5.4 and 5.5, and I find it works really well.
Were were able to successfully stagger our upgrades as suggested above. From say 5.6.0.1 to 5.6.1.2 the upgrade worked without a hitch, however when trying to then upgrade from 5.6.1.2 to 5.6.2.1 we were also receiving the above error referencing INDEX:
'.../updates/concrete5.6.2.1/concrete/libraries/3rdparty/adodb/adodb.inc.php(1074): adodb_throw('mysqlt', 'EXECUTE', 1142, 'INDEX command d...', 'DROP INDEX cPar...', false, Object(ADODB_mysqlt))...'
The solution did end up being the following related to db user permissions:
As posted here:
http://www.concrete5.org/community/forums/installation/an-unexpecte...
'So, I added the INDEX privilege to the user in mysql and that did the trick!'
'.../updates/concrete5.6.2.1/concrete/libraries/3rdparty/adodb/adodb.inc.php(1074): adodb_throw('mysqlt', 'EXECUTE', 1142, 'INDEX command d...', 'DROP INDEX cPar...', false, Object(ADODB_mysqlt))...'
The solution did end up being the following related to db user permissions:
As posted here:
http://www.concrete5.org/community/forums/installation/an-unexpecte...
'So, I added the INDEX privilege to the user in mysql and that did the trick!'
then
update slowly you can't jump from 5.4.2.2 to 5.6
**updating versions steps thanks to mesuva**
Just to enhance this answer a bit more, in terms of the update jumps, I find it's best to go:
- Upgrade to latest 5.4 version (which is 5.4.2.2)
- Then upgrade to latest 5.5 version (which is 5.5.2.1)
- Then upgrade to latest 5.6 version
***
its recommended after 5.4.2.2 to just use the dashboard update settings
http://www.rynomediaonline.com/resources/downgrading-your-concrete5...
http://www.concrete5.org/documentation/how-tos/developers/update-ve...