2012/5/10 Frank Lanitz <frank.lan...@uni-jena.de> > Am 10.05.2012 15:46, schrieb Henrique Junior: > > > > > > 2012/5/10 Frank Lanitz <frank.lan...@uni-jena.de > > <mailto: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 try this, please? > > > > # rm -f /var/lib/rpm/__db* > > > > # rpm --rebuilddb > > Looks like it did the trick. At least rpm is working again as well as > yum is doing. Thx. > > Cheers, > Frank > -- > Stabsstelle Information und Kommunikationsdienste (STI) > Friedrich-Schiller-Universität Jena > > Fürstengraben 1 > D-07743 Jena > frank.lanitz@uni-jena-de > Tel: 03641 / 9 31717 > PGP: 0xDF9CD530 > > > Glad to help.
-- Henrique "LonelySpooky" Junior