While provisioning the site with the latest CiviCRM 4.1.1 version on D7 works fine, it crashes after running Verify with error in the failed task log:

CiviCRM: Generated config civicrm.settings.php file
CiviCRM: about to run _provision_civicrm_do_site_move()
Drush command terminated abnormally due to an unrecoverable error. Error: Call to undefined method CRM_Core_BAO_Setting::getConfigSettings() in /data/disk/o1/.drush/provision_civicrm/verify.provision.inc, line 222
Output from failed command : Generating civicrm settings file ..

When you run a diff between working and broken site civicrm.settings.php file, it reveals an empty CIVICRM_SITE_KEY:

-define( 'CIVICRM_SITE_KEY', 'add14229f7dc5aad05d3cfd33df4068a' );
+define( 'CIVICRM_SITE_KEY', '' );

FYI: this has been tested on the latest Aegir 2.x used in the BOA head.

Comments

omega8cc’s picture

omega8cc commented

I just tried it again with this patch reverted: http://drupalcode.org/project/provision_civicrm.git/commit/0b6e600 and now it fails, as expected, with previously known error:

CiviCRM: in _provision_civicrm_upgradedb()
Drush command terminated abnormally due to an unrecoverable error.
winston’s picture

winston commented

Just a note that I believe I'm getting the same issue in Civicrm 3.4.7. Will try to investigate further.

winston’s picture

winston commented

Apologies, didn't read this too carefully. I must have "previously known error".

pauleb’s picture

pauleb commented

I'm getting the same error message using provision 1.6, provision_civicrm 1.0-beta2 and drush 4.5 with civicrm >= 4.1.1.

I'm sorry, but I don't know what you mean with #1. "Fails as expected" sounds like a strange concept to me. Is there an error somewhere in my config or db, so that the verifying process is supposed to fail?

Forgive me my naivity, but I did some grepping in the civicrm directory for CRM_Core_BAO_Setting and for getConfigSettings().
I don't know about the coding conventions of civicrm, but for the case that CRM_Core_BAO_Setting should be the path from the civicrm root directory to the file and getConfigSettings() is the function, there is no function by this name in the file CRM/Core/BAO/Setting.php. But there is a function with this name in CRM/Core/BAO/ConfigSetting.php.

After changing CRM_Core_BAO_Setting::getConfigSettings() and CRM_Core_BAO_Setting::getBestGuessSettings to CRM_Core_BAO_ConfigSetting::* I got a bit further, but there seems to be another error.

CiviCRM: finished _provision_civicrm_fixpermissions()                                                    [notice]
CiviCRM: in _provision_civicrm_upgradedb()                                                               [notice]
Undefined variable: smarty Smarty.php:91                                                                 [notice]
Trying to get property of non-object Smarty.php:91                                                       [notice]
CiviCRM doeso not have permission to write temp files in , ExitingDrush command terminated abnormally due to an unrecoverable error.                                    [error]

You can find the whole drush provision-verify -vv output at http://pastebin.com/we3cArTT

pauleb’s picture

pauleb commented

I think I didn't get it.

It all works fine with the cloned git repository.

thx

bgm’s picture

bgm commented
Status: Active » Fixed

While debugging #1545902: Provisioning the site doesn't enable CiviCRM with any version - tested with Aegir 2.x based on 1.8 with omega88cc yesterday, we fixed the issues with the CRM_Core_BAO_Setting::getConfigSettings() and other stuff which will change in CiviCRM 4.2.

(some of those things changed in civi 4.1, others in 4.2, and I had done some changes a bit too quickly in the code, but now it should work fine with civi 3.x to 4.2-trunk)

I'm not sure about the Smarty warning, but it seems to be fixed?

pauleb’s picture

pauleb commented

I think I got this smarty error before but hadn't had the time for recherching. Maybe when I updated from civicrm 4.1.0 to 4.1.1 . I'm not sure about this, but the error felt quite familiar.

Version 57d3d790 from git fixed it, now it's possible again to restore, migrate and verify the site.

Thanks for the fixes.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

Anonymous’s picture

(not verified) commented
Issue summary: View changes

Debug log update