apt-get update fails with error 416 Requested Range Not Satisfiable

Bug #798023 reported by Sebastian Nohn
98
This bug affects 21 people
Affects Status Importance Assigned to Milestone
apt (Ubuntu)
Fix Released
High
Unassigned

Bug Description

Binary package hint: apt

Err http://de.archive.ubuntu.com maverick-updates/main i386 Packages
  416 Requested Range Not Satisfiable [IP: 141.30.13.30 80]
Fetched 5,079B in 2s (2,296B/s)
W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/maverick-updates/main/binary-i386/Packages.gz 416 Requested Range Not Satisfiable [IP: 141.30.13.30 80]

E: Some index files failed to download, they have been ignored, or old ones used instead.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: apt 0.8.3ubuntu7.1
ProcVersionSignature: Ubuntu 2.6.35-28.50-generic 2.6.35.11
Uname: Linux 2.6.35-28-generic i686
Architecture: i386
Date: Thu Jun 16 07:56:13 2011
ExecutablePath: /usr/bin/apt-get
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: apt

Revision history for this message
Sebastian Nohn (sebastian-nohn) wrote :
Revision history for this message
Douglas Leeder (ubuntu-leeder) wrote :

One way around the problem might be to change your sources.list to a different country, so that apt-get is forced to download the whole file.

Changed in apt (Ubuntu):
status: New → Confirmed
Revision history for this message
Mika Pflüger (mikapflueger) wrote :

Changeing the mirror to the main mirror from the update-manager did work, but somehow the german mirror still appears broken.

Revision history for this message
Axel Pospischil (apos) wrote :

I am on 11.04 but using the oneiric sources with apt-pinning and get the same error:

Fehl http://de.archive.ubuntu.com oneiric/universe amd64 Packages
  416 Requested Range Not Satisfiable [IP: 141.30.13.10 80]

and in the summary:

W: Fehlschlag beim Holen von http://de.archive.ubuntu.com/ubuntu/dists/oneiric/universe/binary-amd64/Packages 416 Requested
Range Not Satisfiable [IP: 141.30.13.10 80]

But when i change my oneiric.list to use the default server (without prefix "de."), everything works fine.

This really seams to be a problem with the server. The problem is, that it takes several sekonds ( about a minute) for apt to resolve the issue which is very annoying on updates.

Revision history for this message
Ilja Pavkovic (ipavkovic) wrote :

sudo rm -rf /var/lib/apt/lists/partial/* removes partially downloaded repository files. This fixed this problem on my system.

Revision history for this message
Sven K. (wagalaweia) wrote :

I had the same problem, but the workaround by Ilja (removing partially downloaded repository files) solved it. I did not even had to restart the update manager.

Revision history for this message
Christopher K. (christopher-christosoft) wrote :

Same problem here and Ilja's workaround fixed it. I think apt might delete these files and try again when this error happens. As this seems to be easy to fix automatically, I think apt should be able to fix it without any user interaction.

Changed in apt (Ubuntu):
importance: Undecided → High
Revision history for this message
Ben Howard (darkmuggle-deactivatedaccount) wrote :

http:400%20URI%20Failure%0aURI:%20http://us-east-1.ec2.archive.ubuntu.com.s3.amazonaws.com/ubuntu/dists/precise-updates/main/binary-i386/Packages.bz2%0aMessage:%20416%20%20Requested%20Range%20Not%20Satisfiable%20%0aFailReason:%20HttpError416

The S3 Apt mirrors are blocked pending this bug. A review of debug logs shows that S3-Ec2 mirror users who are hitting 403 are getting the 403 due to a fall through of 416 errors.

Note this only applies to meta-data failures.

Revision history for this message
ptoche (patrick-toche) wrote :

I guess I must have been experiencing a similar problem.

However, I removed all the lists, not just the partial lists, they were rebuild automatically by muon after "check for updates", and no restart needed as mentioned above:

sudo rm -rf /var/lib/apt/lists/partial/*
sudo rm -rf /var/lib/apt/lists/*

Note that the following was of no help whatsoever:
sudo apt-get purge muon
sudo apt-get clean
sudo apt-get install muon

Revision history for this message
ptoche (patrick-toche) wrote :

precision: my comment above is not clear enough, apologies.

1. removing the partial lists didn't "solve" the warning message, but removing all the lists did.

2. shouldn't one expect that "purge"-ing muon would remove these lists?

3. after purging, cleaning, installing again, then removing the lists, my list of "software sources" was still present in muon, before a restart (not sure if they would have been cleared after a restart because I did not restart).

I'm on kubuntu 10.04.

hope this helps a little. Thanks.

Revision history for this message
Daniel Hartwig (wigs) wrote : Re: [Bug 798023] Re: apt-get update fails with error 416 Requested Range Not Satisfiable

On 9 February 2013 22:04, ptoche <email address hidden> wrote:
> 2. shouldn't one expect that "purge"-ing muon would remove these lists?

No. Muon is not responsible for those lists. As indicated by the
path, they are handled by the apt package.

>
> 3. after purging, cleaning, installing again, then removing the lists,
> my list of "software sources" was still present in muon, before a
> restart (not sure if they would have been cleared after a restart
> because I did not restart).

No. The software sources are configured in /etc/apt/sources.list.
The lists under /var/lib contain package information retrieved from
those sources.

Revision history for this message
EOLE team (eole-team) wrote :

Hello,

Any news on this issue, we are facing it on Precise Pangolin some times.

Regards.

tags: added: precise
Revision history for this message
Timur Nurlygayanov (tnurlygayanov) wrote :

This issue reproduced on my labs, do we have fixed / workarounds?
I was described in 2011 and not fixed yet...

Revision history for this message
Julian Andres Klode (juliank) wrote :

There have been quite a lot of changes in xenial and newer to fetching files, so I'm closing this. If anyone can reproduce this in 16.04 or newer, feel free to reopen it or open a new bug.

Changed in apt (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.