CiviCRM Community Forums (archive)

Hi,
We've managed previous civiCRM upgrades without incident, but this time no such luck.

The situation:
Stable 2.02 installation, which we've been using for around 6 months on drupal 5-7. We are trying to migrate to drupal 6-10 and civiCRM 2.1.6.

The drupal-6 migration went just fine, and we've been running off it for several days now. However, the civiCRM upgrade process is stuck.

What we did:
1. Made copy of database
2. Downloaded new civiCRM code into modules area
3. Put website into maintenance mode
4. Tried running the .../sites/all/modules/civicrm/install/upgrade.php?reset=1 upgrade script.

It was at step #4 where things get stuck. What I see from the web browser is that the thing is just spinning its wheels. The script never seems to complete and I don't get any messages or errors back. Eventually, the web connection just dies (page not found error). The "page not found" result happens exactly 3 minutes after I initiate the script.

If I try running the script a second time, it claims the database has been updated. But this seems unlikely, and trying to move onto the next steps doesn't work (i.e. rebuild menus step fails).

Questions:
1. Can the upgrade script be run from command-line?
2. How can I at least get some diagnostic messages to see where the hangup is?

Note: this is a shared host (dreamhost), where the sql performance has always seemed slow to me. However, I talked to their tech support and they claim the sql server and other hardware reports normal load levels. BTW, our database has around 8k contacts.

I've also tried doing this upgrade many times now, always with same result. I also tried the 2.1.0 release, without any luck. Any help or hints appreciated. We also played around with usual php settings to increase timeout and max-execution-time settings.

If you have tables like -

'civicrm_cache', 'civicrm_group_contact_cache', 'civicrm_menu', 'civicrm_discount', 'civicrm_pledge', 'civicrm_pledge_block', 'civicrm_pledge_payment'.

OR to be even more precise, the tables and columns mentioned in the file - http://svn.civicrm.org/civicrm/branches/v2.1/CRM/Upgrade/TwoOne/Form/TwoOneTwo.php (against first two if conditions) are -

present in your upgraded civicrm db, AND "version" column of "civicrm_domain" table is set to '2.1.6', implies you have successfully upgraded to v2.1.6.

ditto: same situation, same host, except it took a lot longer than 3 minutes to stop.  still, all checks out as per above.