OpenID plugin borkage

My blog was down for much of the morning, and after contacting Dreamhost tech support ninjas, they told me that my account was sucking the RAM out of the server, and that wasn’t cool. They gave some tips on how to reduce memory usage (didn’t work), and then I rolled up my sleeves to debug my WordPress site to see wtf was going on.

I started by SSHing into the server, and moving my wp-content/plugins out of the way and creating a new, empty plugins directory.

mv wp-content/plugins wp-content/plugins-dis
mkdir wp-content/plugins
cd wp-content/plugins-dis

Then, I reloaded the blog in a browser, and it worked! Aha! Something wonky with a plugin. So… To debug with plugin was the culprit…

I started having flashbacks to debugging MacOS 7/8/9 systems, where you got to reboot a dozen times, each with a different set of control panels/extensions enabled, until you figured out which one was borking the system. Same thing here, but with plugins. I moved them back into the active plugins directory, one at a time, until it borked again. Something like Conflict Catcher might be handy here…

mv plugin-1 ../plugins/
(reload browser)
mv plugin-2 ../plugins/
(reload browser)

Looks like the OpenID plugin I use, which allows folks to leave comments using their OpenID credentials, started borking my blog for some reason. I’ve been using that plugin for several weeks (months?) with no problems, but now, it reliably kills my blog. Frack.

For now, I’ve disabled the OpenID plugin I had been using, and am trying out a different one to see if/how it works out. Simple OpenID is now enabled.

Update: I had to disable Simple OpenID as well. It was borking violently on comment submissions. If only OpenID was integrated into WordPress, as it has been for Drupal 6…

7 thoughts on “OpenID plugin borkage”

  1. D’Arcy, thanks for this post, both for the info that the OpenID plugin was the culprit (I was about to install it this weekend) but also the description of the process you followed which was handy to read. I agree 100% – WP should just support OpenID out of the box.

  2. Agreeing with Scott- I had looked at a few of the openId pliugins. They seem to offer less value on a blog comment- once you’ve generally posted something acceptable, it is a different aspect of “logging” in- I have liked the openID integration with some of the wiki and other 2.0 sites

  3. I’m not sure whether it’s a problem with the plugin, or with Dreamhost. It worked for several weeks just fine, and all of a sudden just borked. I’ve got a sneaky suspicion that something’s been changed on the server, which is now interacting with the openid authentication plugin…

  4. D’Arcy,

    I saw your Twitter about Fast CGI on Dreamhost. Does it make your sites any … um … faster? I have a slow Elgg site on Dreamhost that I would love to speed up, and I suspect that shared mySQL hosting has something to do with the problem. Thanks.


  5. @Richard: I’m really not sure. I’ve also enabled WP-Cache, which is a module that uses filesystem caching to reduce PHP and MySQL loads. As a result, I’m not sure how much of the gain is from WP-Cache, and how much is from FastCGI… The page generation time at the bottom of this page says it took 4 seconds to spit out – so I’d guess most of the boost is from caching rather than FastCGI…

  6. D’Arcy-
    Could Dreamhost have changed your WP install? I’ve been having a wicked bad time with 2.2.1- can’t seem to get the WYSIWG editor to work- and have to keep backgrading to 2.1.3
    Don’t know what’s causing your issues- but if you didn’t change it- someone did.

  7. RE FastCGI — php runs faster when it is installed as an apache module —

    RE Dreamhost in general: I have found that php based apps seem to run a little more slowly on Dreamhost than on other shared hosting providers. While I haven’t benchmarked sites yet (and probably never will, unless a client specifically requests this), I have been pretty underwhelmed by what I’ve seen from Dreamhost.



Comments are closed.