Hi,
Not sure if this is related to Storm or not but I'm getting problems when I activate the Team module.
I cannot access some admin pages (like permissions).
I have:
memory_limit=500M
max_execution_time=300
I should have enough.
I have the following modules activated:
masquerade
block
color
comment
dblog
filter
help
menu
node
path
php
system
taxonomy
tracker
update
upload
user
adminrole
admin_menu
content
content_permissions
nodereference
number
optionwidgets
text
userreference
content_access
currency_api
date
date_api
date_timezone
formatted_number
format_number
http_request_fail_reset
money
phone
plugin_manager
statcounter
storm
stormattribute
stormexpense
storminvoice
stormnote
stormorganization
stormperson
stormproject
stormtask
stormteam
stormticket
stormtimetracking
subscriptions
subscriptions_cck
subscriptions_mail
subscriptions_ui
systeminfo
tokenSTARTER
token_actions
userloginbar
views_ui
forum
subscriptions_content
auto_nodetitle
fieldgroup
token
views
I've had this problem on and off for months now but always managed to find the right combination of modules. Now I don't know.
500MB should be enough.
Can anyone help?
Comments
Comment #1
Roberto Gerola commentedHi.
If you disable the Team module does it work correctly ?
It would be of great help if you could install the devel module.
It would permit to identify the module that is causing the problem.
Roberto
Comment #2
tchurch commentedYes, disabling Team makes it work.
I've installed the devel module but I'm not sure what I should do with it.
Comment #3
Magnity commented- Install and enable Devel.
- Go to Devel Settings in site configuration, ensure "Display memory usage" is checked.
- Memory usage should appear at the bottom of the page.
Comment #4
tchurch commentedDid that.
My main problem at the moment is the user/permissions page.
I get this (and only this) on the screen:
Memory used at: devel_init()=0.95 MB, devel_shutdown()=19.15 MB.
Comment #5
Magnity commentedDo you have normal access to the rest of your site?
And on the user/perm page - this is just a white screen with that text? That's odd.
Is Storm Team disabled at this point?
Comment #6
tchurch commentedI seem to have normal access to the rest of the site.
Storm team is disabled now and I still get the error.
Sometimes I get the memory info, other times I get the http 500 message.
Comment #7
Magnity commentedwhat type of server / hosting are you on?
Comment #8
tchurch commentedI've got some more information (I thought I'd already posted it but obviously not).
I get the following error message in my error log file:
[Wed Nov 04 12:00:53 2009] [error] [client 195.233.250.6] PHP Fatal error: Out of memory (allocated 31195136) (tried to allocate 1980955 bytes) in /home/sites/xyz.co.uk/public_html/includes/common.inc on line 167
I found this strange because I set the memory limit to 500.
I also found out that there was a web server limit which I could override using "RLimitMem 128000000" inside my .htaccess file for Drupal.
I don't know. After discussing with a friend (who knows Drupal better than me) the permissions page is created from looking through the active modules (not a database table) which is using over 32MB of memory (hence my problem).
It was only after upgrading Storm (with all the permissions it needs) that I actually found this (sorry for assuming it was Storm).
Should I re-direct this issue to Drupal core or just live with it?
What do you think, Magnity?
Comment #9
Magnity commentedThe reason I asked about your server is that the html 500 error usually indicates an internal server error.
From the information you have given so far, I don't think your server is giving you 500MB of memory - in fact as you see from the out of memory message returned by PHP, the limit seems more like 32MB.
Therefore, although the issue may be triggered by Storm adding that extra amount to tip it over the edge, the way to solve it is to find out why your server is only allowing 32MB rather than the 500MB you have allocated.
Depending on your set up - virtual / dedicated / etc., this may be under your control or your host's control if you don't administer the server yourself.
Comment #10
tchurch commentedI'm using shared (so I assume virtual) hosting.
I looked on their support pages and they said about the increase in the web server memory in the .htaccess file.
Let me know what you think.
Comment #11
Magnity commenteddoes the reports section of your site show how much memory drupal thinks it has?
i would contact your host for advice
Comment #12
tchurch commentedThe report page for PHP (and the phpinfo page) both show that I have 500MB, which is the limit I put in the php.ini file.
I will contact my host further about the limits.
Comment #13
Magnity commentedAny joy from your host?
Wondering whether this issue can be closed as there seems to be no signs that this is a specific Storm problem...?
Comment #14
tchurch commentedI haven't bothered contacting them really because the solution in #8 fixed my issue.
I was wondering if this issue should be re-directed to Drupal core (because of using too much memory when having lots of modules and permissions.
Comment #15
Magnity commentedOK. Glad it is no longer a problem.