Date: Sun, 18 Apr 2021 08:51:05 +0800 From: Philip Paeps <philip@freebsd.org> To: Rainer Duffner <rainer@ultra-secure.de> Cc: Ferdinand Goldmann <Ferdinand.Goldmann@jku.at>, freebsd-stable@freebsd.org, clusteradm@freebsd.org Subject: Re: freebsd-update and speed Message-ID: <F096A52E-743B-4A4C-8AA3-184F3D43EEDE@freebsd.org> In-Reply-To: <C5C382FD-5F5E-42CA-9E0C-138CC879A0EC@ultra-secure.de> References: <672990ce-2fa4-d3b0-57f1-1d3221f13e95@jku.at> <0F8B7132-0721-4999-9C3E-ED29C80BDB17@ultra-secure.de> <3c25f2c6-8686-eb29-2877-cb601c6f46bc@jku.at> <C5C382FD-5F5E-42CA-9E0C-138CC879A0EC@ultra-secure.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2021-04-18 03:12:35 (+0800), Rainer Duffner wrote: >> Am 16.04.2021 um 10:17 schrieb Ferdinand Goldmann = >> <ferdinand.goldmann@jku.at>: >> >> On Thu, 15 Apr 2021, Rainer Duffner wrote: >> >>> >>> >>> It=E2=80=99s OK-ish most of the time here (CH). >>> >>> It does *NOT* work through a proxy, due to the use of pipelined = >>> http-requests. >>> >>> What=E2=80=99s your internet-connection? >> >> The 10Gbit uplink of my university, directly connected to the = >> internet, not >> behind a proxy. I don't think that's the problem. When update3 was = >> still online >> I'd always use that and updates were really fast back then. >> >> Now that update3 is gone all update servers seem to be in the US or = >> Australia. >> >> After waiting for nearly one hour: >> >> ..8530....8540....8550....8560....8570....8580....8590....8600....8610= =2E...8620....8630....8640....8650....8660....8670....8680....8690....870= 0.... = >> done. >> Applying patches... done. >> Fetching 9628 files... gunzip: (stdin): unexpected end of file >> 0a4626107f3700cf5f87bd9c123bf427bd5a8561aadc2eca1d1605465c090935 has = >> incorrect hash. >> >> This is getting kind of tiresome. :( >> >> Regards >> Ferdinand > > > > > There seems to be a problem with update4. > > I now have this, too. > > > I=E2=80=99m cc-ing clusteradm and dnsadmin, in hope that there=E2=80=99= s somebody = > there who can either fix it or take update4 out of the srv record=E2=80= =A6 I can take update4 out of the DNS if it's misbehaving consistently. If = at all possible though, I'd prefer to fix the actual problem rather than = simply make it disappear from the DNS. It looks like there were at least experiments with pointing = freebsd-update at AWS, similar to how portsnap currently works. I will = check if these experiments went anywhere and possibly point = freebsd-update there instead. I believe the problem with update4 is load-related. > :-( > > I would rather just mirror the update server but I think this is not = > supposed to be done? I think you can set up your own freebsd-update servers, but that won't = fix this problem. I'll see what can be done to fix this. Watch this space. Philip [hat: clusteradm firefighter] -- = Philip Paeps Senior Reality Engineer Alternative Enterprises
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?F096A52E-743B-4A4C-8AA3-184F3D43EEDE>