RPM out of locker what now?!

July 12, 2007 - 12:00 pm

rpmdb: Lock table is out of available locker entries

What is this, and why is it suggestiong you install bash for an rpm that does not require it - especially considering you have bash installed already?

It's very simple: Your RPM DB is completely borked; good luck installing packages now.

You're doomed. Doomed! DoOOoOOoOomed! It's almost 5 AM, and you need to get stuff working! What will you do?! Oh, crap.

Chances are, no matter how bad this might look, you've only got simple corruption. Sure, simple corruption of the RPM DB means 'completely borked', but simple corruption also means, 'easily fixed'. Here's what you want to do:

First, for the love of Bob, take a backup of the existing DB. If you manage to break things more, you want to be able to restore it to a point of slightly less broken, so you can always blame someone else for the original state you found things in:

# cd /var/lib
# tar czvf /tmp/rpmdb.tar.gz rpm

Once you've done that, it's time for the main event. Don't go and get some popcorn, because this is fairly quick:

# rpm -vv --rebuilddb

Run this and it'll rebuild your rpm database with terminal verbosity. To test, just run yum or up2date or manually attempt to rpm -ivh something, and it should act normally again.