Fetching most recent snapshot ... Trying to retrieve 20170918 snapshot from http://mirror.eu.oneandone.net/linux/distributions/gentoo/gentoo ... Fetching file portage-20170918.tar.bz2.md5sum ... Redirecting output to 'wget-log'. Fetching file portage-20170918.tar.gz.md5sum ...
Working again. So it seems just one day was skipped?
We are again missing snapshot for 20180304, I see infra-status.g.o isn't green. Since this bug is not closed, I'll re-use it (if someone could change its summary please?)
(In reply to Branko Grubic from comment #2) > We are again missing snapshot for 20180304, I see infra-status.g.o isn't > green. Since this bug is not closed, I'll re-use it (if someone could change > its summary please?) The box was dead over night so it did not generate a snapshot. I presume it will generate one for the next day.
Hi Alec, Snapshot is missing this morning again. Can someone trigger it manually for now? It would be nice if possible to run the job few times a day, in case machine was down ..., so it could generate a missing snapshot?
(In reply to Branko Grubic from comment #4) > Hi Alec, > > Snapshot is missing this morning again. Can someone trigger it manually for > now? It would be nice if possible to run the job few times a day, in case > machine was down ..., so it could generate a missing snapshot? I will generate a snapshot for 0305 (today.) There will not be snapshots for previous days; I think that is OK (the delta will be bigger but clients should use the latest snapshot.) We can certainly modify the script to not require manual action during downtime (its a fairly trivial change.) I'm less convinced its a great idea to try 3-4 times to make a snapshot (I'd rather skip a day and just make one the next day, rather than make the script over complicated.) But I'll discuss it with the team.
I filed: https://bugs.gentoo.org/649754 for some scripting improvements.
Hi Alec, It seems that today's snapshot isn't good, I tried it, gpg verification passed, but then tar complained. Since this is detached gpg signature of tar archive I guess there is no need to re-verify checksums, if something changes signature verification will fail as well? Fetching most recent snapshot ... Trying to retrieve 20180305 snapshot from http://mirror.yandex.ru/gentoo-distfiles ... Fetching file portage-20180305.tar.xz.md5sum ... Fetching file portage-20180305.tar.xz.gpgsig ... Fetching file portage-20180305.tar.xz ... Checking digest ... Checking signature ... gpg: Signature made Tue 06 Mar 2018 04:52:37 PM CET gpg: using RSA key E1D6ABB63BFCFB4BA02FDF1CEC590EEAC9189250 gpg: Good signature from "Gentoo Portage Snapshot Signing Key (Automated Signing Key)" [ultimate] Getting snapshot timestamp ... tar: Unexpected EOF in archive tar: Error is not recoverable: exiting now Syncing local tree ... tar: Unexpected EOF in archive tar: Unexpected EOF in archive tar: Error is not recoverable: exiting now emerge-webrsync: error: tar failed to extract the image. tarball is corrupt? (/var/tmp/portage/webrsync-Hb9bTN/portage-20180305.tar.xz)
(In reply to Branko Grubic from comment #7) > Hi Alec, > > It seems that today's snapshot isn't good, I tried it, gpg verification > passed, but then tar complained. Since this is detached gpg signature of tar > archive I guess there is no need to re-verify checksums, if something > changes signature verification will fail as well? > > Fetching most recent snapshot ... > Trying to retrieve 20180305 snapshot from > http://mirror.yandex.ru/gentoo-distfiles ... > Fetching file portage-20180305.tar.xz.md5sum ... > Fetching file portage-20180305.tar.xz.gpgsig ... > Fetching file portage-20180305.tar.xz ... > Checking digest ... > Checking signature ... > gpg: Signature made Tue 06 Mar 2018 04:52:37 PM CET > gpg: using RSA key E1D6ABB63BFCFB4BA02FDF1CEC590EEAC9189250 > gpg: Good signature from "Gentoo Portage Snapshot Signing Key (Automated > Signing Key)" [ultimate] > Getting snapshot timestamp ... > tar: Unexpected EOF in archive > tar: Error is not recoverable: exiting now > Syncing local tree ... > tar: Unexpected EOF in archive > tar: Unexpected EOF in archive > tar: Error is not recoverable: exiting now > emerge-webrsync: error: tar failed to extract the image. tarball is corrupt? > (/var/tmp/portage/webrsync-Hb9bTN/portage-20180305.tar.xz) Ack, I can't work on it for a while (at the office) but I'll poke it again tonight.
(In reply to Alec Warner from comment #8) > (In reply to Branko Grubic from comment #7) > > Hi Alec, > > > > It seems that today's snapshot isn't good, I tried it, gpg verification > > passed, but then tar complained. Since this is detached gpg signature of tar > > archive I guess there is no need to re-verify checksums, if something > > changes signature verification will fail as well? > > > > Fetching most recent snapshot ... > > Trying to retrieve 20180305 snapshot from > > http://mirror.yandex.ru/gentoo-distfiles ... > > Fetching file portage-20180305.tar.xz.md5sum ... > > Fetching file portage-20180305.tar.xz.gpgsig ... > > Fetching file portage-20180305.tar.xz ... > > Checking digest ... > > Checking signature ... > > gpg: Signature made Tue 06 Mar 2018 04:52:37 PM CET > > gpg: using RSA key E1D6ABB63BFCFB4BA02FDF1CEC590EEAC9189250 > > gpg: Good signature from "Gentoo Portage Snapshot Signing Key (Automated > > Signing Key)" [ultimate] > > Getting snapshot timestamp ... > > tar: Unexpected EOF in archive > > tar: Error is not recoverable: exiting now > > Syncing local tree ... > > tar: Unexpected EOF in archive > > tar: Unexpected EOF in archive > > tar: Error is not recoverable: exiting now > > emerge-webrsync: error: tar failed to extract the image. tarball is corrupt? > > (/var/tmp/portage/webrsync-Hb9bTN/portage-20180305.tar.xz) > > Ack, I can't work on it for a while (at the office) but I'll poke it again > tonight. Ok I think I determined why the tarball was cutoff (error on my part.) I've wiped the snapshots and redid them. Maybe wait 30-60 minutes for mirror propagation and try again. I'm also working on some script changes to make the mirror scripts somewhat less error prone.
(In reply to Alec Warner from comment #9) ... > > Ok I think I determined why the tarball was cutoff (error on my part.) I've > wiped the snapshots and redid them. Maybe wait 30-60 minutes for mirror > propagation and try again. > > I'm also working on some script changes to make the mirror scripts somewhat > less error prone. Thank you Alec, latest snapshot is OK!
(In reply to Branko Grubic from comment #10) > (In reply to Alec Warner from comment #9) > ... > > > > Ok I think I determined why the tarball was cutoff (error on my part.) I've > > wiped the snapshots and redid them. Maybe wait 30-60 minutes for mirror > > propagation and try again. > > > > I'm also working on some script changes to make the mirror scripts somewhat > > less error prone. > > Thank you Alec, latest snapshot is OK! Great thanks, I'll push script updates in the other bug I mentioned to try to avoid it breaking in the future. -A
