CiviCRM Community Forums (archive)

*

News:

Have a question about CiviCRM?
Get it answered quickly at the new
CiviCRM Stack Exchange Q+A site
This forum was archived on 25 November 2017. Learn more.
How to get involved.
What to do if you think you've found a bug.



  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Upgrading CiviCRM (Moderator: Deepak Srivastava) »
  • Failed upgrade from 4.29 to 4.3.3
Pages: [1]

Author Topic: Failed upgrade from 4.29 to 4.3.3  (Read 1139 times)

ldgpangeo

  • I post occasionally
  • **
  • Posts: 38
  • Karma: 0
  • CiviCRM version: 4.2.6
  • CMS version: drupal-7.17
  • MySQL version: 5.5.23
  • PHP version: 5.3.13
Failed upgrade from 4.29 to 4.3.3
May 11, 2013, 06:48:12 pm
My upgrade from 4.2.9 to 4.33 went smoothly until the step to update the mysql database
   http://<your_drupal_home>/civicrm/upgrade?reset=1

Instead of opening the upgrade page, I'm redirected back to drupal's user page.    As a result, basic civicrm searches succeed but any attempt to display detailed information fails with a "field not found" error -- presumably because the db is not updated.

I've previously done about 5 updates on my development instances with no problems.  The only substantive difference between my dev instances and this one is that it's remote hosted.   Since it's a production instance, I have reverted it back to 4.2.9 until I have a strategy for resolving the problem.

How do I get past this roadblock?

Coleman Watts

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 2346
  • Karma: 183
  • CiviCRM version: The Bleeding Edge
  • CMS version: Various
Re: Failed upgrade from 4.29 to 4.3.3
May 11, 2013, 07:45:08 pm
Why not use drush?
Try asking your question on the new CiviCRM help site.

Hershel

  • Forum Godess / God
  • I’m (like) Lobo ;)
  • *****
  • Posts: 4640
  • Karma: 176
    • CiviHosting
  • CiviCRM version: Latest
  • CMS version: Mostly WordPress and Drupal
Re: Failed upgrade from 4.29 to 4.3.3
May 12, 2013, 08:55:07 am
Or try a smaller jump in versions--sometimes that helps.
CiviHosting and CiviOnline -- The CiviCRM hosting experts, since 2007

See here for the official: What to do if you think you've found a bug.

ldgpangeo

  • I post occasionally
  • **
  • Posts: 38
  • Karma: 0
  • CiviCRM version: 4.2.6
  • CMS version: drupal-7.17
  • MySQL version: 5.5.23
  • PHP version: 5.3.13
Re: Failed upgrade from 4.29 to 4.3.3
May 12, 2013, 12:41:45 pm
drush is not very practical because I don't really have good terminal level access to the site. 

--------------

What do you mean by a "jump in version"?    I'm not familiar with that.

Coleman Watts

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 2346
  • Karma: 183
  • CiviCRM version: The Bleeding Edge
  • CMS version: Various
Re: Failed upgrade from 4.29 to 4.3.3
May 12, 2013, 01:33:13 pm
Hershel means don't try to upgrade too many versions at once. But in this case, I think 4.2 -> 4.3 is about as small as it gets.
Try asking your question on the new CiviCRM help site.

Hershel

  • Forum Godess / God
  • I’m (like) Lobo ;)
  • *****
  • Posts: 4640
  • Karma: 176
    • CiviHosting
  • CiviCRM version: Latest
  • CMS version: Mostly WordPress and Drupal
Re: Failed upgrade from 4.29 to 4.3.3
May 12, 2013, 01:37:33 pm
Yes, I guess "4.2.9 to 4.3.3" is pretty small. When you tried, did you flush Drupal caches and also remove all CiviCRM cached template files?
CiviHosting and CiviOnline -- The CiviCRM hosting experts, since 2007

See here for the official: What to do if you think you've found a bug.

Eileen

  • Forum Godess / God
  • I’m (like) Lobo ;)
  • *****
  • Posts: 4195
  • Karma: 218
    • Fuzion
Re: Failed upgrade from 4.29 to 4.3.3
May 12, 2013, 03:01:18 pm
Redirecting back to the drupal user page doesn't seem like a particularly 'Civi' thing to do. Hershel's suggestions could be the trick. Otherwise you probably want to check drupal permissions, any drupal redirection configuration and perhaps try turning off drupal modules that might be interferring
Make today the day you step up to support CiviCRM and all the amazing organisations that are using it to improve our world - http://civicrm.org/contribute

ldgpangeo

  • I post occasionally
  • **
  • Posts: 38
  • Karma: 0
  • CiviCRM version: 4.2.6
  • CMS version: drupal-7.17
  • MySQL version: 5.5.23
  • PHP version: 5.3.13
Re: Failed upgrade from 4.29 to 4.3.3
May 13, 2013, 06:53:06 pm
I believe I've finally found the problem.

Version 4.3 begins to use triggers and database functions within mysql.  There are some database security aspects that can be problematic -- particularly if a multi-site hosting service has the database locked down. 

I found I was able to upgrade the database by exporting it to my development box, performing the upload there, and then exporting it back to the production box -- with one major SNAFU.

mysqldump commands include the "definer" in the definitions for triggers and functions.  (e.g. CREATE DEFINER = `user`@`localhost` FUNCTION `civicrm_strip_non_numeric`...   

This causes major problems if the database user on the two systems are not identical, because you then need special "SUPER" privs to create a trigger or function in behalf of a different user. 

In the end, I had to do a search/replace to change the username to the one on the production site in order to install the upgraded database. 

You might need to watch out for this when migrating databases across systems.
Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Upgrading CiviCRM (Moderator: Deepak Srivastava) »
  • Failed upgrade from 4.29 to 4.3.3

This forum was archived on 2017-11-26.