I installed CentOS 3.4 from a CD image I'd burned a while ago, and then attempted to update with yum to 3.7. All the packages installed OK, but at the very end of final cleanup I got an error message from db4 saying to "RUN RECOVERY". I did "rpm --rebuilddb" which may have been the wrong thing -- it issued an error about "pages missing". I then ran it again, and it came back with no errors, but after rebooting (for the kernel update) "rpm -qa" lists only a dozen packages or so, of which "rpm" is not one, and "yum check-update" chokes, showing Null for $releasever and the empty string for $basearch. This was a brand-new system, so I'm thinking I'll just download the 3.7 ISOs and re-install, but on the off chance there's some other way to recover from this I thought I'd ask. There doesn't seem to be anything missing other than a large chunk of the RPM database itself.
On Thu, 2006-07-06 at 17:40 -0700, Bart Schaefer wrote:> I installed CentOS 3.4 from a CD image I'd burned a while ago, and > then attempted to update with yum to 3.7.I have done the exact thing form 3.4 to 3.7 w/out issue. Not sure what caused it in this case.> All the packages installed > OK, but at the very end of final cleanup I got an error message from > db4 saying to "RUN RECOVERY". > > I did "rpm --rebuilddb" which may have been the wrong thing -- it > issued an error about "pages missing". I then ran it again, and it > came back with no errors, but after rebooting (for the kernel update) > "rpm -qa" lists only a dozen packages or so, of which "rpm" is not > one, and "yum check-update" chokes, showing Null for $releasever and > the empty string for $basearch.I would try reinstalling CentOS-release and see how that goes.> > This was a brand-new system, so I'm thinking I'll just download the > 3.7 ISOs and re-install, but on the off chance there's some other way > to recover from this I thought I'd ask. There doesn't seem to be > anything missing other than a large chunk of the RPM database itself.You can try rebuilding the database again ... and then if there are any other issues, I would just reinstall 3.7. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: <http://lists.centos.org/pipermail/centos/attachments/20060707/88e59c43/attachment-0002.sig>
On Thu, Jul 06, 2006 at 05:40:10PM -0700, Bart Schaefer enlightened us:> I installed CentOS 3.4 from a CD image I'd burned a while ago, and > then attempted to update with yum to 3.7. All the packages installed > OK, but at the very end of final cleanup I got an error message from > db4 saying to "RUN RECOVERY". > > I did "rpm --rebuilddb" which may have been the wrong thing -- it > issued an error about "pages missing". I then ran it again, and it > came back with no errors, but after rebooting (for the kernel update) > "rpm -qa" lists only a dozen packages or so, of which "rpm" is not > one, and "yum check-update" chokes, showing Null for $releasever and > the empty string for $basearch. > > This was a brand-new system, so I'm thinking I'll just download the > 3.7 ISOs and re-install, but on the off chance there's some other way > to recover from this I thought I'd ask. There doesn't seem to be > anything missing other than a large chunk of the RPM database itself.Coincidentally, there is a thread regarding this happening right now over on the nahant mailing list: https://www.redhat.com/archives/nahant-list/2006-July/msg00011.html Matt -- Matt Hyclak Department of Mathematics Department of Social Work Ohio University (740) 593-1263
On Thu, 6 Jul 2006, Bart Schaefer wrote:> I installed CentOS 3.4 from a CD image I'd burned a while ago, and > then attempted to update with yum to 3.7. All the packages installed > OK, but at the very end of final cleanup I got an error message from > db4 saying to "RUN RECOVERY". > > I did "rpm --rebuilddb" which may have been the wrong thing -- it > issued an error about "pages missing". I then ran it again, and it > came back with no errors, but after rebooting (for the kernel update) > "rpm -qa" lists only a dozen packages or so, of which "rpm" is not > one, and "yum check-update" chokes, showing Null for $releasever and > the empty string for $basearch.Never, ever do "rpm --rebuilddb" with the __db.* files in place. First remove the __db* files then see if that fixes your problem. If you have to run "rpm --rebuilddb", make sure you remove the __db.* files first otherwise this will most likely corrupt your database (especially when the __db* files are the cause of your problems). If you happen to have cache-corruption again, always make a copy of /var/lib/rpm, because rpm in that case thinks it has fixed the problem while it made it worse and does not leave a directory behind. Kind regards, -- dag wieers, dag at wieers.com, http://dag.wieers.com/ -- [all I want is a warm bed and a kind word and unlimited power]