vrypan |--o--|
@vrypan.eth
The Hubble problems saga goes on :-( Re-installing from scratch. New vps, new install. https://download.farcaster.xyz/snapshots/MAINNET/DB_SCHEMA_10/latest.json returns 404. @v @sanjay, something is going on, it doesn't;t seem that this is on my side...
1 reply
1 recast
12 reactions
Varun Srinivasan
@v
Looking
1 reply
0 recast
1 reaction
vrypan |--o--|
@vrypan.eth
Any luck?
1 reply
0 recast
0 reaction
Sanjay
@sanjay
Look like there's an issue with the hub that generates the snapshots. We're fixing, hope to have the latest snapshot uploaded later today.
1 reply
0 recast
2 reactions
christopher
@christopher
CATCHUP_SYNC_WITH_SNAPSHOT=false should temporarily resolve this blocker.
2 replies
0 recast
0 reaction
vrypan |--o--|
@vrypan.eth
Found it in docker-compose.yaml, thanks.
1 reply
0 recast
0 reaction
Sanjay
@sanjay
Not that if it's a brand new hub, I think it will still fail. The flag is only for catchup sync. You have to pass the `--disable-snapshot-sync` cli flag to bypass snapshot entirely (and it will start with no data). I would wait for the snapshots to be fixed if it's a new hub.
2 replies
0 recast
2 reactions
christopher
@christopher
Snapshot 404 again this morning fyi.
1 reply
0 recast
0 reaction
Sanjay
@sanjay
Looking
1 reply
0 recast
1 reaction
Sanjay
@sanjay
Hmm, people are out today. I don't have an ETA for the fix. I suggest working around this for now by disabling snapshot sync. I'll set up on some alerts so we can catch this before the snapshot expires next time.
1 reply
0 recast
0 reaction
christopher
@christopher
All good with me. We run redundant hubs and turned off catch up sync due to the last incident. But worth noting for others folks running their own or starting anew.
1 reply
0 recast
2 reactions
