For us change `VfileUseRangeOps: -1` did not solved that problem. It was
happening with our custom repository only, let say `repo.xxx.com`
(unsure why, maybe because it was changing quite often?) and after
upgrade host from Xenial or Bionic (doesn't matter) to Focal the error
started to appear
VfileUseRangeOps: -1 fixed all my use cases.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1826405
Title:
Repeatedly "storage error [503 Inconsistent file state], last errno:
File exists
To
Well, touch wood, something I've done has made things happier. I moved
everything from the cache directory to a subfolder, made it
inaccessible, removed apt lists from clients and ran apt-get update,
then linked all the original cache files into _import and made acng
reimport them.
The first time
I was seeing the dreaded "503 Inconsistent file state" talking to the
canonical (sorry) package repositories. As I said, there are no explicit
upstream proxies, but who knows what the ISP is doing (this would be a
big argument in favour of running apt-get over https to my mind..)
Anyway, at the
Hi Steve,
On 8/15/19 11:04 PM, Steve Dodd wrote:
> acng seems totally broken in bionic. I'm not knowingly behind a proxy -
> can't completely rule out ISP doing something evil though. Anyone have
> any pointers on this? Very few google hits, nothing on bugs.debian.org
> that I can see, very
acng seems totally broken in bionic. I'm not knowingly behind a proxy -
can't completely rule out ISP doing something evil though. Anyone have
any pointers on this? Very few google hits, nothing on bugs.debian.org
that I can see, very little activity for acng on salsa.debian.org ..
--
You
Hoo my
Our proxys are NOT fixed.
I go back to VfileUseRangeOps: 0.
I need to choose between a functional repository for daily updates or a
functional repository for distribution release upgrade.
Will try if with VfileUseRangeOps: -1 I could get both.
--
You received this bug notification
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: apt-cacher-ng (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1826405
Same bug different cause:
VfileUseRangeOps: 0
is no longer usable.
Ubuntu dis-upgrader-all tar.gz files (for do-release-upgrade) always trigger
the same bug with the "storage error [503 Inconsistent file state], last errno:
File exists".
As our proxys seems to be fixed regarding if-range
Further analysis shows that this problem is due to a fun interaction
between lighttpd an ACNG. We use lighttpd to serve a local Debian/Ubuntu
package repository. In about half the cases where we run 'apt update',
it will fail with error 503 on the 'Release' file of such a repository.
What happens
10 matches
Mail list logo
