Comments on: Site Down 36 Hours : How I Fixed Internal Server Errors

By: 500 Internal Server Error - How We Fixed - Wordpress - Dreamhost | ForDevs

500 Internal Server Error - How We Fixed - Wordpress - Dreamhost | ForDevs — Sun, 25 Oct 2009 15:55:32 +0000

[...] Disable the plugins.This we cant do because wordpress was installed in the root folder which made impossible to login [...]

By: security locks

security locks — Tue, 28 Jul 2009 00:09:42 +0000

fantastic web site, the internet i starved of good content like this, keep it up, the web needs it.

By: No Wordpress (Super) Cache on Dreamhost < blog@AndreiNeculau

No Wordpress (Super) Cache on Dreamhost < blog@AndreiNeculau — Thu, 01 Jan 2009 21:16:18 +0000

[...] After checking all of my plugins (of course, not checking exactly the right one) reading about it and then some more, I tried disabling my WP Super Cache plugin (it’s an enhanced version of [...]

By: Web Tech

Web Tech — Wed, 26 Nov 2008 23:16:30 +0000

I even can;t access the wp dashboard. Then I delete wp_cache_mutex.lock at wp-content/cache. And it works perfectly, thx

By: Bill

Bill — Fri, 25 Apr 2008 19:23:19 +0000

Beetlejuice – that is a different problem… blank pages is a totally different issue.

This is a new problem which has cropped up with Dreamhost (and maybe others)… and hard to believe but no solutions can be found.

This error will cause your entire blog to be down and usually will spit out ugly error messages on your home page that look something like…

blah blah wp-cache-phase2.php on line 96

By: Beetlejuice

Beetlejuice — Tue, 06 Nov 2007 04:50:44 +0000

Dreamhost have a fix for this problem in their Help pages:

1. Open /wp-content/plugins/wp-cache/wp-cache-phase2.php file* in your favourite text editor, where is the domain that you’re having troubles with EG: dreamhost.com/wp-content/plugins/wp-cache/wp-cache-phase2.php
2. Alternatively if that file is not in that location for some reason you can issue this command to find it from the directory: find . -name wp-cache-phase2.php
3. Locate the wp_cache_ob_end function
4. then inside that function find the line with: ob_end_clean(); (it should be line 219 or about)
5. and finally replace that line with: ob_end_flush();

http://wiki.dreamhost.com/WordPress#Blank_Pages

By: WP-Cache Bug Strikes Back: Site Down 17 Hours

WP-Cache Bug Strikes Back: Site Down 17 Hours — Tue, 09 Oct 2007 17:44:23 +0000

[...] the site a few hours back, it was down with internal server errors. Unlike last time when the site was down 36 hours, this time I knew what the problem was and as soon as I disabled Wp-cache, the site was instantly [...]

By: J

Fri, 07 Sep 2007 17:02:27 +0000

if your new host is godaddy then there is no fix currently because its a problem with the host.

By: videokeman

videokeman — Thu, 06 Sep 2007 17:56:07 +0000

funny i was having the same problem too with the mutex lock, i changed host was succesful to migrate everything. but when i enable wp-cahe im having the mutex lock error. has any one found a solution for this?

By: j

Tue, 04 Sep 2007 08:41:18 +0000

I have just installed WP-Cache and was happy to finally get it working. Right after i started getting 500 errors. So i knew something was up. After doing some research i found out that all people with godaddy.com have this problem and can not fix it. I tried deleting the wp_cache_mutex.lock file and all that but the problem just wont go away.

So far I’m told there is no solution. But nice post i found it on google. just thought i would leave that godaddy.com has a problem as well.