2012/5/10 Frank Lanitz <frank.lan...@uni-jena.de> > Am 10.05.2012 13:29, schrieb Nico Kadel-Garcia: > > Interrupting an RPM or yum operation in mid-stream can cause interesting > > problems. as can disk problems or overflowing the partition that has > > /var/lib/rpm on it in mid-deployment. > > > > Make sure no one is doing yum or rpm operations, and consider these > steps: > > > > rpm --rebuilddb # to rebuild the messed up database > > Unfortunately this is failing. > > # rpm -vv --rebuilddb > D: rebuilding database /var/lib/rpm into /var/lib/rpmrebuilddb.16419 > D: creating directory /var/lib/rpmrebuilddb.16419 > D: opening old database with dbapi 3 > D: opening db environment /var/lib/rpm/Packages joinenv > rpmdb: unable to join the environment > error: db4 error(11) from dbenv->open: Resource temporarily unavailable > D: opening db index /var/lib/rpm/Packages rdonly mode=0x0 > error: cannot open Packages index using db3 - Resource temporarily > unavailable (11) > D: removing directory /var/lib/rpmrebuilddb.16419 > D: May free Score board((nil)) > > Cheers, > Frank >
Can you provide your rpm and db4 versions? After a quick search I've found this: http://www.issociate.de/board/post/20046/RPM_issue_on_2.6.5.html Are you getting any error when running rpm -qa as root? (don't try that workaround in the link yet). -- Henrique "LonelySpooky" Junior