Opened 4 years ago

Last modified 4 years ago

#16928 new bug

Haiku Repository Unavailable

Reported by: jmontleon Owned by: haiku-web
Priority: normal Milestone: Unscheduled
Component: Sys-Admin Version: R1/beta2
Keywords: Cc:
Blocked By: Blocking:
Platform: All

Description

Starting last evening I have been receiving errors when trying to refresh or re-add the Haiku repo.

In all cases it is similar to this, whether trying to use r1beta2 or master.

pkgman add-repo https://eu.hpkg.haiku-os.org/haiku/r1beta2/x86_64/current
Fetching repository info from https://eu.hpkg.haiku-os.org/haiku/r1beta2/x86_64/current ...
*** failed! : I/O error

Change History (1)

comment:1 by kallisti5, 4 years ago

Here's a rundown of what happened:

In 2018 when we decided to use wasabi.com for hosting our artifacts, they had a policy of unlimited egress traffic. As of April 26th, they walked back that commitment and shut down egress traffic on our buckets for using too much bandwidth. We store around 1TiB of data, and have 3TiB of monthly outbound traffic.

Wasabi tech support has temporarily removed the egress block, but I feel like we're going to run into it again.

Here is some scope information:

  • Haiku master/r1beta1/r1beta2 repos
    • Where: Wasabi s3
    • What: Haiku's core update repositories
    • Signed: Yes. minisig on repo file
  • Haiku nightly images
    • Where: Wasabi s3
    • What: Haiku's nightly builds
    • Signed: Yes. minisig on artifacts
  • Haikuports repo - Our own server
    • Where: Digital Ocean block volume
    • What: Haikuports repos
    • Signed: No
  • Haiku releases - Wasabi s3 (US), our own server (EU), generous mirrors
    • Where: Wasabi S3, Digital Ocean block volume, rsync Mirrors
    • What: Haiku releases (r1beta2, etc)
    • Signed: Yes. minisig on artifacts

Anything on "Wasabi S3" was impacted, including the financial tracker on haiku-inc.org.

We really can't depend on external rsync mirrors until every repository is signed *AND* haikuporter gets some signature checking ability.

I've been panic mirroring our Haiku repos from Wasabi onto IPFS as a temporary measure incase they pull down access again. (IPFS has deduplication, easy mirroring, *AND* transparent signature checking. You can access the US gateway here: https://us.hpkg.haiku-os.org (and notes on how to use it here: https://us.hpkg.haiku-os.org/readme.html). Be gentle on this mirror... it is currently only pinned a personal VM and my home NAS :-D. If you use IPFS, please help out and occasionally re-pin /ipns/us.hpkg.haiku-os.org

"haikuports" is empty there since my only focus at the moment is stuff on Wasabi.

So.. this issue isn't solved yet, but we're working on backup options incase this stuff goes down again.

Note: See TracTickets for help on using tickets.