Movable Type: Berkeley DB Upgrade, Problems Logging In


In this post, I mention how my old web host had upgraded their servers without notifying me, as a customer, in advance. One simple little change caused me to be unable to log into my Movable Type administration altogether.

Apparently, this is somewhat common - but the remedy is not well known. I had to Google around and eventually found some information from Six Apart's Japanese page, but just now found a domestic knowledge base article that gives you the same information.

New server OS installations including Berkeley DB are apparently not backward compatible with older versions. For me, I had to use db_dump185 program. Unless your web hosting provider offers you shell access, you'll have to pull all of your DB files from your movable type installation, and run the the db_dump or db_dump185 program locally, and then upload the DB files back to your webserver. In either case, it's a painstaking effort. If you're good at writing a shell script or a batch file (though I didn't personally try to do this using Windows) you may want to do so.

Movable type stores your login and password information in these DB files (along with the majority of everything else that has to do with your blog). If the Berkeley DB libraries are upgraded, you won't be able to log in at all. This is why you may want to "export" your content in Movable Type from time to time, if it's just easier to do a fresh install of Movable Type. (The last time I had done an export was about five weeks ago). Otherwise, to retain your content, you'll have to go through the procedures above.