[Gllug] Broken RPM Database

[Lee, Paul]

Hi
Has anyone on the list successfully rebuilt their RPM database? I don't 
mean rpm --rebuilddb. I've tried that and that was only partially 
successful. This partly rebuilt a list of 71 packages (when the real 
number will be over 300). rpm -Va reveals a list of failed dependencies.

I had just carried out an update of my Centos 3.6 using yum when I 
discovered rpm was broken with `error: db4 error(-30989) from 
dbcursor->c_get: DB_PAGE_NOTFOUND: Requested page not found` - I think 
it might be this bug..

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=157229

yum is also broken with a Centos "null" or retrygrab() problem ie:

[root at host1 root]# yum update
Gathering header information file(s) from server(s)
Server: CentOS-Null - Addons
retrygrab() failed for:

This would doubtless be due to the fact that the centos release package 
although present is no longer in the RPM database.

cat /etc/redhat-release
CentOS release 3.6 (Final)

I can think there are ways of manually recreating or initialising the 
database again but I'm wondering if it might be just best to start from 
scratch. The system works fine - it obviously can't be updated via RPM 
at them moment!

I've never really `lost` an RPM database before, --rebuilddb usually 
doing its thing, but searching the Centos forums this would appear to be 
a very rare event. It's strange that rebuilddb is only partially 
rebuilding the list.

Any suggestions? recommendations? ;o)


Paul
-- 
Gllug mailing list  -  Gllug at gllug.org.uk
http://lists.gllug.org.uk/mailman/listinfo/gllug