yum error

[jerboyd]

does anyone know what this yum error means?

Installing : yum-plugin-fastestmirror 1/1
Error unpacking rpm package yum-plugin-fastestmirror-1.1.20-4.fc11.noarch
error: unpacking of archive failed on file /etc/yum/pluginconf.d/fastestmirror.conf;49aff610: cpio: MD5 sum mismatch

[JonathanR]

does anyone know what this yum error means?

Installing : yum-plugin-fastestmirror 1/1
Error unpacking rpm package yum-plugin-fastestmirror-1.1.20-4.fc11.noarch
error: unpacking of archive failed on file /etc/yum/pluginconf.d/fastestmirror.conf;49aff610: cpio: MD5 sum mismatch

That's not an issue with yum, but the package. Try and download the package again. If that still fails, file a bug report with the packager.

[jerboyd]

i did a fresh install of f11 alpha yesterday and tried to install akmod-nvidia. it downloaded about 90 packages or so and when it went to install i got that message from about half of the packages. the other half of them installed and it broke my system. i re-installed this morning and the first package i tried was the yum-fastestmirror and i get the same error. how is it possible that so many packages have errors?

[kingston26]

Had the same issue.

Here is what You should do:

Install fresh fedora 11 Alhpa.
Update rpm and yum before any other packages.
(first run "yum update rpm" and then "yum update yum")

That solved my problem.

good luck!

[timliim]

I had the same issue with F11-Alpha fresh intall, and
Kingston26's fix worked for me. Kingston26, thanks!

On 1st try I missed by a bit, though, doing "yum update rpm yum"
(updating rpm,yum together), and got "cpio: MD5 sum mismatch"
when updating yum :-) itself. The next "yum update yum" went
well, though, which led me to believe the problem was in
rpm-4.6.0-0.rc3.2.fc11 itself.

[Lebenskuenstler]

Looks quite ugly to me:

[root@test-f11 Packages]# yum update rpm
Geladene Plugins: dellsysidplugin2, refresh-packagekit
rpmdb: Program version 4.7 doesn't match environment version 4.5
Fehler: db4-Fehler (-30971) von dbenv->open: DB_VERSION_MISMATCH: Database environment version mismatch
Fehler: Kann den Packages-Index nicht öffnen, benutze db3 - (-30971)
Fehler: Kann Paket-Datenbank in /var/lib/rpm nicht öffnen
Traceback (most recent call last):
File "/usr/bin/yum", line 29, in <module>
yummain.user_main(sys.argv[1:], exit_code=True)
File "/usr/share/yum-cli/yummain.py", line 299, in user_main
errcode = main(args)
File "/usr/share/yum-cli/yummain.py", line 153, in main
base.getOptionsConfig(args)
File "/usr/share/yum-cli/cli.py", line 188, in getOptionsConfig
self.conf
File "/usr/lib/python2.6/site-packages/yum/__init__.py", line 630, in <lambda>
conf = property(fget=lambda self: self._getConfig(),
File "/usr/lib/python2.6/site-packages/yum/__init__.py", line 227, in _getConfig
self._conf = config.readMainConfig(startupconf)
File "/usr/lib/python2.6/site-packages/yum/config.py", line 772, in readMainConfig
yumvars['releasever'] = _getsysver(startupconf.installroot, startupconf.distroverpkg)
File "/usr/lib/python2.6/site-packages/yum/config.py", line 842, in _getsysver
idx = ts.dbMatch('provides', distroverpkg)
TypeError: rpmdb open failed

[scottro]

Known issue, documented and fixed.

After installation

yum -y update rpm

After that, yum will run without problems.

It had to do with a major rebuild, but they fixed it quite quickly and got it documented. At first it was a bit more complex to fix, but within 24-48 hours, all you had to do was update rpm as mentioned above, and then your upgrades will work correctly.

Many thanks and praise to the developers for fixing it as quickly as they did.

[Lebenskuenstler]

Known issue, documented and fixed.

After installation

yum -y update rpm

After that, yum will run without problems.

It had to do with a major rebuild, but they fixed it quite quickly and got it documented. At first it was a bit more complex to fix, but within 24-48 hours, all you had to do was update rpm as mentioned above, and then your upgrades will work correctly.

Many thanks and praise to the developers for fixing it as quickly as they did.

This happend AFTER i updated rpm today.

[scottro]

Hrrm. I tried to duplicate it on a fresh install, and wasn't able to do it.

And rpm, as well as db-utils, rpm-python and rpm-libs all updated without an issue?

Ok, if it's happening to you, I suspect it will start happening to others as well--at this point, I can only say something useless.

The only thing that *might* (and I have little or no hope that it would) help, that I can think of off the top of my head is doing yum clean all, making sure rpm is up to date and trying again.

Unfortunately, there's no way to get rpm to ignore md5. There is a documented --nomd5 option in the man page, but as I found to my sorrow, it doesn't seem to work..

I realize this is not much help at all, and apologize--I also now worry about my next update. (Makes quick check). No mention of it on the Fedora-testing list, at least not yet.

If this is a fresh install, is it worth the aggravation to try a reinstall, then, before doing anything, updating rpm and trying again? (Knowing that you might have the same issue?)


(Right now, all my rawhide installs are light test installations, I realize this isn't the case for everyone.)

[Lebenskuenstler]

Hi,

thanks for your reply.

I followed your advice and did reinstall (WOW, runs very nicely from my old, noisy 20G USB disk.)

I did only update NetworkManager after rpm update now, but I had no issues there.

LK

[timliim]

This happend AFTER i updated rpm today.

Lebenskuenstler,
Could you confirm that you
- installed F11 alpha
- did "yum -y update rpm" right after first boot

Same procedure worked for me yesterday, so I'd like
to find out why too.

Thanks,
Tim Taiwanese Liim

[Lebenskuenstler]

Lebenskuenstler,
Could you confirm that you
- installed F11 alpha
- did "yum -y update rpm" right after first boot

Same procedure worked for me yesterday, so I'd like
to find out why too.

Thanks,
Tim Taiwanese Liim

In the second run, YES, I confirm.

[scottro]

So, now did it work this time? (Hrrm, that made little sense.) In other words, after doing the reinstall, and running yum update rpm immediately afterwards, were you then able to upgrade everything successfully or did you just stop with NM for the moment?

Thanks.
By the way, your answers, and the time you took are probably helping a lot of people, if it's any consolation for the aggravation of reinstall.

[Lebenskuenstler]

At the point I wrote the reply I had stoped with NM packages. Afterwards I TRIED to make a complete yum update. At some point I had to reboot (I guess the was related to xorg driver) which resulted again in a corrupted database *grmpf*

For the 3rd and last time now I am running a install and will update in text mode after installation.

I will tell you what happens.

[Lebenskuenstler]

In German we have a sayinig: All good things are three.
Meaning: In the 3rd run everything should turn out fine.

And it did :)

[timliim]

Great to know it works now! And thanks for sharing the
German saying. Interesting one.

Tim Taiwanese Liim

[scottro]

Ah, in English have a few sayings too, good things come in threes, third time pays for all, third time's the charm, third time lucky. Of course, our language comes from yours. :)

[timliim]

:) My first language is Taiwanese. But English works great for me.
Tim Taiwanese Liim

