Description of problem:
With todays (once again broken) push of updates,
yum aborts without any further error message midst of a yum update:
[root@mccallum] # yum update
Loaded plugins: fastestmirror, refresh-packagekit
Loading mirror speeds from cached hostfile
Install 1 Package(s)
Update 76 Package(s)
Remove 0 Package(s)
Total size: 185 M
Total download size: 105 M
Is this ok [y/N]: y
http://ftp.nluug.nl/pub/os/Linux/distr/fedora/linux/updates/11/i386/java-1.6.0-openjdk-126.96.36.199-25.b16.fc11.i586.rpm: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
(1/36): java-1.6.0-openjdk-188.8.131.52-25.b16.fc11.i586.rpm | 32 MB 00:25
(2/36): kernel-184.108.40.206-213.fc11.i586.rpm | 20 MB 00:18
http://ftp.tudelft.nl/download.fedora.redhat.com/linux/updates/11/i386/kernel-firmware-220.127.116.11-213.fc11.noarch.rpm: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
(3/36): kernel-firmware-18.104.22.168-213.fc11.noarch.rpm | 501 kB 00:00
(4/36): kernel-headers-22.214.171.124-213.fc11.i586.rpm | 853 kB 00:00
(5/36): libgweather-126.96.36.199-1.fc11.i586.rpm | 5.8 MB 00:05 ...
Version-Release number of selected component (if applicable):
The crap above. Likely yum is not able to produce something usable from the brokenness of the repos.
Ralf, this is repeatable ... it always just exits? And always after downloading a couple of pkgs?
I presume you aren't hitting C-c, right?
This is just one box?
Can you strace it and attach the result.
(In reply to comment #1)
> Ralf, this is repeatable
Repeatable, in the sense of "happened more than once on the same machine", yes.
Repeatable, in the sense of "how to reproduce it", no.
It happened more than once within ca. 1 hour on the same machine, but wasn't repeatable on others.
> ... it always just exits?
No, this breakdown was interspersed with other breakdowns (404's, missing files).
> And always after
> downloading a couple of pkgs?
> I presume you aren't hitting C-c, right?
> This is just one box?
> Can you strace it and attach the result.
I can try, but ... as I tried to indicate, earlier today, most update-repo mirrors yum redirected me to, were broken.
Seemingly, the repomd.xml didn't match the repo contents (Wild guess: mirror-manager is defective), while rpmfusion managed to screw their repos at the same time ...
So, I guess, it'll be very difficult to reproduce this issue.
I think this is the same root cause as 518720.
I'm going to mark it as a duplicate unless I hear otherwise.
*** This bug has been marked as a duplicate of bug 518720 ***