I've got a Drupal installation that formerly labored perfectly on my small localhost. However, now, following a formatted my computer, it simply shows an empty screen (completely whitened).

So my real question is, how do i see where situations are failing, basically can't even log in to the sever?

The only real errors I'm able to find are (obtained from the Apache Error Logs):

[Tue May 17 05:05:04 2011] [notice] Parent: child process exited with status 255 -- Restarting.
[Tue May 17 05:05:04 2011] [notice] Digest: generating secret for digest authentication ...
[Tue May 17 05:05:04 2011] [notice] Digest: done
[Tue May 17 05:05:07 2011] [notice] Apache/2.2.11 (Win32) DAV/2 mod_ssl/2.2.11 OpenSSL/0.9.8i PHP/5.2.9 configured -- resuming normal operations
[Tue May 17 05:05:07 2011] [notice] Server built: Dec 10 2008 00:10:06
[Tue May 17 05:05:07 2011] [notice] Parent: Created child process 6992

You will find no errors in Watchdog...

I'm using Xamp 1.7.1 (PHP 5.2) and Drupal 6.

I simply should also point out that after i try to load the website on my small local machine, apache also crashes! I added this:

ini_set('display_errors', TRUE);
ini_set('display_startup_errors', TRUE);

Also it still just shows the screen of dying? How can i really see errors?

I additionally found this in apache access.log: - - [17/May/2011:05:22:14 +0200] "GET /greekmerchant/src/ HTTP/1.1" 200 3 - - [17/May/2011:05:25:45 +0200] "GET /greekmerchant/src/update.php HTTP/1.1" 302 - - - [17/May/2011:05:25:46 +0200] "GET /greekmerchant/src/update.php?op=info HTTP/1.1" 200 -

... after attempting to access update.php. Additionally, it just would go to a whitened screen.

I've this during my sql config file:

port= 3306
socket= "C:/xampp/mysql/mysql.sock"
key_buffer = 16M
max_allowed_packet = 128M
table_cache = 64
sort_buffer_size = 512K
net_buffer_length = 8K
read_buffer_size = 256K
read_rnd_buffer_size = 512K
myisam_sort_buffer_size = 8M


max_allowed_packet = 128M

Also, my PHP memory is placed to 1024MB.

Anybody got any idea why case dying? Could it be a real memory problem? What else can one do in order to get errors proven in my experience? I still see nothing despite enabling error logging.


The web site operates on my local machine basically remove the files folder. So, for whatever reason, if this needs to access files within the files folder, it expires of memory. Why? Or even better, what is leading to this unneccessary use of memory?

There's an entire page within the Drupal hand books devoted to debugging the "White Screen of Death". The bottom line is, enable error confirming with the addition of the next towards the top of your index.php file:

ini_set('display_errors', TRUE);
ini_set('display_startup_errors', TRUE);

...and appearance the logs, which you've already began to complete. Individuals two steps often target the problem, more often than not. In the event that does not point you towards an answer, continue lower the guide page, for much more tips.

Basically needed to have a wild guess, I'd say your situation is most likely an out-of-memory error.

Look at your error confirming configurations for PHP. You may want to enable error confirming.

This might help: http://drupal.org/node/158043