Problem with rpm database
This isn't so nice. I seem to have an error of some sort in my RPM database. Everything I run that touches the RPM database ends in a segfault. I tried a rebuild.... and this is what I got: ------- rpm --rebuilddb error: rpmdbNextIterator: skipping h# 1072 Header V3 DSA signature: BAD, key ID 87d0fc15 ------- I did a rebuild again, and it got all the way through the secodn time without errors. But.... it still didn't fix the problem. If i do soemthing as simple as... say... apt-get check... ------ apt-get check Segmentation faultsts... 64% ------ The segfault always happens at the same point... at 64%. There is nothing in the messages or warn log files to help me out. So, now what do I do? What can I do to recover my RPM database? C.
* Clayton;
This isn't so nice. I seem to have an error of some sort in my RPM database. Everything I run that touches the RPM database ends in a segfault.
I tried a rebuild.... and this is what I got:
Try rpm --initdb this will build a new database -- Togan Muftuoglu | Unofficial SuSE FAQ Maintainer | Please reply to the list; http://susefaq.sf.net | Please don't put me in TO/CC. Nisi defectum, haud refiecendum
This isn't so nice. I seem to have an error of some sort in my RPM database. Everything I run that touches the RPM database ends in a segfault.
I tried a rebuild.... and this is what I got:
Try rpm --initdb
this will build a new database
Thanks for the suggestion Togan.... I did an rpm --initdb and then a rpm --rebuilddb. That went off without a hitch. Tried an apt-get check next and still am getting a segfault at 64%. YAST isn't segfaulting now though. I was able to add an app, and romve one using YAST.... so something is still broken.... at least with apt. Is there any way to "rebuild" apt? I thought it just looked into the RPM database.... ?? C.
* Clayton;
segfaulting now though. I was able to add an app, and romve one using YAST.... so something is still broken.... at least with apt. Is there any way to "rebuild" apt? I thought it just looked into the RPM database.... ??
I am still not using apt so do not expect a big help on that side. yet IIRC apt has a separate database. Did you check the FAQ for apt as I am sure Richard has mentioned it there -- Togan Muftuoglu | Unofficial SuSE FAQ Maintainer | Please reply to the list; http://susefaq.sf.net | Please don't put me in TO/CC. Nisi defectum, haud refiecendum
* Clayton
Thanks for the suggestion Togan.... I did an rpm --initdb and then a rpm --rebuilddb. That went off without a hitch. Tried an apt-get check next and still am getting a segfault at 64%. YAST isn't segfaulting now though. I was able to add an app, and romve one using YAST.... so something is still broken.... at least with apt. Is there any way to "rebuild" apt? I thought it just looked into the RPM database.... ??
Just a guess, but there are two files updated when 'apt update' runs that may be causing your problem: /var/cache/apt/pkgcache.bin /var/cache/apt/srcpkgcache.bin you might move them or rename them and see if your still have your problem. That way you can put them back if they are not your problem. -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/gallery2
participants (3)
-
Clayton -
Patrick Shanahan -
Togan Muftuoglu