Date: Mon, 20 Jun 2022 12:06:54 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 260399] freebsd-update: Downloading patches often fails repeatedly Message-ID: <bug-260399-227-6OYl8mKjY5@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-260399-227@https.bugs.freebsd.org/bugzilla/> References: <bug-260399-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D260399 Julian Noble <julian@precisium.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |julian@precisium.com.au --- Comment #13 from Julian Noble <julian@precisium.com.au> --- 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.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-260399-227-6OYl8mKjY5>