White Screen of death when visiting nodes with comments
bflora - January 13, 2009 - 23:02
I'm getting the worst error ever.
When you visit a node with a comment on it. You get the white screen of death.
There's no error logged in my php error log.
There's no error logged in Drupal's error log.
When we turned on error reporting in htaccess, it still didn't show us anything.
So I'm getting the white screen of death when I visit a node with comments.
I emptied the comments.tpl.php file. I'm still getting the error.
The only thing that's helped so far is completely disabling the comments module.
Surely that can't be the only solution!
I've been Drupaling for almost a year now. I thought I'd seen everything. But this...I have no idea what this could be.
Suggestions? How can I get help?
=-=
white screen can be apache errors, have you checked you apache error logs?
have you tried viewing the source of the blank page? is there any source code at all?
Good calls. I checked the
Good calls.
I checked the source of the white screen. Nothing in the source.
I checked my apache error log. There are errors, but none that sync up with getting these white screens every 5 minutes when I visit the page.
The site in question is http://www.windycitizen.com
and here's a URL for you to try:
http://www.windycitizen.com/link/politicscity-news/2009/01/city-to-close...
=-=
I checked the site, loaded multiple pages. Played around for a few mins. Not once did I get a white screen.
This link tho: http://www.windycitizen.com/link/politicscity-news/2009/01/city-to-close...
gives me a server error.
Ok. That sounds
Ok. That sounds helpful.
What does that mean? What's the difference?
Why would some pages return a server error while others don't?
=-=
http://www.windycitizen.com/link/politicscity-news/2009/01/city-to-close...
gives the same server error. Looks to me like you are using drigg?
yes I am using Drigg. Could
yes I am using Drigg. Could that be involved somehow? A "short" in the Drigg code?
Problem = FIXED. My sysadmin
Problem = FIXED.
My sysadmin and I reloaded apache. Everything works now.
Man, that was awful.
quick solution, but hardly fixed
I had the same problem, drupal 5.7 (I know, needs an upgrade). All of a sudden one night, blank screen on all nodes with comments. It took a while just to figure that part out. Disabling the comments module worked but we want comments. Read here that an apache restart solved the problem, and it did for me also: I reenabled the comments module, got the blank screen, reloaded apache, page was fine with comments. So there's no problem currently, but what caused this, and how do I prevent it from happening again?
I don't think I've ever before seen a php code problem that could be fixed with an apache restart, it's not a reassuring solution. Anyone?
same issue?
I believe this is the same issue, they are tracing the problem to the use of the comments module with eaccelerator php cache:
http://drupal.org/node/220316
Also see this article regarding segfaults and php op-code caches:
http://2bits.com/articles/php-op-code-caches-accelerators-a-must-for-a-l...
which seems to suggest you have to choose between no php cache or segfaults, take your poison. Restarting apache is the only remedy discussed for the segfaults, but they suggest a script solution to automatically restart apache when the segfault problem is detected in the logs:
http://2bits.com/articles/logwatcher-restart-apache-after-a-segmentation...
some nice options, from pure bash scripts to sh/php combos, started from init. Still a bit of a hack, but this can solve your problems.
There's some talk of a script that will clear the code from the php cache that's causing the segfault, but I think this is a little more complex and no one has tried to implement it.