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 »
  • Installing CiviCRM »
  • Drupal Installations (Moderator: Piotr Szotkowski) »
  • Out of memory with 3.1.3 (worked fine with 3.1.2) -- how to roll back?
Pages: [1]

Author Topic: Out of memory with 3.1.3 (worked fine with 3.1.2) -- how to roll back?  (Read 3429 times)

Steve Baker

  • I’m new here
  • *
  • Posts: 8
  • Karma: 1
Out of memory with 3.1.3 (worked fine with 3.1.2) -- how to roll back?
February 28, 2010, 04:54:33 am
Hello!

Just upgraded from 3.1.2 to 3.1.3 on my Drupal 6.15 installation on a shared Linux server via 1&1 hosting.

Unfortunately I'm now experiencing out of memory errors on my contribution pages.  I didn't perform any other changes or updates to the site, just the upgrade from 3.1.2 to 3.1.3.  In a small dash of desperation I disabled a few other Drupal modules and still have the same problem.

Of course this is the one upgrade where I didn't backup the database first, for shame for shame...  ;-)   It's too bad that 3.1.3 tipped me over the edge of my 40mb memory pool; I knew I was skating on thin ice and I simply hadn't encountered a memory problem before.

Until I figure out a plan to upgrade my service (assuming the folks at 1&1 won't simply increase the PHP memory limit) how can I roll back to the 3.1.2 version?  Would it work if I take the site offline, delete the sites/all/modules/civicrm directory, and untar the previous 3.1.2 version in its place?

Thanks for your guidance and for a terrific product (we really enjoy using it!),
Steve


Donald Lobo

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 15963
  • Karma: 470
    • CiviCRM site
  • CiviCRM version: 4.2+
  • CMS version: Drupal 7, Joomla 2.5+
  • MySQL version: 5.5.x
  • PHP version: 5.4.x
Re: Out of memory with 3.1.3 (worked fine with 3.1.2) -- how to roll back?
February 28, 2010, 07:26:42 am

yeah, i think going back to 3.1.2 should mainly work. no major sql changes made, so the DB should be in a good state

however getting a better host / plan / more php memory should be your main goal, IMO

lobo
A new CiviCRM Q&A resource needs YOUR help to get started. Visit our StackExchange proposed site, sign up and vote on 5 questions

Steve Baker

  • I’m new here
  • *
  • Posts: 8
  • Karma: 1
Re: Out of memory with 3.1.3 (worked fine with 3.1.2) -- how to roll back?
February 28, 2010, 08:59:02 am
Hello again,

Terrific, thanks so much for the quick reply and the good advice.  I rm'd the 3.1.3 directory and untar'd the 3.1.2 code in its place.  All seems to be working fine, in particular the contribution pages - yea!

While the 3.1.3 code pushed my site's allocated memory over the edge, it's also nudged me to either upgrade my hosting package or rehost elsewhere.  I do want to stay current with the CiviCRM releases and not have to worry about memory limits.

Cheers and thanks again!
Steve

Piotr Szotkowski

  • Moderator
  • I live on this forum
  • *****
  • Posts: 1497
  • Karma: 57
Re: Out of memory with 3.1.3 (worked fine with 3.1.2) -- how to roll back?
March 01, 2010, 08:29:45 am
Quote from: Steve Baker on February 28, 2010, 08:59:02 am
I rm'd the 3.1.3 directory and untar'd the 3.1.2 code in its place.  All seems to be working fine, in particular the contribution pages - yea!

Cool. :) Do take a backup now, though; just in case.

When you move (and/or upgrade to 3.1.4+), you might want to consider editing your database’s civicrm_domain table and changing the value in the version column to 3.1.2; this way the 3.1.2 → 3.1.3 SQL queries will be run again.

(As Lobo said: these queries do minor fixes, but it’s good to run them again just for consistency sake; I checked and running them multiple times won’t hurt.)
If you found the above helpful, please consider helping us in return – you can even steer CiviCRM’s future and help us extend CiviCRM in ways useful to you.

Denver Dave

  • Ask me questions
  • ****
  • Posts: 471
  • Karma: 9
Re: Out of memory with 3.1.3 (worked fine with 3.1.2) -- how to roll back?
March 04, 2010, 03:41:10 pm
I hold my breath also, install screen says 32 MB is minimal.  Wonder why the install takes so much memory and can't be run in 2 parts.  My move to 3.1.3 worked, but upgrade might not next time.

Steve Baker

  • I’m new here
  • *
  • Posts: 8
  • Karma: 1
Re: Out of memory with 3.1.3 (worked fine with 3.1.2) -- how to roll back?
March 07, 2010, 04:46:06 am
Hello again!

