I've been building a site (ecommerce, simplenews, mailmime, and a bunch of others) on our development server. I transfered it to the live host today and imported the db. When I pulled up the site I get a white screen. We've loaded up sites on this host before without a problem, so there is some strange thing going on with this new site.
I really don't want to rebuild the site from scratch on the host. It'll take days.
So, is there some way I can debug this? See exactly where it's failing? The hosts errors logs show nothing.
I tried some insert "echo" commands here and there to do some rudimentary tracing. It's failing when "print theme('page', $return);" is called in index.php. I sprinkled some echos in phptemplate.engine but I became overwhelmed because I don't know exactly how the functions get called, in what order, etc.
Any help would be appreciated.
If you are getting a white screen of death on all pages, it may be a memory limit. Is this site more complex than the others? More modules loaded?
Try inserting this in your settings.php file
ini_set('memory_limit', '12M');
Increase the number until it works (or you hit the maximum set by your host)
Also, you might try disabling all your modules and turn off clean URLs before you export the db from your development server. Then try turning on the modules one at a time, to see if a problem occurs.
Greg
________________________________
From: support-bounces@drupal.org [mailto:support-bounces@drupal.org] On Behalf Of John Barreiros Sent: Thursday, August 23, 2007 6:43 PM To: support@drupal.org Subject: [support] white screen of death
I've been building a site (ecommerce, simplenews, mailmime, and a bunch of others) on our development server. I transfered it to the live host today and imported the db. When I pulled up the site I get a white screen.
We've loaded up sites on this host before without a problem, so there is some strange thing going on with this new site.
I really don't want to rebuild the site from scratch on the host. It'll take days.
So, is there some way I can debug this? See exactly where it's failing? The hosts errors logs show nothing.
I tried some insert "echo" commands here and there to do some rudimentary tracing. It's failing when "print theme('page', $return);" is called in index.php. I sprinkled some echos in phptemplate.engine but I became overwhelmed because I don't know exactly how the functions get called, in what order, etc.
Any help would be appreciated.
Quoting Greg Holsclaw Greg.Holsclaw@trouvemedia.com:
If you are getting a white screen of death on all pages, it may be a memory limit. Is this site more complex than the others? More modules loaded?
Try inserting this in your settings.php file
ini_set('memory_limit', '12M');
You may want (well I would anyway) to put the following in your .htaccess file rather than modifying your settings.php file.
php_value memory_limit 12M
Earnie -- http://for-my-kids.com/ -- http://give-me-an-offer.com/
On Thursday 23 August 2007 18:43:04 John Barreiros wrote:
I've been building a site (ecommerce, simplenews, mailmime, and a bunch of others) on our development server. I transfered it to the live host today and imported the db. When I pulled up the site I get a white screen. We've loaded up sites on this host before without a problem, so there is some strange thing going on with this new site.
From the Troubleshooting FAQ handbook: http://drupal.org/node/158043
John Barreiros wrote:
I've been building a site (ecommerce, simplenews, mailmime, and a bunch of others) on our development server. I transfered it to the live host today and imported the db. When I pulled up the site I get a white screen.
We've loaded up sites on this host before without a problem, so there is some strange thing going on with this new site.
I really don't want to rebuild the site from scratch on the host. It'll take days.
So, is there some way I can debug this? See exactly where it's failing? The hosts errors logs show nothing.
I tried some insert "echo" commands here and there to do some rudimentary tracing. It's failing when "print theme('page', $return);" is called in index.php. I sprinkled some echos in phptemplate.engine but I became overwhelmed because I don't know exactly how the functions get called, in what order, etc.
Any help would be appreciated.
Check your webserver error log.
Thanks for the suggestions all. My host actually has the memory limit set to 32M. I increased to 50M, but still nothing.
I tried the suggestions from the handbook page, nada.
I also tried switching to the garland theme, turning off friendly urls, and turning off all modules. nada
I looked at the error log, but it didn't tell me anything useful.
next I created the db from scratch. This made the site show up. Then I turned on every module on one by one. The site is still showing. It looks like I have no choice but to rebuild the entire site. I'll be honest, this really blows.
On 8/24/07, Eric Mckenna eric.mckenna@gmail.com wrote:
John Barreiros wrote:
I've been building a site (ecommerce, simplenews, mailmime, and a bunch of others) on our development server. I transfered it to the live host today and imported the db. When I pulled up the site I get a white screen.
We've loaded up sites on this host before without a problem, so there is some strange thing going on with this new site.
I really don't want to rebuild the site from scratch on the host. It'll take days.
So, is there some way I can debug this? See exactly where it's failing? The hosts errors logs show nothing.
I tried some insert "echo" commands here and there to do some rudimentary tracing. It's failing when "print theme('page', $return);" is called in index.php. I sprinkled some echos in phptemplate.engine but I became overwhelmed because I don't know exactly how the functions get called, in what order, etc.
Any help would be appreciated.
Check your webserver error log.
[ Drupal support list | http://lists.drupal.org/ ]
Well, if you have the patience, I would try re-importing the tables one by one. This will at least allow you to find where the issue is. And then you only have to recreate that portion of the site (or fix the issue if discernable).
-G
________________________________
From: support-bounces@drupal.org [mailto:support-bounces@drupal.org] On Behalf Of John Barreiros Sent: Friday, August 24, 2007 9:16 AM To: support@drupal.org Subject: Re: [support] white screen of death
Thanks for the suggestions all.
My host actually has the memory limit set to 32M. I increased to 50M, but still nothing.
I tried the suggestions from the handbook page, nada.
I also tried switching to the garland theme, turning off friendly urls, and turning off all modules. nada
I looked at the error log, but it didn't tell me anything useful.
next I created the db from scratch. This made the site show up. Then I turned on every module on one by one. The site is still showing. It looks like I have no choice but to rebuild the entire site. I'll be honest, this really blows.
On 8/24/07, Eric Mckenna eric.mckenna@gmail.com wrote:
John Barreiros wrote:
I've been building a site (ecommerce, simplenews, mailmime, and a bunch of others) on our development server. I transfered it to the live host today and imported the db. When I pulled up the site I get a
white screen.
We've loaded up sites on this host before without a problem, so there is some strange thing going on with this new site.
I really don't want to rebuild the site from scratch on the host. It'll take days.
So, is there some way I can debug this? See exactly where it's failing? The hosts errors logs show nothing.
I tried some insert "echo" commands here and there to do some rudimentary tracing. It's failing when "print theme('page', $return);" is called in index.php. I sprinkled some echos in phptemplate.engine but I became overwhelmed because I don't know exactly how the functions get called, in what order, etc.
Any help would be appreciated.
Check your webserver error log. -- [ Drupal support list | http://lists.drupal.org/ ]
You might try directly examining the watchdog table to see if there are errors there, using PHP Myadmin or some such tool.
also you could hard code in your theme some PHP error set directives.
I think there must be erros that you aren't seeing - something like:
Dave
________________________________
From: support-bounces@drupal.org [mailto:support-bounces@drupal.org] On Behalf Of John Barreiros Sent: Friday, August 24, 2007 9:16 AM To: support@drupal.org Subject: Re: [support] white screen of death
Thanks for the suggestions all.
My host actually has the memory limit set to 32M. I increased to 50M, but still nothing.
I tried the suggestions from the handbook page, nada.
I also tried switching to the garland theme, turning off friendly urls, and turning off all modules. nada
I looked at the error log, but it didn't tell me anything useful.
next I created the db from scratch. This made the site show up. Then I turned on every module on one by one. The site is still showing. It looks like I have no choice but to rebuild the entire site. I'll be honest, this really blows.
On 8/24/07, Eric Mckenna eric.mckenna@gmail.com wrote:
John Barreiros wrote: > I've been building a site (ecommerce, simplenews, mailmime, and a > bunch of others) on our development server. I transfered it to the > live host today and imported the db. When I pulled up the site I get a > white screen. > > We've loaded up sites on this host before without a problem, so there > is some strange thing going on with this new site. > > I really don't want to rebuild the site from scratch on the host. > It'll take days. > > So, is there some way I can debug this? See exactly where it's > failing? The hosts errors logs show nothing. > > I tried some insert "echo" commands here and there to do some > rudimentary tracing. It's failing when "print theme('page', $return);" > is called in index.php. I sprinkled some echos in phptemplate.engine > but I became overwhelmed because I don't know exactly how the > functions get called, in what order, etc. > > Any help would be appreciated. Check your webserver error log. -- [ Drupal support list | http://lists.drupal.org/ ]
On Friday 24 August 2007 09:15:37 John Barreiros wrote:
Thanks for the suggestions all. My host actually has the memory limit set to 32M. I increased to 50M, but still nothing.
I tried the suggestions from the handbook page, nada.
I also tried switching to the garland theme, turning off friendly urls, and turning off all modules. nada
I looked at the error log, but it didn't tell me anything useful.
next I created the db from scratch. This made the site show up. Then I turned on every module on one by one. The site is still showing. It looks like I have no choice but to rebuild the entire site. I'll be honest, this really blows.
You might try it from the other direction and disabling modules on the production site. You can move the modules out of the sites directory one-by-one or all at once to see if your site comes back. I would probably start with a database back up, then by moving the e-commerce modules, since there's so much code there.
Another thing to consider is potentially errant PHP code in a block or node that might be causing the problem. I've done that enough times to look for it as an option.
so I tried removing my all/modules and all/themes folder and I get an access denied message. If I bring back all my modules I'm suddenly able to see an unthemed homepage.
okay, this is really strange.
So, I uploaded the full database again, with no modifications. I removed my all/themes folder and now I'm able to see an unthemed homepage. If I try to access any other pages, I get the WSOD.
Now, if I switch my theme to garland and upload that version of the db (and my all/themes folder removed) I get the WSOD.
On 8/24/07, Jason Flatt drupal@oadaeh.net wrote:
On Friday 24 August 2007 09:15:37 John Barreiros wrote:
Thanks for the suggestions all. My host actually has the memory limit set to 32M. I increased to 50M,
but
still nothing.
I tried the suggestions from the handbook page, nada.
I also tried switching to the garland theme, turning off friendly urls,
and
turning off all modules. nada
I looked at the error log, but it didn't tell me anything useful.
next I created the db from scratch. This made the site show up. Then I turned on every module on one by one. The site is still showing. It
looks
like I have no choice but to rebuild the entire site. I'll be honest,
this
really blows.
You might try it from the other direction and disabling modules on the production site. You can move the modules out of the sites directory one-by-one or all at once to see if your site comes back. I would probably
start with a database back up, then by moving the e-commerce modules, since there's so much code there.
Another thing to consider is potentially errant PHP code in a block or node that might be causing the problem. I've done that enough times to look for it as an option.
-- Jason Flatt http://www.oadaeh.net/ Father of Six: http://www.flattfamily.com/ (Joseph, 14; Cramer, 12; Travis, 10; Angela; Harry, 7; and William, 12:04 am, 12-29-2005) Linux User: http://www.xubuntu.org/ Drupal Fanatic: http://drupal.org/ -- [ Drupal support list | http://lists.drupal.org/ ]
On 8/24/07, John Barreiros johnbarreiros2@gmail.com wrote:
so I tried removing my all/modules and all/themes folder and I get an access denied message. If I bring back all my modules I'm suddenly able to see an unthemed homepage.
okay, this is really strange.
So, I uploaded the full database again, with no modifications. I removed my all/themes folder and now I'm able to see an unthemed homepage. If I try to access any other pages, I get the WSOD.
Now, if I switch my theme to garland and upload that version of the db (and my all/themes folder removed) I get the WSOD.
Do the internal paths look right when you hover over the unthemed homepage? Are the paths right in the WSODs? I guess you have already checked the .htaccess file. Any php code in blocks or nodes for which a different PHP version would matter?
Quoting John Barreiros johnbarreiros2@gmail.com:
Thanks for the suggestions all. My host actually has the memory limit set to 32M. I increased to 50M, but still nothing.
I tried the suggestions from the handbook page, nada.
I also tried switching to the garland theme, turning off friendly urls, and turning off all modules. nada
I looked at the error log, but it didn't tell me anything useful.
I forget what all you've tried so if you've done this already please forgive me.
First empty the cache tables in the DB. Also the sessions table.
If that doesn't help try turning on PHP's display_errors variable, you can do this from .htaccess ``php_value display_errors 1''; however, you may need to do it in php.ini.
Earnie -- http://for-my-kids.com/ -- http://give-me-an-offer.com/
-
Cog Rusty -
Earnie Boyd -
Eric Mckenna -
Greg Holsclaw -
Jason Flatt -
John Barreiros -
Metzler, David