By darkelf on

I have Drupal 5 website on SourceForge (http://magicgarden.sf.net) and I have serious problems with its stability.
Almost all the time I notice white screens of death. No matter what I click.

First I had white screen of death in Drupal when I was sending images, then I read about PHP memory problems, I increased PHP to 16MB (more is not allowed on SourceForge) and it helped a little.

But what about problems other than sending images? What if I just want to enter page or click on menu and I see white screen of death?

I understand that white screen of death is kind of way to hide error message. But I want to see this message to know what is wrong and how to fix it.
I have logging enabled, but I don't see anything about it in logs (available from administer panel).

How can I fix my problem? How can I debug it?

⋅ Categories: Drupal 5.x

Comments

asbdpl’s picture

asbdpl commented

> I have Drupal 5 website on SourceForge (http://magicgarden.sf.net) and I have serious problems with its stability.
> Almost all the time I notice white screens of death. No matter what I click.

You should first check out http://drupal.org/node/158043.

What kind of logging do you have enable (database, webserver, php, drupal?)

Basically, I'd suggest for troubleshooting to disable all 3rd party modules; if it helps, then re-enable them one by one.

I'm running Drupal on a dedicated server and have a resource limit of 64M in php.ini (temporarily even 128M). The WSOD still appear irregulary on several sites and I've never figured out, what exactly is causing it.

Regards, -asbdpl

pranay2284’s picture

pranay2284 commented

You must disable all modules and then re-enable them one by one. You'll get to know the problem and the module which was causing it.

nabha’s picture

nabha commented

This worked for me when nothing else worked. (I couldn't get error messages at all, even with error messages turned on.) Thanks!

Anonymous’s picture

Anonymous (not verified) commented

"Basically, I'd suggest for troubleshooting to disable all 3rd party modules; if it helps, then re-enable them one by one."

It worked great for me but two details:

> to access the page to disable: http://monsite/?q=admin/build/modules
> the one which seems to be ... hem hem is Update Auto (or disable it during install -> no problem)

No memory changes or other :)

drfuzetto’s picture

drfuzetto commented

I was getting the white screen of death on all of my views with one of my custom modules enabled when I upgraded from 5.x to 6.x. After many hours of looking, I concluded that the problem was due to calling drupal_add_css at the top of my module outside any of the functions (or maybe it was the path_to_theme function). Once I put it in a preprocess function, the WSOD went away.

function MODULENAME_preprocess( $variables, $callback ){
  static $css_added = false;
  if( !$css_added ){
      drupal_add_css(path_to_theme() . '/css/mystyle.css');
      $css_added = true;
  }
}

Deborah Fuzetto

lilott8’s picture

lilott8 commented

If you have access to logs (/var/log/httpd/error*) will ALWAYS log what the problem is, usually down to the line! Would definitely look there if you can!