14 Nov
2024
14 Nov
'24
11:59 a.m.
Hi,
It seems that since about 0500Z today the Debian mirror CDN at
deb.debian.org has been rejecting requests from our apt-cacher with a
message like:
E: Failed to fetch
http://apt-cacher.lon.bitfolk.com/debian/deb.debian.org/debian/dists/bullse…
421 Misdirected Request [IP: 2001:ba8:1f1:f079::2 80]
I am looking into this. I don't know what is wrong yet. If you are
urently needing to uodate or install new packages just disable use of
BitFolk;s apt0cacher by removing "apt-cacher.lon.bitfolk.com/debian/"
from every line of your sources.list file(s).
I suspect some unfortunate interaction between Debian CDN (Fastly?) and
apt-cacher, as other mirrors are still working fine through our
apt-cacher.
Thanks,
Andy
--
https://bitfolk.com/ -- No-nonsense VPS hosting
14 Nov
14 Nov
2:26 p.m.
On Thu, Nov 14, 2024 at 11:59:42AM +0000, Andy Smith via BitFolk Users wrote:
It seems that since about 0500Z today the Debian
mirror CDN at
deb.debian.org has been rejecting requests from our apt-cacher with a
message like:
E: Failed to fetch
http://apt-cacher.lon.bitfolk.com/debian/deb.debian.org/debian/dists/bullse…
421 Misdirected Request [IP: 2001:ba8:1f1:f079::2 80]
The BitFolk aptcacher VMs are pretty ancient. I've quickly deployed a
new one with an up to date version of apt-cacher-ng and the problem
doesn't manifest, so this seems like a simple fix.
I assume that Fastly have done something with their configuration that
older versions of acng can't handle.
This will probably remain broken for the rest of today as I need to
deploy these properly.
Again, should you particularly urgently need to do package
updates/upgrades you can edit your sources to remove the literal string
"apt-cacher.lon.bitfolk.com/debian/" from each line. That leaves you
talking directly to deb.debian.org.
Thanks,
Andy
--
https://bitfolk.com/ -- No-nonsense VPS hosting
2:41 p.m.
Hi all!
On Thu, 14 Nov 2024, at 2:26 PM, Andy Smith via BitFolk Users wrote:
The BitFolk aptcacher VMs are pretty ancient. I've quickly deployed a
new one with an up to date version of apt-cacher-ng and the problem
doesn't manifest, so this seems like a simple fix.
I assume that Fastly have done something with their configuration that
older versions of acng can't handle.
This will probably remain broken for the rest of today as I need to
deploy these properly.
Again, should you particularly urgently need to do package
updates/upgrades you can edit your sources to remove the literal string
"apt-cacher.lon.bitfolk.com/debian/" from each line. That leaves you
talking directly to deb.debian.org.
In the VMs in future it might be neater/more flexible to use a generic or as-shipped
/etc/apt/sources.list and define the proxy in either /etc/apt/preferences.d/ with a config
file containing 'Acquire::http::Proxy "http://proxyaddress:proxyport";'
or use auto-apt-proxy[1] and set it in /etc/hosts or figure out the autodetection magic it
uses!
I use the latter on my home development setup these days, and also recently broke
everything by config-defining a proxy *and* using auto proxy!
[1] https://packages.debian.org/sid/auto-apt-proxy
Cheers!
--
Dave Hibberd <hibby(a)debian.org>
Debian Developer
Packet Radioist
MM0RFN
4:47 p.m.
Hi Dave,
On Thu, Nov 14, 2024 at 02:41:19PM +0000, Hibby via BitFolk Users wrote:
In the VMs in future it might be neater/more flexible
to use a generic
or as-shipped /etc/apt/sources.list and define the proxy in either
/etc/apt/preferences.d/ with a config file containing
'Acquire::http::Proxy "http://proxyaddress:proxyport";' or use
auto-apt-proxy[1] and set it in /etc/hosts
The reason why I have not done any of these things is that I wanted it
to be incredibly obvious from the main sources list what is going on. If
the mirrors were listed in sources.list but then the VM actually
contacted another host based on a setting in some other file, I think
that would be more complex for people to understand.
Anyway for most people package updates are a fairly trivial amount of
data transfer so there is no harm in just disabling it.
Thanks,
Andy
--
https://bitfolk.com/ -- No-nonsense VPS hosting
4:52 p.m.
On Thu, Nov 14, 2024 at 02:26:32PM +0000, Andy Smith via BitFolk Users wrote:
This will probably remain broken for the rest of today
as I need to
deploy these properly.
Monitoring shows this has started working again but I have not yet
finished deploying the new cacher VMs, so it seems like Fastly must have
reverted whatever they did at 5am. Ho hum. Guess it needed doing anyway.
I will go ahead and finish the deployment but in the intervening time I
can't guarantee they won't change things back again before I am done.
Thanks,
Andy
--
https://bitfolk.com/ -- No-nonsense VPS hosting
16 Nov
16 Nov
4:47 p.m.
Hi,
On Thu, Nov 14, 2024 at 02:26:32PM +0000, Andy Smith via BitFolk Users wrote:
I assume that Fastly have done something with their
configuration that
older versions of acng can't handle.
This will probably remain broken for the rest of today as I need to
deploy these properly.
It seems that Fastly reverted whatever change they made by later
Thursday night, just as I was about to deploy the first of the newer
aptcacher VMs that work despite their change.
I slacked off a little then as it didn't seem so urgent, but I did go
ahead and replace all of our aged aptcacher VMs with new ones just in
case any mirror should do this again. That's complete now.
Thanks,
Andy
--
https://bitfolk.com/ -- No-nonsense VPS hosting
68
days inactive
70
days old
5 comments
2 participants
participants (2)
-
Andy Smith -
Hibby