Opened 3 years ago

Last modified 14 months ago

#17720 reopened bug

[Website] Fundraising information missing from home-page

Reported by: bipolar Owned by: kallisti5
Priority: normal Milestone: Unscheduled
Component: Website/www.haiku-os.org Version:
Keywords: Cc: leavengood
Blocked By: Blocking:
Platform: All

Description

Since aprox 10 days ago the "Fundraising" info on the haiku-os.org keeps reading "Loading..." forever.

Maybe something got broke on the last repository migration?

Change History (9)

comment:1 by waddlesplash, 3 years ago

Cc: leavengood added
Owner: changed from waddlesplash to kallisti5
Status: newassigned

comment:2 by kallisti5, 3 years ago

The fundraising meter reads a json file from the former cdn.haiku-os.org s3 buckets. I just need to migrate it over to wasabi.

comment:3 by waddlesplash, 3 years ago

And presumably leavengood needs to change whatever regenerates it.

comment:4 by kallisti5, 3 years ago

comment:5 by kallisti5, 3 years ago

And presumably leavengood needs to change whatever regenerates it.

Yeah.. it's a manual process he does. I'll let him know

comment:6 by kallisti5, 3 years ago

Resolution: fixed
Status: assignedclosed

fixed on haiku-os.org and haiku-inc.org

comment:7 by bipolar, 14 months ago

Resolution: fixed
Status: closedreopened

Reopening, as I've just noticed it's happening again.

This time https://s3.us-west-1.wasabisys.com/haiku-inc/donations.json ends up with:

<Error>
<Code>InternalError</Code>
<Message>
We encountered an internal error. Please retry the operation again later.
</Message>
<Detail>
None:GolangError at=metadata_client.(*MetadataV2Client).Get( metadata_client/object-get.go:33 )
</Detail>
<RequestId>4ED87A190A106689:A</RequestId>
<HostId>
Saq7RkDqECrKkGclX3Tg/d6QktsojK3YpDsAhreZai2mKfVxyVRHNeMZzwDBXFQsxj25yD7aSJgv
</HostId>
</Error>

comment:8 by kallisti5, 14 months ago

that's... concerning. We're seeing a different error now:

<Error>
<Code>InternalError</Code>
<Message>We encountered an internal error. Please retry the operation again later.</Message>
<Detail>Could not find pool number 1075 in extent B-886816/O-76034ca026547dbc/S-1</Detail>
<RequestId>B9310B2C07DCE26A:B</RequestId>
<HostId>ext58crGg6Cvyu1l9LqHyq3RGzRAPFwKkzoL8Z9S+gmpoS+9xlKAwXujWOfk+BjfwWq45pgCazxP</HostId>
</Error>

If they're losing our data potentially... it might be time to search for a different object storage provider :-|

Version 0, edited 14 months ago by kallisti5 (next)

comment:9 by kallisti5, 14 months ago

Ah. Support noted Wasabi is having an outage in their us-west-1 region. https://status.wasabi.com

They're investigating. I'll leave this one open to monitor, but it's technically a different issue than this ticket was originally opened for.

*slaps another reason on the list to look at moving us to Storj*

Note: See TracTickets for help on using tickets.