Details
-
Type:
Bug
-
Status: Done/Fixed
-
Priority:
Trivial
-
Resolution: Cannot Reproduce
-
Affects Version/s: 4.4.6
-
Fix Version/s: 4.4.9
-
Component/s: Core CiviCRM, Drupal Integration Modules
-
Labels:None
-
Documentation Required?:None
Description
When upgrading using Drush:
1. Code backed up.
Database dump saved to <deleted>/../backup/modules/20140719113138/civicrm.sql [success]
2. Database backed up. [ok]
3. Tarfile unpacked. [ok]
WD php: Exception: Your database has already been upgraded to CiviCRM 4.4.5 in CRM_Upgrade_Headless->run() (line 50 of [error]
<deleted>/sites/all/modules/civicrm/CRM/Upgrade/Headless.php).
Cannot modify header information - headers already sent by (output started at /<deleted>/drush/includes/output.inc:38) bootstrap.inc:1224 [warning]
Exception: Your database has already been upgraded to CiviCRM 4.4.5 in CRM_Upgrade_Headless->run() (line 50 of /<deleted>/sites/all/modules/civicrm/CRM/Upgrade/Headless.php).
Drush command terminated abnormally due to an unrecoverable error. [error]
CiviCRM continues to operate and I have to upgrade civicrm/upgrade?reset=1 in Drupal itself which correctly updates 4.4.5 to 4.4.6
Attachments
Activity
@Eileen: The issue was that doing an upgrade from 4.4.5 to 4.4.6 using Drush attempts to do an update to the database version 4.4.5 (which obviously fails) instead of 4.4.6.
Using the web interface everything off course worked but the web interface is fiddly, sometimes CiviCRM takes longer than the PHP timeout to complete certain commands (eg. enabling logging which borks half the triggers) which could cause major issues.
since 4.4.7 is out you should check if that works fine for you - not that you might want to double check all files in templates_c are deleted first as permissions over the cached version.tpl could cause the version to be misrepresented and a common problem using drush is that the permissions get messed up as the webuser of the drush user may own the files & not have correct permissions for the other.
My guess is this problem is irrelevant now 4.4.8 is out so putting to can't reproduce
in general I don't think 'your db has already been upgraded' needs to be an exception / error. The fact the script has already been run might be worthy of a message but an exception implies a problem. In the reported case maybe there was one? We usually run drush @sites civicrm-upgrade-db fairly often along with drush updb to make sure updates haven't been missed