I'm beyond being a newbie, but still have much to learn. Right now I'm blocked on a Drupal 7 site of mine by a "white screen of death" (WSOD common enough to have an acronym).
Whenever I run into WSOD, the majority of the time it's related to using too much mem. Depending on what hosting your using, whether you upgraded from Drup6, etc, etc the WSOD could be caused form a lot of different situations.
My suggestion would be to FTP in and see if you can remove one or two of your non-mandatory modules (such as XML Sitemap, Footermap, etc if you have something like them) to see if it reduces the mem load enough.
It could also be a conflict between modules, a new module and core, etc.
What actions did you take just prior to the WSOD?
Oh, and um.... "Hi!!!!! My names Charles, and I'm a dev-in-training out of the Austin area!" hehe.
When you get a WSOD, Apache logs the error in it's error log. In Ubuntu servers, the default location is /var/log/apache2/error.log You'll want to look for "Fatal Error."
@cleverington is right about the memory thing though. That's the #1 error. You need to edit php.ini and set the memory_limit to something larger. I have mine set to 96M on most servers.
Thanks for the suggestions, but my hosting provider doesn't afford access to either error.og or php.ini. If its not in my user directory tree I can't view it, and no such file is found there.
I will try removing modules to see if that helps. I was never able to edit a new page, even before adding modules. I proceeded to add modules, thinking the problem was the lack of some module, but that didn't work.
I may just have to wipe the entire site and start over.
Raising the memory_limit to 96 didn't work, but disabling many modules did. However, I will eventually need most of those modules, so I will try enabling them one at a time until something breaks. Thanks for the suggestions.
If raising it to 96M with all of your modules installed didn't work, then I would just keep raising it by a little at a time until it does work (with all the modules you need enabled). Start with 128M and work your way up. It probably shouldn't require a whole lot more memory.
Agreed...this seems to be a relatively common issue with D7. At our Milwaukee Drupal User group, many folks who moved from D6 to D7 have had issues that were resolved by increasing the memory to at least 128M.
Also keep in mind that some modules can cause conflicts that won't resolve. For example, when Skinr was first released with Drup6, the Theme Builder module (Similar to the DrupalGardens ThemeBuilder) would cause the whole site to crash every time if they were both loaded.
After enjoying being able to add content again, I discovered I had to add yet more modules, and, perhaps no surprise, got the WSOD again. So tried raising the memory_limit to 256M. No joy. So disabled the modules I added, which is what I did before to get past the WSOD. But still have it. Is it necessary to actually uninstall those modules and remove the files? Disablement worked before. Any ideas?
Since this thread has been thoroughly hijacked at this point . ;)
You might want to make sure you have upgraded your views module recently. There was a known memory link in views-7.x late last year that persisted into February but has been resolved. 128 megs is usually enough be enough to run a normal website without issues unless you have enabled a ton of modules with a lot of image/file manipulation etc.
Comments
Okay, now what?
I'm beyond being a newbie, but still have much to learn. Right now I'm blocked on a Drupal 7 site of mine by a "white screen of death" (WSOD common enough to have an acronym).
Have you thrown in a new Module?
Whenever I run into WSOD, the majority of the time it's related to using too much mem. Depending on what hosting your using, whether you upgraded from Drup6, etc, etc the WSOD could be caused form a lot of different situations.
My suggestion would be to FTP in and see if you can remove one or two of your non-mandatory modules (such as XML Sitemap, Footermap, etc if you have something like them) to see if it reduces the mem load enough.
It could also be a conflict between modules, a new module and core, etc.
What actions did you take just prior to the WSOD?
Oh, and um.... "Hi!!!!! My names Charles, and I'm a dev-in-training out of the Austin area!" hehe.
~~Cheers!
cleverington
The man of many hats.
Look @ Apache error logs
When you get a WSOD, Apache logs the error in it's error log. In Ubuntu servers, the default location is /var/log/apache2/error.log You'll want to look for "Fatal Error."
@cleverington is right about the memory thing though. That's the #1 error. You need to edit php.ini and set the memory_limit to something larger. I have mine set to 96M on most servers.
No access to error.log or php.ini
Thanks for the suggestions, but my hosting provider doesn't afford access to either error.og or php.ini. If its not in my user directory tree I can't view it, and no such file is found there.
I will try removing modules to see if that helps. I was never able to edit a new page, even before adding modules. I proceeded to add modules, thinking the problem was the lack of some module, but that didn't work.
I may just have to wipe the entire site and start over.
Have to create local php.ini
My hosting provider allows one to create a local php.ini. I will try that.
Created local php.ini
Raising the memory_limit to 96 didn't work, but disabling many modules did. However, I will eventually need most of those modules, so I will try enabling them one at a time until something breaks. Thanks for the suggestions.
If raising it to 96M with all
If raising it to 96M with all of your modules installed didn't work, then I would just keep raising it by a little at a time until it does work (with all the modules you need enabled). Start with 128M and work your way up. It probably shouldn't require a whole lot more memory.
Agreed...this seems to be a
Agreed...this seems to be a relatively common issue with D7. At our Milwaukee Drupal User group, many folks who moved from D6 to D7 have had issues that were resolved by increasing the memory to at least 128M.
Conflicting Modules
Also keep in mind that some modules can cause conflicts that won't resolve. For example, when Skinr was first released with Drup6, the Theme Builder module (Similar to the DrupalGardens ThemeBuilder) would cause the whole site to crash every time if they were both loaded.
~~Cheers!
cleverington
The man of many hats.
WSOD is back
After enjoying being able to add content again, I discovered I had to add yet more modules, and, perhaps no surprise, got the WSOD again. So tried raising the memory_limit to 256M. No joy. So disabled the modules I added, which is what I did before to get past the WSOD. But still have it. Is it necessary to actually uninstall those modules and remove the files? Disablement worked before. Any ideas?
Page Manager module was the problem
Disabling it restored the ability to add and edit content.
Since this thread has been
Since this thread has been thoroughly hijacked at this point . ;)
You might want to make sure you have upgraded your views module recently. There was a known memory link in views-7.x late last year that persisted into February but has been resolved. 128 megs is usually enough be enough to run a normal website without issues unless you have enabled a ton of modules with a lot of image/file manipulation etc.