Great idea about tweaking the CiviCRM version from 3.1.3 back to 3.1.2 so that the upgrade script doesn't get confused.  Also, the site is now fully backed up!  :-)

About the memory limits and the upgrade script, I actually had no problems at all with the upgrade, nor with using the admin functions, nor with the reporting functions... the only error I encountered was with the outward-facing pages.

Specifically, I could easily view and navigate the contribution pages when logged in as the admin; however, when not logged in those same contribution pages choked with out of memory errors.

So... I figure it has to do with the public site theme?  My admin theme is a very clean Zen layout, while the public sees a different, slightly more elaborate theme.  I only have a few modules active (like Google analytics, FancyZoom, Robots.txt, Advanced Front Page, etc.) and have no blocks or anything like that enabled.

But... for whatever reason, the memory grab when combined with the outward-facing public theme was somehow increased juuuuuuust enough to tip my memory allocation over the top.  :-(

On the "inside" with the clean Zen theme, everything (administration functions, CiviReport reporting, and even viewing those same pesky contribution pages) was fine with the 3.1.3 install; just something tipped the scales when combined with the public theme.

Well, thanks again for the quick response, the good advice, and of course for a terrific system.  We'll figure out some way around the memory problem (rehosting the whole thing or standing up a parallel Drupal site with a skinny theme dedicated for CiviCRM functions) because we're very happy with Drupal + CiviCRM.

Cheers and thanks,
Steve



vrteach

  • Guest
Re: Out of memory with 3.1.3 (worked fine with 3.1.2) -- how to roll back?
March 09, 2010, 09:58:19 am
I just did a new install (my first) and ran into a memory problem right after installation. I'm on my own server (16GB RAM, 256MB php memory allocated).

I'm running Drupal 6.16, Fusion Theme (lightly modified), a good many modules including Domain access.

Enabling the civicrm module gives me the following error when going to the front page (or any other):

Fatal error: Allowed memory size of 266338304 bytes exhausted (tried to allocate 76 bytes) in /local/drupal/sites/all/modules/civicrm/CRM/Core/Error.php on line 397

Should I try 3.1.2? Are there other debugging steps that could give useful information?

Dave Greenberg

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 5760
  • Karma: 226
    • My CiviCRM Blog
Re: Out of memory with 3.1.3 (worked fine with 3.1.2) -- how to roll back?
March 09, 2010, 04:47:12 pm
In general 128MP php memory s/b more than enough unless you have lots of other drupal modules loaded. We had some reports in earlier CiviCRM versions of memory allocation issues related to CIVICRM_DSN (database connection) misconfigurations in civicrm.settings.php - but I think that problem was fixed. Still you should check that your DB credentials are valid / have access etc.
Protect your investment in CiviCRM by  becoming a Member!

Piotr Szotkowski

  • Moderator
  • I live on this forum
  • *****
  • Posts: 1497
  • Karma: 57
Re: Out of memory with 3.1.3 (worked fine with 3.1.2) -- how to roll back?
March 10, 2010, 03:10:48 am
Quote from: vrteach on March 09, 2010, 09:58:19 am
I'm running Drupal 6.16, Fusion Theme (lightly modified), a good many modules including Domain access.

Enabling the civicrm module gives me the following error when going to the front page (or any other):

Fatal error: Allowed memory size of 266338304 bytes exhausted (tried to allocate 76 bytes) in /local/drupal/sites/all/modules/civicrm/CRM/Core/Error.php on line 397

That’s a 254 MiB memory limit, so should be definitely more than enough for CiviCRM.

Is there a chance that you can try disabling other modules and check whether it’s indeed CiviCRM that is memory-hungry?

Quote
Should I try 3.1.2? Are there other debugging steps that could give useful information?

I don’t think we fixed any memory issues in 3.1.2 (nor 3.1.3 for that matter). You can try (a) checking the Drupal devel module to see how Drupal behaves without CiviCRM enabled and/or (b) for low level profiling use the CRM_Utils_System::memory() calls to see where CiviCRM might leak.
If you found the above helpful, please consider helping us in return – you can even steer CiviCRM’s future and help us extend CiviCRM in ways useful to you.

alfred_nutile

  • Ask me questions
  • ****
  • Posts: 464
  • Karma: 14
    • River Valley Tech Collective
Re: Out of memory with 3.1.3 (worked fine with 3.1.2) -- how to roll back?
March 12, 2010, 05:12:40 pm
If you turn on the drupal devel module and go to it's settings you can turn on all the memory reports.
This will slow your site down but you will get some great information about modules, memory and speed.
http://drupal.org/project/devel
Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Installing CiviCRM »
  • Drupal Installations (Moderator: Piotr Szotkowski) »
  • Out of memory with 3.1.3 (worked fine with 3.1.2) -- how to roll back?

This forum was archived on 2017-11-26.