[SOLVED for now]I broke my rpm database?

This forum is dedicated to basic help and support :

Ask here your questions about basic installation and usage of Mageia. For example you may post here all your questions about getting Mageia isos and installing it, configuring your printer, using your word processor etc.

Try to ask your questions in the right sub-forum with as much details as you can gather. the more precise the question will be, the more likely you are to get a useful answer

[SOLVED for now]I broke my rpm database?

Postby mark9117 » Jul 6th, '15, 21:59

Brand new Mageia 5 install. I had my first round of updates today. Ran the updates and got an error. Seems to be related to a package. Scouring Google searches seems to indicate that I need to uninstall a package and/or rebuild the rpm database. That last step seems pretty straitforward, but I can't find the command or switch that rebuilds the rpm database.

Here is the error from "rpm -qa":

Code: Select all
kfind-4.14.3-1.mga5
:error: rpmdbNextIterator: skipping h#    2336 blob size(3784): BAD, 8 + 16 * il(-2119925340) + dl(-2119925340)
error: rpmdbNextIterator: skipping h#    2335 blob size(63088): BAD, 8 + 16 * il(1700869985) + dl(3749476)
error: rpmdbNextIterator: skipping h#    2332 blob size(3572): BAD, 8 + 16 * il(71) + dl(17812)
error: rpmdbNextIterator: skipping h#    2333 blob size(5748): BAD, 8 + 16 * il(841823022) + dl(1835491634)
error: rpmdbNextIterator: skipping h#    2338 blob size(19332): BAD, 8 + 16 * il(1761301884) + dl(1761301884)
error: rpmdbNextIterator: skipping h#    2331 blob size(18956): BAD, 8 + 16 * il(66) + dl(14168)
error: rpmdbNextIterator: skipping h#    2337 blob size(85564): BAD, 8 + 16 * il(808727349) + dl(1650669368)
error: rpmdbNextIterator: skipping h#    2334 blob size(15232): BAD, 8 + 16 * il(1651732332) + dl(1702126948)
lib64gweather3_6-3.14.3-1.mga5


I bookended that information with the programs that show up as listed. Is one of those packages at fault? Is there some way to rebuild the rpm database, and is that likely to fix it?

Has anybody seen this before?

Thanks.

Mark
Last edited by mark9117 on Jul 6th, '15, 22:59, edited 1 time in total.
Let's just reboot everything all the time.
User avatar
mark9117
 
Posts: 395
Joined: Sep 12th, '11, 20:32
Location: Eastern New Mexico -- Not Hell, but you can see it from here.

Re: I broke my rpm database?

Postby jkerr82508 » Jul 6th, '15, 22:26

There is an open bug report:
https://bugs.mageia.org/show_bug.cgi?id=16197

To rebuild the rpm data base, as root execute the following two commands:
Code: Select all
rm -f /var/lib/rpm/__db*
rpm --rebuilddb

Jim
jkerr82508
 
Posts: 946
Joined: Mar 26th, '11, 01:34
Location: Fife, Scotland

Re: I broke my rpm database?

Postby mark9117 » Jul 6th, '15, 22:31

I appreciate the assistance Jim. Unfortunately, no joy:

Code: Select all
# rpm --rebuilddb
error: rpmdbNextIterator: skipping h#    2336 blob size(3784): BAD, 8 + 16 * il(-2119925340) + dl(-2119925340)
error: rpmdbNextIterator: skipping h#    2335 blob size(63088): BAD, 8 + 16 * il(1700869985) + dl(3749476)
error: rpmdbNextIterator: skipping h#    2332 blob size(3572): BAD, 8 + 16 * il(71) + dl(17812)
error: rpmdbNextIterator: skipping h#    2333 blob size(5748): BAD, 8 + 16 * il(841823022) + dl(1835491634)
error: rpmdbNextIterator: skipping h#    2338 blob size(19332): BAD, 8 + 16 * il(1761301884) + dl(1761301884)
error: rpmdbNextIterator: skipping h#    2331 blob size(18956): BAD, 8 + 16 * il(66) + dl(14168)
error: rpmdbNextIterator: skipping h#    2337 blob size(85564): BAD, 8 + 16 * il(808727349) + dl(1650669368)
error: rpmdbNextIterator: skipping h#    2334 blob size(15232): BAD, 8 + 16 * il(1651732332) + dl(1702126948)


Still looking for solutions.

Mark
Let's just reboot everything all the time.
User avatar
mark9117
 
Posts: 395
Joined: Sep 12th, '11, 20:32
Location: Eastern New Mexico -- Not Hell, but you can see it from here.

Re: I broke my rpm database?

Postby mark9117 » Jul 6th, '15, 22:58

Sorry, I didn't see that second message you sent before I posted.

Update: I rebuilt the db and just installed a package with no error. I'll shelve this for now and see if it show up again, and/or see if an update patches.

I do appreciate the time and attention.

I'll mark this solved for now.

Mark
Let's just reboot everything all the time.
User avatar
mark9117
 
Posts: 395
Joined: Sep 12th, '11, 20:32
Location: Eastern New Mexico -- Not Hell, but you can see it from here.


Return to Basic support

Who is online

Users browsing this forum: No registered users and 1 guest