I've been down for 24 hours with the following error at Dreamhost resulting from their upgrade to PHP 5.2:
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, webmaster@openplanner.org and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.
I'm running Drupal 4.7.6 on my production site (down with above error).
Interestingly enough, I've got test sites running Drupal 4.7.4 and 5.0 and both are running fine, whereas my test site with Drupal 4.7.5 is also down.
Yes I've already tried deleting the .htaccess file and specific override commands within it suggested in Drupal forums.
My error log gives many of these errors: Premature end of script headers: /dh/cgi-system/php5.cgi
Comments
They have info on how to get
They have info on how to get running again.
http://www.dreamhoststatus.com/2007/02/08/php5-downgrade-completeupgrade...
Thanks but this isn't the issue
Yeah...I went down those links too....
My problem isn't the login issue...it's the 500 internal configuration error... both of those links don't relate.
Thanks for the pointer nonetheless!
php4
I suggest you downgrade to php4 until this has been more clearly sorted out. That solved it for me.
--
Knaddison Family | mmm Free Range Burritos
--
Morris Animal Foundation
Not solving it
I downgraded, didn't solve my problem
In my case it was the Textile module
I changed the name of the Textile module directory and the site came right back up. So it's maybe a module.
It's still a real drag for me but I know what's going on.
--Chick Foxgrover
Are you using Devel?
If so, delete it (not just disable), then delete all the system variables that it set. Devel and PHP5 don't play well together.
Nancy W.
Drupal Cookbook (for New Drupallers)
Adding Hidden Design or How To notes in your database
NancyDru
pretty broad
Saying devel and php5 don't work together is way too broad. They work together fine on many hosts. It's a very specific combination of devel settings and php5 with zend optimizer that causes a complete 500.
Unless you have other issues with Devel and php5. And in that case, can you provide links to the issues? I'd be happy to test them.
--
Knaddisons Denver Life | mmm Free Range Burritos
--
Morris Animal Foundation
Just going by the many posts
Just going by the many posts that I've read. It mostly works for me on my test site.
Nancy W.
Drupal Cookbook (for New Drupallers)
Adding Hidden Design or How To notes in your database
NancyDru
.htaccess
if you take your .htaccess file out do you still get the 500 error? I've had similar issues where the host made an upgrade that caused my .htaccess to no longer be compatible with the server.
If that fixes the 500 error (your drupal site will still be broken until you replace/fix it) you can at least go thru the .htaccess and comment things out until you find what's causing it. It's a place to start anyway.
it didnt work out - here is how I got over the problem
I did a few things, including reading your good comments & advice. Fortunately I was not too far into development so I could afford to start from scratch again.
tried opening up perms
tried removing .htaccess
tried disabling modules such as devel, by removing them
checked my symbolic links for proper references
removed CVS files, since my copy of drupal was grabbed from the cvs tree.
all that and no change in my site, still the crazy error. My good friend told me she also had DH problems with drupal grabbed from cvs.
I didnt bother at this point to try and checkout from the drupal cvs tree into the DH site to see if it worked.
Its surprising that nothing I have found from researching actually solved this problem.
I did my due dilligence looking around, but then decided to get on with life and start over. So I said to heck with it and started with a fresh tarball of drupal.
Back up all your old stuff - its the golden rule.
dump your old db, and either empty your db of tables or build a new site with a new table prefix.
Backup your site files elsewhere.
Start with a fresh copy of Drupal in a new db or with table prefixes. This worked.
Try commenting out the table prefix in settings to look at the result to see if it works. I had broken theme.
If you have opted for table prefixes, you might try swapping out your new tables for your old, to see what happens.
You could do queries of the old tables and save to the new tables with insert_node(), and a bit of php hacking.
It would be nice if somebody actually posted the solution to this problem. I should not have to do this, but I did. I only have so much time to agonize over these irrelevant little problems of hosts who stop people like us in our tracks and then leave us twisting in the wind.
Its a shame to have restarted from scratch again, and I know that is not everybody's option. But I dont have a problem anymore. Ill be developing on this new install.
cheers,
PG
This posting on the Drupal.org forum is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.