What on earth is going on? I wish someone could explain to me in good order… because I’ve never seen so many problems all in one day.

I’ve getting lots of help but I’m still struggling to figure out the source of the problem, and hence the solution.

I’ve had five serious problems in the last 24 hours.

1.- Unable to reboot…

Yesterday my webserver went down, couldn’t bring it back up. When it did come back, some sites were absolutely fine… but some were totally screwed up.

So I’m trying to find out what if any updates DH made to the server that would cause these two kinds of problems:

#2: Erroneous Codes
this is being generated by the plugin wp-cache (yesterday the plugin was working without any problems!) I tried removing the plugin and reinstalling: didn’t work. Just produced the same errors even after removing it from the plugins directory…

Warning: fopen(/home/.damper/obblogatory/obblogatory.com/wp-content/cache/wp_cache_mutex. lock) [function.fopen]: failed to open stream: No such file or directory in /home/.damper/obblogatory/obblogatory.com/wp-content/plugins/wp-cache/wp-cache-p hase2.php on line 96
Couldn’t write to: /home/.damper/obblogatory/obblogatory.com/wp-content/cache/wp-cache-357509ba2733 b5ed2b4e72148985cc17.html
Warning: flock() expects parameter 1 to be resource, boolean given in /home/.damper/obblogatory/obblogatory.com/wp-content/plugins/wp-cache/wp-cache-p hase2.php on line 105

Warning: fopen(/home/.damper/obblogatory/obblogatory.com/wp-content/cache/wp-cache-357509 ba2733b5ed2b4e72148985cc17.meta) [function.fopen]: failed to open stream: No such file or directory in /home/.damper/obblogatory/obblogatory.com/wp-content/plugins/wp-cache/wp-cache-p hase2.php on line 240

Warning: fputs(): supplied argument is not a valid stream resource in /home/.damper/obblogatory/obblogatory.com/wp-content/plugins/wp-cache/wp-cache-p hase2.php on line 241

Warning: fclose(): supplied argument is not a valid stream resource in /home/.damper/obblogatory/obblogatory.com/wp-content/plugins/wp-cache/wp-cache-p hase2.php on line 242

Warning: flock() expects parameter 1 to be resource, boolean given in /home/.damper/obblogatory/obblogatory.com/wp-content/plugins/wp-cache/wp-cache-p hase2.php on line 114

#3: I’m still getting this error on at least three sites…

Warning: require_once(/home/.damper/eeeblogger/eeeblogger.com/wp-config.php) [function.require-once]: failed to open stream: Permission denied in /home/.damper/eeeblogger/eeeblogger.com/wp-load.php on line 27

Fatal error: require_once() [function.require]: Failed opening
required ‘/home/.damper/eeeblogger/eeeblogger.com/wp-config.php’ (include_path=’.:/usr/local/php5/lib/php:/usr/local/lib/php’) in /home/.damper/eeeblogger/eeeblogger.com/wp-load.php on line 27

What’s even odder is that they are all supposed to be running on the same server, all of them are running WP2.7 as you requested, and most of them have the SAME plugins or broadly similar ones.

#4: FTP is shutout

All the passwords for my FTP accounts were non functional until I reset them. I still can’t login via FTP to most of my accounts UNLESS I set them to Shell access. They were working before that’s for sure. And no one else has Shell access.

#5 A lot of permissions have been reset making errors for some blogs that I can’t fix EVEN IF I reset the folder permissions.

I am thinking that one of two possibilities happened: an update was roled out with unexpected consequences in some cases or that the server became corrupted (by accident or by hacker?) and this means some sites are just dandy while others are out.

I spoke extensively with DanielG who helped me get the passwords reset and saved me from tearing my hair out. But we’re still no nearer on what happened and how to fix the situation. Kudos to DanielG for his effort…

Please can you help me sort this mess out.

Best Wishes
Kenneth

These problems have had me spend hours trying to trouble shoot the origin of the problems. It’s really prevented me from running my sites, doing maintenance or getting posts done. Very frustrating, what is it with DreamHost? Things were going well, but things are just so seriously screwed up…