From nobody Mon Jun 20 12:06:54 2022 X-Original-To: bugs@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 5FCCB86FF76 for ; Mon, 20 Jun 2022 12:06:54 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (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 "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4LRT0G01ZPz3rCP for ; Mon, 20 Jun 2022 12:06:54 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (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 mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id D053B1CEB0 for ; Mon, 20 Jun 2022 12:06:53 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 25KC6rnU071461 for ; Mon, 20 Jun 2022 12:06:53 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 25KC6rsY071460 for bugs@FreeBSD.org; Mon, 20 Jun 2022 12:06:53 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 260399] freebsd-update: Downloading patches often fails repeatedly Date: Mon, 20 Jun 2022 12:06:54 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: Unspecified X-Bugzilla-Keywords: needs-qa X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: julian@precisium.com.au X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: koobs@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Bug reports List-Archive: https://lists.freebsd.org/archives/freebsd-bugs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-bugs@freebsd.org MIME-Version: 1.0 ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1655726814; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=cGKQrP3eq1ypwh08KYdcfmTrfjLH886ZQBNRRVLNNIE=; b=Tp8y2kZpTkQeX4TumMco8Ga3nHGOC/5jCbOkPy5a7IYa0JbzX5UTJP3I3ZCKSefF3enXtK 2YAOz3oyX8xii8R/JQVcOxfF+B2xj4tIX0n4l1UPK1cMjpU4B4nLu74lT8fDfe4xttqy5b K/IlZLQ10bFoTlE2GFEIsnYOLewKskDAlFwUhGJQNGqbZxkz0Kh/6y0yR6hyb2Zkq2a9ro uBHDJOz3BtGeL4R3zV6OtaBdP0WUVqdYwgKdErWZm8TW1fUSn8sCtExmHYNiJoBAgnKlPq 1iACkZz+40viPas77WuJ+1A9oNxmXH9w93uk2TZLYODC0kMeOJBxl56lzUagyg== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1655726814; a=rsa-sha256; cv=none; b=NRBVBeYZ7yZ8349uzx6MqZR9K7658zOk3UpH9HyeVX/gU7OdAoFKK+eqKUsH/ZpZvm8pyl HhGOy81WfsyJAiBsv6HoGnNJQhwR93N2AG0uzmB6Job9tyZijRjbGOsrpO8yqrvWogeT/N cVaacvxBpnLpFGS/eIWCb/A5EiWRXZuQ3WoGj9FoiiyTN1HTQwPpTApgfSaQfmj1Vj8/0L WwQrxWVS7SVofWL+9xKzptlV3KdMH1ZMCD+d7PnP56dDXGqqE2TIX6cmRThaYOt/cMOBHl YCgt4pqKUhe2hLG5uqpa8lEkjbHz1W3Gu/6w4Xi0KzCGQexGonYK8y8QlePNjA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D260399 Julian Noble changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |julian@precisium.com.au --- Comment #13 from Julian Noble --- I think the most important bug here is the failure to restart utilizing the already downloaded patches and files. I'm usually running it on a low latency 1Gbps link in a big city in Austral= ia - but freebsd-update has been a big *slow* problem for me for a long time on different systems and different network paths. The additional latency and no local mirrors doesn't help - but all that wou= ld be bearable if it just wouldn't restart doing work that has already been do= ne each time. Really I don't think understanding exactly why a particular request failed = or exactly what version people are upgrading to or from is the issue. The netw= orks will never be perfect. I've tried proxy/caching via nginx - but that's another layer of indirection which makes it harder to debug (e.g it seems that 404s are common and norma= l - but some can be cached - others shouldn't be?) Simply doing a quick restart of nginx means any freebsd-updates pointed to = it need to restart from scratch... which suggests to me that the way this works isn't really suitable for global distribution. I'd love to try running my own freebsd-update server - but that seems a mas= sive job - and really I can see fewer and fewer technically inclined people even getting to that level with the freebsd-update experience as it is. Perhaps it's fine in North America with latencies of a few 10s of milliseco= nds and everyone there barely cares about the odd restart from scratch? I know freebsd-update involves a lot of cleverness in what it does - but I= =20 understand the frustrations of the OP.=20 Starting a slow grind through 57000+ high latency http requests again is mo= re than a minor annoyance. It's not just an hour or two either.. these update attempts for a few machines can end up taking days of an admins time and th= us get put off. The only indication at the end is "failed" In some cases - such as running via a wrapper such as iocage - I don't think there's even a way to pass through the debug flag. Is there a way to make freebsd-update resume from close to where it stopped? --=20 You are receiving this mail because: You are on the CC list for the bug.=