From owner-freebsd-stable@freebsd.org Sun Apr 18 00:51:12 2021 Return-Path: Delivered-To: freebsd-stable@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id C2B765E8AC9 for ; Sun, 18 Apr 2021 00:51:12 +0000 (UTC) (envelope-from philip@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4FNBG84zJ5z3m27; Sun, 18 Apr 2021 00:51:12 +0000 (UTC) (envelope-from philip@freebsd.org) Received: from weatherwax.trouble.is (weatherwax.trouble.is [IPv6:2a00:1098:82:3a::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "weatherwax.trouble.is", Issuer "R3" (verified OK)) (Authenticated sender: philip/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 87B34F6F1; Sun, 18 Apr 2021 00:51:12 +0000 (UTC) (envelope-from philip@freebsd.org) Received: from rincewind.trouble.is (rincewind.trouble.is [95.216.22.234]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits)) (Client CN "rincewind.trouble.is", Issuer "R3" (verified OK)) by weatherwax.trouble.is (Postfix) with ESMTPS id 4FNBG74vnwz2LCZ; Sun, 18 Apr 2021 00:51:11 +0000 (UTC) Received: by rincewind.trouble.is (Postfix, authenticated sender philip) id 4FNBG534HJz5QR3; Sun, 18 Apr 2021 00:51:09 +0000 (UTC) From: Philip Paeps To: Rainer Duffner Cc: Ferdinand Goldmann , freebsd-stable@freebsd.org, clusteradm@freebsd.org Subject: Re: freebsd-update and speed Date: Sun, 18 Apr 2021 08:51:05 +0800 X-Clacks-Overhead: GNU Terry Pratchett X-Mailer: MailMate (1.14r5795) Message-ID: In-Reply-To: References: <672990ce-2fa4-d3b0-57f1-1d3221f13e95@jku.at> <0F8B7132-0721-4999-9C3E-ED29C80BDB17@ultra-secure.de> <3c25f2c6-8686-eb29-2877-cb601c6f46bc@jku.at> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed; markup=markdown Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.34 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Apr 2021 00:51:12 -0000 On 2021-04-18 03:12:35 (+0800), Rainer Duffner wrote: >> Am 16.04.2021 um 10:17 schrieb Ferdinand Goldmann = >> : >> >> 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