[Bug 260399] freebsd-update: Downloading patches often fails repeatedly

From: <bugzilla-noreply_at_freebsd.org>
Date: Thu, 06 Jan 2022 23:07:54 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260399

--- Comment #9 from Some Signup <somesignup@icloud.com> ---
My apologies for the delay in trying to update my machines. It's such a pain
that I put it off until I can't put it off any longer.


If I run freebsd-update with --debug I get to see thousands of errors
downloading files. I can post them all here, but I don't think it's necessary.
A couple of sample but unrelated entries:

http://ipv4.aws.portsnap.freebsd.org/bp/8585c48bb921235425ee2865596c60b70aab551562ade66b65902e35b979a1f8-6cf7851b2ddd1d39ac9345fb4efe852f25da266ce85a6a3906f808c6287c81e6:
404 Error (ignored)

http://ipv4.aws.portsnap.freebsd.org/f/a9be29debdb0c5186913b752ad4145f5221bd8944a58abbca1de03084d2acadf.gz:
400 Error (ignored)


Some of these errors are wrong - the files exist, and in other cases the files
are indeed missing. A couple of examples:

curl
http://ipv4.aws.portsnap.freebsd.org/bp/7f7a3e981fa345c60fc3dff57ed14af3b76c69d374cfaf50bbedcb9bbed2c013-85791eee88708d116494f0051e1e6930f227c9569f3d42d7658f8d01aee65a47
<html>
<head><title>404 Not Found</title></head>
<body>
<center><h1>404 Not Found</h1></center>
<hr><center>nginx/1.20.1</center>
</body>
</html>


curl --output thisoneisok.gz
http://ipv4.aws.portsnap.freebsd.org/f/a9be29debdb0c5186913b752ad4145f5221bd8944a58abbca1de03084d2acadf.gz
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   869  100   869    0     0   4456      0 --:--:-- --:--:-- --:--:--  4456


So there appear to be two errors here: genuinely missing files, and files which
exist but freebsd-update treats as missing.

Interestingly, when I tried in a browser to get to
'http://ipv4.aws.portsnap.freebsd.org/bp' I see an error in my browser trying
to get to 'http://ipv4.aws.portsnap.freebsd.org:8080/bp/'. I did not add this
8080 to the URL so I don't know where it's coming from (definitely not
something locally, no proxies). It would appear to be a redirection coming from
AWS.

-- 
You are receiving this mail because:
You are on the CC list for the bug.