-
Notifications
You must be signed in to change notification settings - Fork 514
Closed
Labels
s-triageNeeds to be reviewed, designed and prioritizedNeeds to be reviewed, designed and prioritized
Description
What is the bug?
Crash on start after updating hubble to 1.15.7
{
"app_name": "hubble",
"message": {
"level": 60,
"time": 1729898201744,
"pid": 29,
"hostname": "farcaster-hubble-0",
"err": {
"type": "Error",
"message": "Failed to start hub: failed to fetch snapshot metadata - Failed to get latest snapshot from https://download.farcaster.xyz/snapshots/MAINNET/DB_SCHEMA_11/latest.json [AxiosError: Request failed with status code 404]",
"stack": "Error: Failed to start hub\n at file:///home/node/app/apps/hubble/src/cli.ts:682:14\n at /home/node/app/node_modules/neverthrow/dist/index.cjs.js:113:102\n at processTicksAndRejections (node:internal/process/task_queues:95:5)\n at Command.<anonymous> (file:///home/node/app/apps/hubble/src/cli.ts:680:25)\ncaused by: HubError: failed to fetch snapshot metadata - Failed to get latest snapshot from https://download.farcaster.xyz/snapshots/MAINNET/DB_SCHEMA_11/latest.json [AxiosError: Request failed with status code 404]\n at Hub.attemptCatchupSyncWithSnapshot (file:///home/node/app/apps/hubble/src/hubble.ts:934:18)\n at processTicksAndRejections (node:internal/process/task_queues:95:5)\n at Hub.start (file:///home/node/app/apps/hubble/src/hubble.ts:631:27)\n at Command.<anonymous> (file:///home/node/app/apps/hubble/src/cli.ts:680:25)"
},
"msg": "Failed to start hub"
},
"process_id": 0,
"timestamp": "2024-10-25T23:16:41.788Z",
"type": "out"
}How can it be reproduced? (optional)
Accessed link https://download.farcaster.xyz/snapshots/MAINNET/DB_SCHEMA_11/latest.json , returned 404
Additional context (optional)
none
bibo7086
Metadata
Metadata
Assignees
Labels
s-triageNeeds to be reviewed, designed and prioritizedNeeds to be reviewed, designed and prioritized