Solve the rpmdb: Lock table is out of available locker entries Problem

Solve the rpmdb: Lock table is out of available locker entries problem. If you run some programs, the remote yum command "rpmdb: Lock table is out of available locker entries... you can follow the steps below to fix the problem: www.2cto.com: rpmdb: Lock table is out of available locker entrieserror: db4 error (22) from db-> close: Invalid argumenterror: cannot open Packages index using db3-Cannot allocate memory (12) error: cannot open Packages database in/var/lib/ Before rpm operations, back up/var/lib/rpm: tar cvzf rpmdb-backup.tar.gz/var/lib/rpm to remove the BDB database used by rpm: rm/var/lib/rpm/_ db.00 * re-create the rpm database. Note: it may take some time: rpm -- rebuilddb check now to see if the rpm package is normal: why does rpm-qa | sort cause this problem? In fact, when you use the rpm command, the rpm will first set a temporary lock to access the BDB database. If you use control-c to interrupt it when it is running, or send an interruption signal to it. Then, rpm may cause errors. This temporary lock has not been released yet. Find the cause and you can find other solutions. Rpmdb: Lock table is out of available locker entries05.27.2007 | Author: major | Posted in PostsIf up2date throws some horrible Python errors and rpm says "rpmdb: lock table is out of available locker entries ", you can restore your system to normality with the fol Lowing: The errors: [html] rpmdb: Lock table is out of available locker entries error: db4 error (22) from db-> close: Invalid argument error: cannot open Packages index using db3-Cannot allocate memory (12) error: cannot open Packages database in/var/lib/rpm Make a backup of/var/lib/rpm in case you break something: [html] tar cvzf Co., rpmdb-backup.tar.gz/var/lib/rpm Remove the Berkeley databases th At rpm uses: www.2cto.com [html] rm/var/lib/rpm/_ db.00 * Make rpm rebuild the databases from scratch (may take a short while ): [html] rpm -- rebuilddb Now, check rpm to make sure everything is okay: [html] rpm-qa | sort Why does this happen? When rpm accesses the Berkeley database files, it makes temporary locker entries within the tables while it searches for data. if you control-c your rpm processes often, this issue will occur much sooner because the locks are never cleared. update: As of February 2009, this post was Ed five times the visits of my next most popular post. this situation must happen very often!