Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to sync hubble locally #2078

Open
louislucrypto opened this issue Jun 21, 2024 · 5 comments
Open

Unable to sync hubble locally #2078

louislucrypto opened this issue Jun 21, 2024 · 5 comments
Labels
s-triage Needs to be reviewed, designed and prioritized

Comments

@louislucrypto
Copy link

What is the bug?
Following the steps in https://docs.farcaster.xyz/hubble/install#install-via-docker
I'm able to set up hubble and grafana but it alsways failed to sync

Here are the message I got

2024-06-21 00:39:05 {"message":" ███████████████████░░░░░░░░░░░░░░░░░░░░░  47% | Getting snapshot | 1555/3300 | ETA: NFs","timestamp":"2024-06-21T04:39:05.603Z","type":"err","process_id":0,"app_name":"hubble"}
2024-06-21 00:39:05 {"message":"\n","timestamp":"2024-06-21T04:39:05.603Z","type":"err","process_id":0,"app_name":"hubble"}
2024-06-21 00:39:05 {"message":"\n","timestamp":"2024-06-21T04:39:05.604Z","type":"err","process_id":0,"app_name":"hubble"}
2024-06-21 00:39:05 {"message":"\n","timestamp":"2024-06-21T04:39:05.603Z","type":"err","process_id":0,"app_name":"hubble"}
2024-06-21 00:39:05 {"message":"\n","timestamp":"2024-06-21T04:39:05.604Z","type":"err","process_id":0,"app_name":"hubble"}
2024-06-21 00:39:05 {"message":"{\"level\":60,\"time\":1718944745605,\"pid\":29,\"hostname\":\"560f088b6cf1\",\"err\":{\"type\":\"Error\",\"message\":\"Failed to start hub: failed to sync snapshot - Error extracting snapshot\",\"stack\":\"Error: Failed to start hub\\n    at file:///home/node/app/apps/hubble/src/cli.ts:697: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:695:25)\\ncaused by: HubError: failed to sync snapshot - Error extracting snapshot\\n    at Hub.attemptCatchupSyncWithSnapshot (file:///home/node/app/apps/hubble/src/hubble.ts:933:20)\\n    at processTicksAndRejections (node:internal/process/task_queues:95:5)\\n    at Hub.start (file:///home/node/app/apps/hubble/src/hubble.ts:594:27)\\n    at Command.<anonymous> (file:///home/node/app/apps/hubble/src/cli.ts:695:25)\"},\"msg\":\"Failed to start hub\"}\n","timestamp":"2024-06-21T04:39:05.630Z","type":"out","process_id":0,"app_name":"hubble"}
2024-06-21 00:39:05 {"message":"{\"level\":60,\"time\":1718944745630,\"pid\":29,\"hostname\":\"560f088b6cf1\",\"reason\":\"Hub Startup failed\",\"msg\":\"shutting down hub\"}\n","timestamp":"2024-06-21T04:39:05.630Z","type":"out","process_id":0,"app_name":"hubble"}
2024-06-21 00:39:06 {"hostname":"560f088b6cf1","pid":29,"time":1718934081226,"level":30,"msg":"Creating new RocksDB","component":"RustRocksDB","path":".rocks/rocks.hub._default"}
2024-06-21 00:39:06 {"hostname":"560f088b6cf1","pid":29,"time":1718934081226,"level":30,"msg":"Creating new RocksDB","component":"RustRocksDB","path":".rocks/rocks.hub._default/trieDb"}
2024-06-21 00:39:06 {"hostname":"560f088b6cf1","pid":29,"time":1718934081226,"level":30,"msg":"Creating new RocksDB","component":"RustRocksDB","path":".rocks/farcaster"}
2024-06-21 00:39:06 {"hostname":"560f088b6cf1","pid":29,"time":1718934081226,"level":30,"msg":"Creating new RocksDB","component":"RustRocksDB","path":".rocks/rocks.hub._default/trieDb"}
2024-06-21 00:39:06 {"hostname":"560f088b6cf1","pid":29,"time":1718934081226,"level":30,"msg":"Opened database","component":"RustRocksDB","path":".rocks/rocks.hub._default/trieDb"}

My question is why does hubble create a new db when sync failed?
Ideally it should keep original record then continue the sync.
How everytime when it failed, I have to start from 0%

How can it be reproduced? (optional)
Not sure if this occurs to other hub runner

Additional context (optional)
I'm running on f25f133 commit from hub-monorepo
Running docker on windows OS Name Microsoft Windows 11 Home
Docker Engine version is v26.1.4

@github-actions github-actions bot added the s-triage Needs to be reviewed, designed and prioritized label Jun 21, 2024
@louislucrypto
Copy link
Author

I'll try everything again from bca9618 since this is the latest tag.

@stevenjoe0906
Copy link

I'm facing the same issue. It often fails, I have to re-sync from scratch.

@sds
Copy link
Member

sds commented Jul 9, 2024

Thanks for the report, @louislucrypto.

We're aware of an issue where if the connection is lost during the initial snapshot download a RocksDB corruption can occur.

Unclear if this is the same as your issue, but it looks similar. See this comment for context.

@danish46k
Copy link

@sds we all are still getting same error in local machines please do something sir please

@danish46k
Copy link

@sds my pc config
ram=16
ssd=1TB
processors= 6 core
os=ubuntu latest

even i formaed entire ssd just booted with ubuntu latest and tried all things from start but still not able to sync 100% hubble even mine network is also speed and stable why this happining again and again please solve this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
s-triage Needs to be reviewed, designed and prioritized
Projects
None yet
Development

No branches or pull requests

4 participants