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

Remote BN does not support EIP-4881 fast deposit sync, error: Error fetching deposit snapshot from remote #4559

Closed
icculp opened this issue Aug 1, 2023 · 7 comments

Comments

@icculp
Copy link

icculp commented Aug 1, 2023

Description

Aug 01 19:04:18.954 WARN Remote BN does not support EIP-4881 fast deposit sync, error: Error fetching deposit snapshot from remote: ServerMessage(ErrorMessage { code: 500, message: "not found", stacktraces: [] }), service: beacon
Aug 01 19:04:18.968 CRIT Failed to start beacon node             reason: Error fetching finalized block from remote: ServerMessage(ErrorMessage { code: 500, message: "not found", stacktraces: [] })

Version

Nethermind 1.20.1, lighthouse 4.3.0, gnosis mainnet

Present Behaviour

Unable to checkpoint sync

Expected Behaviour

Beacon should sync properly

Steps to resolve

Have tried multiple urls, all result in same error.

@icculp
Copy link
Author

icculp commented Aug 1, 2023

Btw, here it says lighthouse will ignore the warning and try syncing from scratch:

https://rustrepo.com/repo/sigp-lighthouse-rust-concurrency

But in my case it does not, it just shuts down. Have to remove checkpoint-sync-url flag to start syncing from scratch

Aug 01 19:04:18.954 WARN Remote BN does not support EIP-4881 fast deposit sync, error: Error fetching deposit snapshot from remote: ServerMessage(ErrorMessage { code: 500, message: "not found", stacktraces: [] }), service: beacon
Aug 01 19:04:18.968 CRIT Failed to start beacon node             reason: Error fetching finalized block from remote: ServerMessage(ErrorMessage { code: 500, message: "not found", stacktraces: [] })
Aug 01 19:04:18.968 INFO Internal shutdown received              reason: Failed to start beacon node
Aug 01 19:04:18.968 INFO Shutting down..                         reason: Failure("Failed to start beacon node")
Failed to start beacon node```

@jimmygchen
Copy link
Member

This seems to be a checkpoint sync server issue, also reported by a few other Discord users. This log line suggested that the checkpoint server returned a server error:

Aug 01 19:04:18.968 CRIT Failed to start beacon node             reason: Error fetching finalized block from remote: ServerMessage(ErrorMessage { code: 500, message: "not found", stacktraces: [] })

@jimmygchen
Copy link
Member

Perhaps try another gnosis checkpoint server or reach out to them on Discord?

@dharmendrakariya
Copy link

I deleted the Consensus data and restarted the node



023-08-04 18:34:22 | Aug 04 13:04:22.506 INFO Ready for Capella                       info: ensure the execution endpoint is updated to the latest Capella/Shanghai release, service: slot_notifier
-- | --
2023-08-04 18:34:27 | Aug 04 13:04:27.501 INFO Syncing                                 est_time: 4 days 4 hrs, speed: 17.65 slots/sec, distance: 6362265 slots (52 weeks 4 days), peers: 9, service: slot_notifier
2023-08-04 18:34:27 | Aug 04 13:04:27.502 WARN Syncing deposit contract block cache    est_blocks_remaining: initializing deposits, service: slot_notifier
2023-08-04 18:34:27 | Aug 04 13:04:27.504 INFO Ready for the merge                     current_difficulty: 8626000110427538733349499292577475819600160930, terminal_total_difficulty: 8626000000000000000000058750000000000000000000, service: slot_notifier
2023-08-04 18:34:27 | Aug 04 13:04:27.505 INFO Ready for Capella                       info: ensure the execution endpoint is updated to the latest Capella/Shanghai release, service: slot_notifier
2023-08-04 18:34:27 | Aug 04 13:04:27.790 WARN Execution endpoint is not synced        last_seen_block_unix_timestamp: 1690992200, endpoint: http://erigon:8551/, auth=true, service: deposit_contract_rpc
2023-08-04 18:34:27 | Aug 04 13:04:27.791 ERRO Error updating deposit contract cache   error: Failed to get remote head and new block ranges: EndpointError(FarBehind), retry_millis: 60000, service: deposit_contract_rpc
2023-08-04 18:34:32 | Aug 04 13:04:32.500 INFO Syncing                                 est_time: 4 days 4 hrs, speed: 17.61 slots/sec, distance: 6362170 slots (52 weeks 4 days), peers: 9, service: slot_notifier
2023-08-04 18:34:32 | Aug 04 13:04:32.500 WARN Syncing deposit contract block cache    est_blocks_remaining: initializing deposits, service: slot_notifier
2023-08-04 18:34:32 | Aug 04 13:04:32.504 INFO Ready for the merge                     current_difficulty: 8626000110427538733349499292577475819600160930, terminal_total_difficulty: 8626000000000000000000058750000000000000000000, service: slot_notifier
2023-08-04 18:34:32 | Aug 04 13:04:32.505 INFO Ready for Capella                       info: ensure the execution endpoint is updated to the latest Capella/Shanghai release, service: slot_notifier

could you verify the logs please?

@jimmygchen
Copy link
Member

Hi @dharmendrakariya I'm not sure what chain you're syncing to but the above logs look ok, looks like it's syncing from genesis and not via checkpoint sync, so it seems unrelated to this issue.

@dharmendrakariya
Copy link

@jimmygchen thanks buddy! btw I am working on Gnosis!

@jimmygchen
Copy link
Member

Looks like this was a checkpoint sync server issue (see discussions in #2915 ) and should be fixed now, closing this one now. Thanks for reporting!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants