[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

database corrupted



Well, it looks like I've been an idiot.  I hope someone can help me fix my 
problem.  I recently upgraded rpm from V3.0.4 to 4.0.2.  In the process I 
forgot to run the command "rpm --rebuilddb".  After I upgraded rpm, I was 
installing some packages and received a segmentation fault after a package 
was installed.  Now whenever I attempt to run "rpm --rebuilddb" I get a 
segmentation fault.  I can run a "rpm -qa" and it will fault just before it 
lists the package the gave me the original segmentation fault.  How can I fix 
the corrupted database?  I neglected to save a backup of the rpm database 
before I upgraded to 4.0.2.

Some particulars:  I'm running RedHat Linux 6.2.  I installed the db3 V3.1.17 
rpms and the rpm 4.0.2 rpms.  I didn't run "rpm --rebuilddb" before I started 
installing the other packages.  The other packages were upgraded kernel rpms 
(V2.2.19-6.2.7).  Everything went fine until I decided I needed to install 
the kernel sources.  When I installed the kernel sources, rpm acted as if it 
had installed correctly (the status bar went all the way to the end) then I 
got a segmentation fault.

Any help would be greatly appreciated.  As it stands right now, I am unable 
to install or examine any other packages.  Please let me know if I need to 
reinitialize the database and start over from scratch.





[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index] []