[cgrim]

Is "cpio: MD5 sum mismatch" problem here again?

After update rpm on version 4.7.0-0.beta1.9 it gives me the same error messages (on all packages I try to install or update) and akmod-nvidia cannot build kmod because of NOKEY error (I think there can be similar problem).

[scottro]

No, it's a different error, you have to redo nss and nss-devel.

See the mailing list archives (sorry, rushing so can't do the link) for Fedora testing, and look for posts about it from Saturday and Sunday). (Ignore my posts, I thought the OP on the list had a different issue.)

[cgrim]

Thank you very much for your help. It solved all problems which have occured to me today:
1) firefox didn't show any page
2) thunderbird didn't connect to any mail server
3) yum updates failed because of MD5 sum mismatch or NOKEY error

... after downgrade nss from nss-3.12.2.99.3-5.fc11 to nss-3.12.2.99.3-3.fc11 everything is working again ;-)

[lmcogs]

This looks like my problem. Where can I get nss-3.12.2.99.3-3.fc11?

[cgrim]

You can download it here:
http://koji.fedoraproject.org/koji/buildinfo?buildID=96076

... depends on what platform are you using ;-)

[lmcogs]

Thanks for help but could not install it for same reason and getting the same on everthing I try to update or install. Also tried to do --nomd5 and --force still got the same
rpm --oldpackage -Uvh nss-3.12.2.99.3-3.fc11.x86_64.rpm
warning:nss-3.12.2.99.3-3.fc11.x86_64.rpm: Header SHA1 digest: NOKEY
Preparing... ########################################### [100%]
warning: nss-3.12.2.99.3-3.fc11.x86_64: Header SHA1 digest: NOKEY
1:nss ########################################### [100%]
error: unpacking of archive failed on file /etc/prelink.conf.d/nss-prelink.conf;49dbc0bb: cpio: MD5 sum mismatch

[cgrim]

Yes it's logical, because you still have bad libs from corrupted nss package.

I did it by a little unclean way:
1) unpack libs from nss-3.12.2.99.3-3.fc11.x86_64.rpm (by rpm2cpio or fileroller)
2) remove nss package using --nodeps flag (rpm -e --nodeps nss)
3) copy new libs (upacked from nss-3.12.2.99.3-3.fc11.x86_64.rpm) into /lib64
4) install nss-3.12.2.99.3-3.fc11.x86_64.rpm

Now, when I'm looking on that steps, step number 2 is probably redundant ;-)

Good luck!

[lmcogs]

Well thanks cgrim that worked. Just back from work thinking a clean install but this has made my day. Didn't I do a system update and that updated nss again, must remember that.

Anyway things are working again plus thunderbird, firefox.

Meant to say I did not do step 2.

[cgrim]

I'm glad that it helped to you ;-)

Did you try nss-3.12.2.99.3-7.fc11? Is it as bad as nss-3.12.2.99.3-5.fc11?

[lmcogs]

Not yet but may do after the football

[lmcogs]

Seems like update has nss-3.12.2.99.3-7.fc11 and works fine