From owner-freebsd-questions@freebsd.org Thu Apr 15 17:11:36 2021 Return-Path: Delivered-To: freebsd-questions@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 3AA725F7387 for ; Thu, 15 Apr 2021 17:11:36 +0000 (UTC) (envelope-from merlyn@geeks.org) Received: from mail.geeks.org (jacobs.geeks.org [204.153.247.1]) (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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4FLm8l0C2Fz4bwP for ; Thu, 15 Apr 2021 17:11:34 +0000 (UTC) (envelope-from merlyn@geeks.org) Received: from mail.geeks.org (localhost [127.0.0.1]) by after-clamsmtpd.geeks.org (Postfix) with ESMTP id A3FD034551 for ; Thu, 15 Apr 2021 12:11:28 -0500 (CDT) Received: by mail.geeks.org (Postfix, from userid 1003) id 8EB0E344E4; Thu, 15 Apr 2021 12:11:28 -0500 (CDT) Date: Thu, 15 Apr 2021 12:11:28 -0500 From: Doug McIntyre To: freebsd-questions@freebsd.org Subject: Re: Why is freebsd-update so horrible slow? Message-ID: References: <2371411618364379@vla3-7c930ca38d8d.qloud-c.yandex.net> <78283e5d-f46f-2e21-7ccb-ce661531af06@qeng-ho.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <78283e5d-f46f-2e21-7ccb-ce661531af06@qeng-ho.org> X-Virus-Scanned: ClamAV using ClamSMTP X-Rspamd-Queue-Id: 4FLm8l0C2Fz4bwP X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of merlyn@geeks.org designates 204.153.247.1 as permitted sender) smtp.mailfrom=merlyn@geeks.org X-Spamd-Result: default: False [-2.27 / 15.00]; RCVD_TLS_LAST(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[204.153.247.1:from]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+ptr]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-questions@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[204.153.247.1:from:127.0.2.255]; RCVD_COUNT_THREE(0.00)[3]; ARC_NA(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.97)[-0.972]; DMARC_NA(0.00)[geeks.org]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:7753, ipnet:204.153.244.0/22, country:US]; SUBJECT_ENDS_QUESTION(1.00)[]; MAILMAN_DEST(0.00)[freebsd-questions] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Apr 2021 17:11:36 -0000 On Thu, Apr 15, 2021 at 01:35:00PM +0100, Arthur Chance wrote: > On 14/04/2021 02:39, Erik Lauritsen wrote: > > I have been setting here for about 6 hours waiting for an upgrade > > from 12.2 to 13 and freebsd-update is only half way through getting > > all the patches! > > > > It's painful. It's like the 90th with 56k modems and I am on a > > gigabit wire. > > > > Then I did a search and this has apparently been an issue for several > > years, it has even been filed as a bug. > > > > Anyway, I have cancelled the upgrade. If it's going to take this > > long, I am not going to upgrade this, but will most likely replace it > > with another OS. > > This tweet from Colin Percival talks about the problem. > > https://twitter.com/cperciva/status/1382491128537096193 > > TL;DR: changes to git caused a massive overload, the number of mirrors > has been increased to deal with it. Although his status is on portupgrade, not freebsd-update. Is there any way for me to build my own update server locally? I've tried web caching the data, but I have to be able to get all the data first.. (What the handbook mentions IIRC) Fetching 3299 files... ....10....20....30....40....50....60....70....80....90....100....110....120.. ..130....140....150....160....170 gunzip: (stdin): unexpected end of file ae47b8b528bdf1369c7779d0dd453364922c77f3993fd147486b952fdbe91634 has incorrect hash. At various points along the fetch on each try.