Bug 122793
Summary: | fatal error communicating with the server - Status Code: 404 | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Bill Roman <bill.roman> |
Component: | up2date | Assignee: | Adrian Likins <alikins> |
Status: | CLOSED WONTFIX | QA Contact: | Fanny Augustin <fmoquete> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 2 | CC: | blackphiber, imc, jadelt, mattdm, phrasky, tony.naccarato |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-04-24 20:38:12 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 124619 |
Description
Bill Roman
2004-05-07 22:43:37 UTC
Same issue with "yum" unless the repositories have neen manually edited I have hit this , looks same. There was a fatal error communicating with the server. The message was: An HTTP error occurred: URL: http://fedora.redhat.com/download/up2date-mirrors/fedora-core-2/headers/header.info Status Code: 404 Error Message: Not Found it gives this error even when i=only the fc2 repo is allowed in sources config file. Same thing here. To get around it I had to downgrade to the previous version of up2date using: rpm -Uvh --oldpackage up2date-4.3.16-1.i386.rpm The bad version of up2date is : up2date-4.3.18-2 I suppose it would be a good idea if say `up2date -u' proceeded to install packages even if some of the listed sources aren't available. For example, FC2 is out, but if people attempt to use up2date to install packages from the core, they are going to have to disable the updates channel, or wait until updates are released such that the header.info file makes it to the servers. A warning would be reasonable, but a hard error for the default config probably isn't. It would also be nice if, when the GUI up2date finds that one of the sources is unreachable, it went back to the channel selection screen, instead of quitting after the user clicks on the error message that pops up. *** Bug 123223 has been marked as a duplicate of this bug. *** 4.3.19 points at the right urls. Sorry for problems, but was playing a bit of a catch-22 as figuring out exactly where fc2 would land before it landed anywhere caused some issues. So how about leaving this open until the points in comment #4 are addressed? *** Bug 123579 has been marked as a duplicate of this bug. *** Not sure who to contact about this, so I'm leaving a comment on the most relevant bug instead. The file at this URL: http://fedora.redhat.com/download/up2date-mirrors/updates-released-fc2.uk refers to a location which no longer exists because (for reasons best known to the current owners of the mirror and the bean-counting management which mandated the change of ownership) they seem to have moved things around. Instead of: http://www.mirror.ac.uk/sites/download.fedora.redhat.com/pub/fedora/linux/core/updates/2/$ARCH/ it should now say: http://www.mirror.ac.uk/mirror/fedora.redhat.com/updates/2/$ARCH/ And similar changes are due to the other UK-mirror lists. (Of course, it would be good if up2date were able to recover from this instead of just giving up.) Fedora Core 2 is now maintained by the Fedora Legacy project for security updates only. If this problem is a security issue, please reopen and reassign to the Fedora Legacy product. If it is not a security issue and hasn't been resolved in the current FC3 updates or in the FC4 test release, reopen and change the version to match. The problem of the URL location was fixed in FC3. The underlying problem of "up2date should work even if one source isn't right," well.. In any case, up2date has been removed from Fedora Core in favor of yum, pirut, and pup. (There are also other GUIs in Extras.) Unlikely that this will get fixed in Fedora, though it could be filed for RHEL if it's an issue there. |