It's really just annoying at this point, because a page refresh makes the error page go away :-)
Still I am wondering what else I can do. The errors have been occurring as I enable modules and click the "save configuration" button. They start out:
Fatal error: Allowed memory size of 33554432 bytes exhausted
And end with something like
***/includes/database.mysqli.inc on line 162
(the error changes each time...don't know why)
I have edited the .htaccess file in drupal root to include:
php_value memory_limit 32M
The php configuration on the server says
Resource Limits memory_limit Maximum amount of memory a script may consume (32MB) 32M
I checked the forums, but the solutions didn't apply to what I have installed (except the page which suggests changing the .htaccess file :) )
Should I also edit the settings.php file?
Thanks,
Carol
Comments
Try setting it to 64mb and
Try setting it to 64mb and restart your web service. Take a look at this article also: http://drupal.org/node/207036
http://www.ojo.do
for settings.php
For settings.php you can add
ini_set('memory_limit','64M');
or use a higher value like 96 or 128 if necessary.
I find it doesn't take many modules to overflow the default 32M.
I agree. 128 M is not that
I agree. 128 M is not that uncommon for one of our sites, once you start adding some of the more memory-intensive modules.
@modulist
Yeah! tell me about it! (multiple modules and overflow)
This is just a test site, but it's on a hosted server. I saw something in one of the posts about being careful about setting the limit too high. I'm getting ready to set up a site on my own server (hence, the test site to play with), where it won't be a problem, but I have several other sites running on this hosted space (including sub domains on this particular test site). Would it potentially have any adverse effects on the rest of the sites if this one is set to 64M?
Thanks,
Carol
interesting
This is an interesting point ... does anyone know what happens when you define different memory limits in settings.php in a multisite installation? Do they all load independently, or ... ?
I know it works because I have some set up that way, but is there any downside to handling it like that?
memory_limit = 128M on VPS for years with no problems
Hi Carol (and everyone) - Please forgive me if this is useless blathering.
I have a virtual private server with root access and changed the memory_limit to 128M well over 1 year ago with no problems and my share of the box only gives me 256M. But then again it is a low volume site.
I double checked:
> cat /etc/php.ini | grep memmemory_limit = 128M ; Maximum amount of memory a script may consume
I would think anything in /etc/php.ini would limit any value in .httaccess or settings.php.
Good luck - Howard
location of php.ini
sorry - I just realized "/etc/php.ini" may not necessarily be everyone's path of php configuration - should have mentioned that - but in drupal:
admin>reports>status>php
should display its location.