Hi; I deleted the rpm db files. I then ran yum update again. Seems to go fine for quite awhile and then... ... Running Transaction ^M Updating : libxml2 ##################### [ 1/719]rpmd b: page 586: illegal page type or format rpmdb: PANIC: Invalid argument error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting ")�ë��^L]�[7m^F^A" records from Filemd5s index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "ĉ&1m��[7m^L^A:�[7m^A" records from Filemd5s index rpmdb: PANIC: fatal region error detected; run recovery ... What to do now? Is libxml2 package corrupt? I have a 333MHz CPU, 230Mb RAM and 12gb disk -- I'm experimenting with the entire FC6...is this too much FC6 for this machine? :-) Thanks, Ken Thanks, Ken <div>On 1/22/07, Kenneth Wolcott <<a href="mailto:kennethwolcott@gmail.com"> kennethwolcott@gmail.com</a>> wrote:<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi; I had already rebooted and the error I reported still exists prior to sending this email. I subsequently deleted the rpm db files and am now doing the yum update. Thanks, Ken<div> <div> On 1/22/07, alan <<a href="mailto:alan@clueserver.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">alan@clueserver.org</a>> wrote:<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> On Mon, 22 Jan 2007, Amitakhya Phukan wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Kenneth Wolcott wrote: >> Hi; >> >> I have a corrupt FC6 rpmdb after a timed-out yum update; >> >> attempt to rebuild fails: >> >> rpm --rebuilddb fails: >> >> rpmdb: PANIC: fatal region error detected; run recovery >> error: db4 error(-30977) from dbenv->open: DB_RUNRECOVERY: Fatal >> error, run database recovery >> error: cannot open Packages index using db3 - (-30977) >> >> How to repair the rpm db? >> >> Thanks, >> Ken Wolcott > > Hi ! > > I face the same problem sometimes. I do rm -rf /var/lib/rpm/__db* > > after that yum update/install and then yum clean all > > then the occurrence frequency of the above decreases. > > the best way is pirut/pup i guess. Actually this is a different problem. There is a known bug where the rpm database gets locked and will not release. The quick solution is to reboot the machine and the lock will release. I do not know how to get it to release "properly". There is a bugzilla report on this, but it is too early in the morning for me to look it up. -- "Invoking the supernatural can explain anything, and hence explains nothing." - University of Utah bioengineering professor Gregory Clark -- fedora-list mailing list <a href="mailto:fedora-list@redhat.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)"> fedora-list@redhat.com</a> To unsubscribe: <a href="https://www.redhat.com/mailman/listinfo/fedora-list" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)"> https://www.redhat.com/mailman/listinfo/fedora-list</a> </blockquote></div> </div></blockquote></div>