CiviCRM Community Forums (archive)

Hi all, I'm on an upgrade process of an older version, and was notified that I need to have MySQL 5.0, If I was to successfully upgrade to v2.2. So having done that, and had the account moved to the new server by my tech guru, I go to start the upgrade process & I hit this

Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 122880 bytes) in /home/xxxxxxx/public_html/subdomain/modules/civicrm/api/utils.php on line 1218

Obviously I have to proceed to the upgrade process to 2.1 , but i cant even get that far.

I've already increased memory to 128M in php.ini, with no effect.

Any ideas?

Thanks Kurund, but had already reviewed and implemented these suggestions before I posted.

Any other thoughts

This thread is old, so I'm going to assume that the original CiviCRM version discussed is out of date, but with 3.1 I'm getting the PHP memory exhausted error at step #6 of this guide: http://wiki.civicrm.org/confluence/display/CRMDOC32/Moving+an+Existing+Installation+to+a+New+Server+or+Location

When calling http://<drupal_site>/index.php?q=civicrm/admin/setting/updateConfigBackend&reset=1
It generates:
PHP Fatal error:  Allowed memory size of 1073741824 bytes exhausted (tried to allocate 983040 bytes) in /Users/<my_account>/Sites/<my_site>/trunk/sites/all/modules/civicrm/packages/Log.php on line 554

That's on a local development mac (trying to get a copy of the site from a development server), so i've already increased the php memory limit to 1024M (as evidenced from the error line above) and the php timeout to 120 seconds.  I find it incredible that CiviCRM would be using so much memory when i've got very little information (10 test users, 2 organizations, a couple membership types, one contribution page, etc.).

I could increase the memory up to 2+ GB, but again, it seems ridiculous that it's even using 1GB.  Were there any changes to 3.2 that would have fixed this problem?  Should I upgrade to 3.2?
Is there anyway to break up the update scripts to run in smaller pieces or is there any other way to accomplish this task?

Lobo,

Thanks for the reply... after a number of tries, i've gotten the migration process working and discovered a number of errors in the migration documentation.  E.g. step #6 should be split into 3 steps: 1. log into drupal, 2. enable civicrm module and 3. go to the updateConfigBackend url.

I was enabling the civicrm module prior to logging into drupal and that was causing it to attempt to run a huge number of civicrm updates... on top of trying to access and update tables that didn't exist (because the documentation said to mysqldump and --ignore-table).

I'll spend some time later today to document the correct process for drupal.

Thanks again for the reply!

Documentation posted here:
http://forum.civicrm.org/index.php/topic,15052.0.html

Since I'm new to the Civi community, i didn't feel right making the changes directly to the wiki, so hopefully someone can review what i've posted and approve or apply the changes to the wiki.

also... i should apologize for hijacking this thread.