white screen of Death - in index page

By yubaraj on 12 Apr 2007 at 06:41 UTC

When i click on the index page of mine, i have got a blank screen. The same problem occurs when going to admin>> modules. The modules page is also blank. Others all page are fine. This intranet was finished one month ago and no more codes are being changed since then, The error occured on 3 days earlier only.

I have tried with:

- increasing memory size in php.ini or in settings.php
- checking with all other files, no error in the access log
- changing the whole database, cleaning cache and session tables.

Can anybody help me out with this?

Comments

make sure to run the

litwol commented 12 April 2007 at 07:19

make sure to run the php_info() function and check to see that memory_limit is more than 8 megs.

Sometimes something interesting appears on http://litwol.com

Maybe you've got too many

pobster commented 12 April 2007 at 08:58

Maybe you've got too many modules in your modules folder? Just because they're not enabled doesn't matter when navigating to admin:modules as they all eat memory when they're being checked for information.

Pobster

no, thats what drupal uses

litwol commented 12 April 2007 at 12:58

no, thats what drupal uses the .info files for.

Sometimes something interesting appears on http://litwol.com

I realise you think you're

pobster commented 12 April 2007 at 14:13

I realise you think you're helping, but this forum topic is tagged Drupal 4.6 - what .info files?

Pobster

oi! i am sincerely sorry. i

litwol commented 12 April 2007 at 15:05

oi! i am sincerely sorry. i didnt pay attention to the tag. sorry again. is it possible to delete my comments above since i realize now they are geared towards 5.x.

thank you and again i'm very sorry.

Sometimes something interesting appears on http://litwol.com

I also had the same problem,

rseiser commented 5 June 2007 at 01:46

I also had the same problem, and it took me a while to figure it out. The answer was simple: My php installation (new version) was setup to "not" display error messages on the screen (I guess since they look ugly, or are a security risk if you show the world what files etc. you are using). So if an error occurred it usually shows the white screen with the error message on top. Since the error message was not shown the screen was white and blank. After I allowed for error messages to be displayed (in my php.ini file), I could see indeed an error message, that I forgot some } or something in one of my included snippets. After I fixed my code, everything was fine.
In general I noticed that when I switched to newer versions of apache, php, and mysql, that some things were stricter, and I had to be more precise with my programming.

I got the same problem on my

Sadmir commented 5 June 2007 at 02:13

I got the same problem on my site. it's just blank, I can't even login, Please give me any suggestions what I can do...

Thank you

www.TechFeed.ca | Your Daily Technology Feed Source

=-=

vm commented 5 June 2007 at 02:17

check your apache error logs for the error being thrown.

This might sound stupid, but

Sadmir commented 5 June 2007 at 02:19

This might sound stupid, but how do I do that?

www.TechFeed.ca | Your Daily Technology Feed Source

=-=

vm commented 5 June 2007 at 02:25

apache error logs are typically stored one level above your public root, if they are not there, you will have to ask you host for a copy of your apache error logs or check your hosts documentation for the location of these logs where server (not Drupal) errors are stored.

Ok I've just talked to

Sadmir commented 5 June 2007 at 03:17

Ok I've just talked to GoDaddy (my host) and asked them for a copy of my apache error logs, and their response was " what do you what sir... ?" we don't have any logs that we can give out. They suggested if it happens again to give them a call with the error message.

The site seams to work now, My question is is there any other way to fix the issue ? or any other suggestions

Thank you

www.TechFeed.ca | Your Daily Technology Feed Source

This is what I did on my own

rseiser commented 5 June 2007 at 02:34

This is what I did on my own localhost to display the error message on the screen. In the file php.ini I changed from "display_errors = Off" to "display_errors = On". But yes, I checked my Apache\logs\error.log now and also do see the mentioned errors there. So I agree this might be the cleaner, albeit slower way to show and solve the errors. Of course, on a hosted server you might not have all these options to change your settings, unless you have local files that override the server settings. So my solution is more for my installation at home where I just test my programming.