Active
Project:
Boost
Version:
6.x-1.21
Component:
Miscellaneous
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
16 Apr 2013 at 06:25 UTC
Updated:
16 Apr 2013 at 12:52 UTC
Jump to comment: Most recent
I do have problem with boost
- Saving module page or trying to deactivate boost static page cache lead to the following error:
Fatal error: Allowed memory size of 2147483648 bytes exhausted (tried to allocate 900 bytes) in /home/shareontheweb/public_html/sites/all/modules/boost/boost.module on line 5315
- I cannot deactivate boost static page cache
- I cannot clear boost's database and file cache - 100K recirs, 300K files
How can I solve this and clean a$up all that? Can I directly delete files and truncate database tables? Which folders/ tables?
Thanks
Comments
Comment #1
jvieille commentedAlso impossible to disable the boost module...
Comment #2
Anonymous (not verified) commentedBaby steps first. (while you provide the other information).
Comment #3
jvieille commentedI don't wish to remove boost, but as it behave now, I cannot save my module page. Also I am experiencing some strange caching effect (pages not updated...)
I have a dedicated server, I can do what I want.
I cannot clear the cache through the interface. I don't know what to clear manually
Nothing changed specifically, but I have 400+ modules on this site, so something might have happened somewhere...
I removed the boost section in htaccess. This solved the caching issues but slowed down the site by 50%.
No way to disable Boost or clear the cache
Thanks very much for taking care.
Comment #4
Anonymous (not verified) commentedYou can clear the cache manually by just deleting the cache/normal/www.example.com folder. 400+ modules is not good at all, it's not surprising that there is some kind of interaction going on, but i doubt it is boost exactly, I'd disable the boost crawler if it's online. Boost works by saving the output buffer to a file, with 400 modules that's a lot of modules to load into memory just to compile a page to produce nothing (which is what it would be doing on the module page, it will be looking at every one but then discarding output as you are not an anonymous user).
This is a catch 22, you can't disable the modules until the module page loads. What you could try is moving the boost module folder temporarily. Disabling some modules (when the page loads) until you get to a point when you could put the boost folder back then turn it off and re-install it from the latest version (probably the dev version would be better) then re-enable the modules. Note down everything you disable as you do it, lest you miss a module.
Comment #5
jvieille commentedThanks, I'll try to fix that.
Wouldn't be easier / riskier to set the module status to 0 in the database system table?