Re: sysupgrade fails with "FAILED" when "verifying sets"?
> On Dec 14, 2022, at 03:03, Bodie wrote: >> On 14.12.2022 11:34, Why 42? The lists account. wrote: >> Right you are, that's the one :-/ I used to be a SPARC kinda guy, but >> those are all gone now. > > OT - they are not, but those prices... > > https://shop.eol.systems/servers/server/ Wow. OK, so maybe there’s hope for me unloading the Ultra 80 and random other Spark boxes I still have! :-) Sean
Re: sysupgrade fails with "FAILED" when "verifying sets"?
On 14.12.2022 11:34, Why 42? The lists account. wrote: On Mon, Dec 12, 2022 at 11:11:24PM -0500, Nick Holland wrote: On 12/12/22 07:22, Why 42? The lists account. wrote: > > Hi All, > > Today sysupgrade failed for me, but I'm not sure why? Here's the output: [ ... ] There is a problem with the distribution network currently. Hopefully will be resolved soon. Doing a quick check, looks like only amd64 is broke..but of course, that's what you probably want. (good time to upgrade your other platforms!) Right you are, that's the one :-/ I used to be a SPARC kinda guy, but those are all gone now. OT - they are not, but those prices... https://shop.eol.systems/servers/server/ I do have a Novena (Bunny + Xobs) ARMv7 Laptop, but I suspect installing there would make my AMD64 issue look like a walk in the park :-) Anyway, the sysupgrade download + verify works now. Just have to reboot ... If I had the slightest of quibbles it would be to wonder why sysupgrade shows "SHA256.sig" (2144 bytes) being downloaded, but it only saves "SHA256" (1992 bytes). Just seems a bit odd is all. Thanks! Cheers, Robb.
Re: sysupgrade fails with "FAILED" when "verifying sets"?
On Tue, Dec 13, 2022 at 11:12:18AM -, Stuart Henderson wrote: > On 2022-12-12, Why 42? The lists account. wrote: > > Today sysupgrade failed for me, but I'm not sure why? Here's the output: > > As the various mirrors get updated, this should be coming back to normal now. Just FYI, It's working for me now. I'll see you after the reboot ... Thanks! Cheers, Robb.
Re: sysupgrade fails with "FAILED" when "verifying sets"?
On Mon, Dec 12, 2022 at 11:11:24PM -0500, Nick Holland wrote: > On 12/12/22 07:22, Why 42? The lists account. wrote: > > > > Hi All, > > > > Today sysupgrade failed for me, but I'm not sure why? Here's the output: > [ ... ] > > There is a problem with the distribution network currently. Hopefully > will be resolved soon. > > Doing a quick check, looks like only amd64 is broke..but of course, > that's what you probably want. (good time to upgrade your other platforms!) Right you are, that's the one :-/ I used to be a SPARC kinda guy, but those are all gone now. I do have a Novena (Bunny + Xobs) ARMv7 Laptop, but I suspect installing there would make my AMD64 issue look like a walk in the park :-) Anyway, the sysupgrade download + verify works now. Just have to reboot ... If I had the slightest of quibbles it would be to wonder why sysupgrade shows "SHA256.sig" (2144 bytes) being downloaded, but it only saves "SHA256" (1992 bytes). Just seems a bit odd is all. Thanks! Cheers, Robb.
Re: sysupgrade fails with "FAILED" when "verifying sets"?
On 2022-12-12, Why 42? The lists account. wrote: > Today sysupgrade failed for me, but I'm not sure why? Here's the output: As the various mirrors get updated, this should be coming back to normal now.
Re: sysupgrade fails with "FAILED" when "verifying sets"?
On Mon, Dec 12, 2022 at 8:19 AM Stuart Henderson wrote: > > On 2022-12-12, Amit Kulkarni wrote: > > retry, and all should be ok. > > No, there is a problem with the files. > Sorry for that Robb and Stuart.
Re: sysupgrade fails with "FAILED" when "verifying sets"?
On 12/12/22 07:22, Why 42? The lists account. wrote: Hi All, Today sysupgrade failed for me, but I'm not sure why? Here's the output: [ ... ] There is a problem with the distribution network currently. Hopefully will be resolved soon. Doing a quick check, looks like only amd64 is broke..but of course, that's what you probably want. (good time to upgrade your other platforms!) Nick.
Re: sysupgrade fails with "FAILED" when "verifying sets"?
On Mon, Dec 12, 2022 at 07:39:49AM -0600, Amit Kulkarni wrote: > retry, and all should be ok. What's the basis of your statement, did something change? It still fails for me (now @16:15 CET). I also tried a different mirror, same failure (below). @Stuart: Although sysupgrade output says that it fetched and used SHA256.sig, it appears only to save a file SHA256. That's why I tried using SHA256 on the signify command line :) Yours, Robb. > mjoelnir:_sysupgrade 12.12 16:13:38 # sysupgrade -s -n > Fetching from https://ftp.halifax.rwth-aachen.de/pub/OpenBSD/snapshots/amd64/ > SHA256.sig 100% > |*| > 2144 00:00 > Signature Verified > INSTALL.amd64 100% > || > 43554 00:00 > base72.tgz 100% > |*| >332 MB00:40 > bsd 100% > |*| > 22470 KB00:04 > bsd.mp 100% > |*| > 22578 KB00:02 > bsd.rd 100% > |*| > 4546 KB00:01 > comp72.tgz 100% > |*| > 75019 KB00:13 > game72.tgz 100% > |*| > 2745 KB00:00 > man72.tgz100% > |*| > 7610 KB00:01 > xbase72.tgz 100% > |*| > 52860 KB00:06 > xfont72.tgz 100% > |*| > 22967 KB00:03 > xserv72.tgz 100% > |*| > 14815 KB00:03 > xshare72.tgz 100% > |*| > 4573 KB00:01 > Verifying sets. > (SHA256) base72.tgz: FAILED > (SHA256) bsd: FAILED > (SHA256) bsd.mp: FAILED > (SHA256) bsd.rd: FAILED > (SHA256) comp72.tgz: FAILED > (SHA256) game72.tgz: FAILED > (SHA256) man72.tgz: FAILED > (SHA256) xbase72.tgz: FAILED > (SHA256) xfont72.tgz: FAILED > (SHA256) xserv72.tgz: FAILED > (SHA256) xshare72.tgz: FAILED > mjoelnir:_sysupgrade 12.12 16:15:17 [$?==1]# ls -l SHA256* > -rw-r--r-- 1 root wheel 1992 Dec 12 16:13 SHA256
Re: sysupgrade fails with "FAILED" when "verifying sets"?
On 2022-12-12, Amit Kulkarni wrote: > retry, and all should be ok. No, there is a problem with the files. >> I have never really used signify before, but this command from the man >> page also generates an error: >> > mjoelnir:_sysupgrade 12.12 13:03:30 # signify -C -p >> > /etc/signify/openbsd-73-base.pub -x SHA256 >> > signify: invalid comment in SHA256; must start with 'untrusted comment: ' Should use SHA256.sig not SHA256. -- Please keep replies on the mailing list.
Re: sysupgrade fails with "FAILED" when "verifying sets"?
retry, and all should be ok. On Mon, Dec 12, 2022 at 7:18 AM Why 42? The lists account. wrote: > > > Hi All, > > Today sysupgrade failed for me, but I'm not sure why? Here's the output: > > # sysupgrade -s -n > > Fetching from http://ftp.fau.de/pub/OpenBSD/snapshots/amd64/ > > SHA256.sig 100% > > |***| > > 2144 00:00 > > Signature Verified > > Verifying old sets. > > base72.tgz 100% > > |***| > >332 MB00:28 > > bsd 100% > > |***| > > 22470 KB00:02 > > bsd.mp 100% > > |***| > > 22578 KB00:02 > > bsd.rd 100% > > |***| > > 4546 KB00:01 > > comp72.tgz 100% > > |***| > > 75019 KB00:07 > > game72.tgz 100% > > |***| > > 2745 KB00:00 > > man72.tgz100% > > |***| > > 7610 KB00:01 > > xbase72.tgz 100% > > |***| > > 52860 KB00:05 > > xfont72.tgz 100% > > |***| > > 22967 KB00:02 > > xserv72.tgz 100% > > |***| > > 14815 KB00:02 > > xshare72.tgz 100% > > |***| > > 4573 KB00:01 > > Verifying sets. > > (SHA256) base72.tgz: FAILED > > (SHA256) bsd: FAILED > > (SHA256) bsd.mp: FAILED > > (SHA256) bsd.rd: FAILED > > (SHA256) comp72.tgz: FAILED > > (SHA256) game72.tgz: FAILED > > (SHA256) man72.tgz: FAILED > > (SHA256) xbase72.tgz: FAILED > > (SHA256) xfont72.tgz: FAILED > > (SHA256) xserv72.tgz: FAILED > > (SHA256) xshare72.tgz: FAILED > > I see that the sha256 digests/checksums in "SHA256" differ from those of > the downloaded files: > > mjoelnir:_sysupgrade 12.12 13:02:53 [$?==1]# grep bsd.rd SHA256 > > SHA256 (bsd.rd) = > > 9065a190be5eaf047c1c0ece2517712e21964c17f39bebe3420aba2372c054ad > > mjoelnir:_sysupgrade 12.12 13:03:15 # sha256 bsd.rd > > SHA256 (bsd.rd) = > > 84ce928ccf6d71ebe5e7673aa198e424a9fdaf409d64723ba6dc8cd9333d9388 > > I don't know if that's the problem though ... > > I have never really used signify before, but this command from the man > page also generates an error: > > mjoelnir:_sysupgrade 12.12 13:03:30 # signify -C -p > > /etc/signify/openbsd-73-base.pub -x SHA256 > > signify: invalid comment in SHA256; must start with 'untrusted comment: ' > > That file starts like this: > > mjoelnir:_sysupgrade 12.12 13:05:09 # head SHA256 > > SHA256 (BOOTIA32.EFI) = > > e05572dc89a5c2c1ac53962cbf6fecda01dad0d4330d95a27e2d645a63b92d6e > > SHA256 (BOOTX64.EFI) = > > c9cf5ec60caba47c4b4ad0dc37dc88409ff9b5adb38814de1e35496759c2eed8 > > SHA256 (BUILDINFO) = > > 4d0249887ed7db9e9f336556c33a7e66024e08aeb5643f517b98c0815917529b > > ... > > Any suggestions? > > Cheers, > Robb. >
sysupgrade fails with "FAILED" when "verifying sets"?
Hi All, Today sysupgrade failed for me, but I'm not sure why? Here's the output: > # sysupgrade -s -n > Fetching from http://ftp.fau.de/pub/OpenBSD/snapshots/amd64/ > SHA256.sig 100% > |***| > 2144 00:00 > Signature Verified > Verifying old sets. > base72.tgz 100% > |***| >332 MB00:28 > bsd 100% > |***| > 22470 KB00:02 > bsd.mp 100% > |***| > 22578 KB00:02 > bsd.rd 100% > |***| > 4546 KB00:01 > comp72.tgz 100% > |***| > 75019 KB00:07 > game72.tgz 100% > |***| > 2745 KB00:00 > man72.tgz100% > |***| > 7610 KB00:01 > xbase72.tgz 100% > |***| > 52860 KB00:05 > xfont72.tgz 100% > |***| > 22967 KB00:02 > xserv72.tgz 100% > |***| > 14815 KB00:02 > xshare72.tgz 100% > |***| > 4573 KB00:01 > Verifying sets. > (SHA256) base72.tgz: FAILED > (SHA256) bsd: FAILED > (SHA256) bsd.mp: FAILED > (SHA256) bsd.rd: FAILED > (SHA256) comp72.tgz: FAILED > (SHA256) game72.tgz: FAILED > (SHA256) man72.tgz: FAILED > (SHA256) xbase72.tgz: FAILED > (SHA256) xfont72.tgz: FAILED > (SHA256) xserv72.tgz: FAILED > (SHA256) xshare72.tgz: FAILED I see that the sha256 digests/checksums in "SHA256" differ from those of the downloaded files: > mjoelnir:_sysupgrade 12.12 13:02:53 [$?==1]# grep bsd.rd SHA256 > > SHA256 (bsd.rd) = > 9065a190be5eaf047c1c0ece2517712e21964c17f39bebe3420aba2372c054ad > mjoelnir:_sysupgrade 12.12 13:03:15 # sha256 bsd.rd > > SHA256 (bsd.rd) = > 84ce928ccf6d71ebe5e7673aa198e424a9fdaf409d64723ba6dc8cd9333d9388 I don't know if that's the problem though ... I have never really used signify before, but this command from the man page also generates an error: > mjoelnir:_sysupgrade 12.12 13:03:30 # signify -C -p > /etc/signify/openbsd-73-base.pub -x SHA256 > signify: invalid comment in SHA256; must start with 'untrusted comment: ' That file starts like this: > mjoelnir:_sysupgrade 12.12 13:05:09 # head SHA256 > SHA256 (BOOTIA32.EFI) = > e05572dc89a5c2c1ac53962cbf6fecda01dad0d4330d95a27e2d645a63b92d6e > SHA256 (BOOTX64.EFI) = > c9cf5ec60caba47c4b4ad0dc37dc88409ff9b5adb38814de1e35496759c2eed8 > SHA256 (BUILDINFO) = > 4d0249887ed7db9e9f336556c33a7e66024e08aeb5643f517b98c0815917529b > ... Any suggestions? Cheers, Robb.
