White screen of death

[Tony Bazeley]

Hi all,

Attempting to access my drupal site shows a completely blank page - no timeout - just a blank page.

I did a much overdue upgrade to Drupal 6.13,
On completion was able to log in OK, change themes (back to 4 seasons), get out of maintenance mode, and test that a couple of pages worked OK.

I then upgraded  to the latest rootcandy theme (the theme was disabled and the system option was selected as the administrative theme)

This is where the trouble started

Initially all output was unthemed. I logged in as administrator and went to the themes page - when I did this WSOD commenced on all page requests.
I can now access nothing

I have checked the WSOD page http://drupal.org/node/158043
I can't see anything in the apache error log files.

http://www.example.com/admin/reports/dblog yields a blank screen

I have also edited index.php to enable errors as suggested on the WSOD page - no change

Removed the rootcandy theme from /sites/all/themes - but still no change

Any help would be greatly appreciated.

Thanks
Tony




--
[ Drupal support list | http://lists.drupal.org/ ]

[FredJones]

> Removed the rootcandy theme from /sites/all/themes - but still no change
>
> Any help would be greatly appreciated.

Can you manually edit the system table in the DB to enable only a core
theme like garland and then see what happens?
--
[ Drupal support list | http://lists.drupal.org/ ]

[A-NO-NE Music]

On 09/07/03(金), at 1:31, Tony Bazeley wrote:

> Attempting to access my drupal site shows a completely blank page -  
> no timeout - just a blank page.

When this happens, the first thing I do is to increase the memory  
size, which solves it all the time in my experiences.


--
- Hiro

Hiroaki Honshuku, A-NO-NE Music, Greater Boston
http://a-no-ne.com   http://anonemusic.com

--
[ Drupal support list | http://lists.drupal.org/ ]

[rotsen]

I get this when I add a module and what I do is to hit the 'Back' button on the browser and reload modules or remove the last module that I loaded
but I have never upgraded revision.  I never understood how such a well used software can go blank and there is not a solution for the
'blank screen of deat'

:-)

2009/7/3 A-NO-NE Music <madflute@...>

On 09/07/03(金), at 1:31, Tony Bazeley wrote:

Attempting to access my drupal site shows a completely blank page - no timeout - just a blank page.

When this happens, the first thing I do is to increase the memory size, which solves it all the time in my experiences.


--
- Hiro

Hiroaki Honshuku, A-NO-NE Music, Greater Boston
http://a-no-ne.com   http://anonemusic.com

--
[ Drupal support list | http://lists.drupal.org/ ]

--
[ Drupal support list | http://lists.drupal.org/ ]

[rotsen]

I meant to say the 'Blank screen of death'.

:-)

2009/7/7 Néstor <rotsen@...>

I get this when I add a module and what I do is to hit the 'Back' button on the browser and reload modules or remove the last module that I loaded
but I have never upgraded revision.  I never understood how such a well used software can go blank and there is not a solution for the
'blank screen of deat'

:-)

2009/7/3 A-NO-NE Music <madflute@...>

On 09/07/03(金), at 1:31, Tony Bazeley wrote:

Attempting to access my drupal site shows a completely blank page - no timeout - just a blank page.

When this happens, the first thing I do is to increase the memory size, which solves it all the time in my experiences.


--
- Hiro

Hiroaki Honshuku, A-NO-NE Music, Greater Boston
http://a-no-ne.com   http://anonemusic.com

--
[ Drupal support list | http://lists.drupal.org/ ]

--
[ Drupal support list | http://lists.drupal.org/ ]

[Julien Nebbout]

Hi!

Getting WSOD usually means you get some kind of runtime/syntax error in
the PHP code but have error reporting turned off.

You can check your php.ini, use the
error_reporting()/display_errors()/ini_set() functions or even use
.htaccess (see the comments at the bottom of the link below).

A first step could be to check your webserver logs, since PHP errors are
usually found in the httpd error log.

For more info check out
http://se.php.net/manual/en/errorfunc.configuration.php#ini.error-reporting

/J
--
[ Drupal support list | http://lists.drupal.org/ ]

[KOBA | Hans Rossel]

I think you best fix this in the database (take backup first):

- truncate all tables that start with cache_

- change active theme back to garland  (there is a 0 / 1 flag for this) as mentioned before

--
[ Drupal support list | http://lists.drupal.org/ ]