deso-protocol / deso-protocol/core
HyperSync Error
- Dominant language
- Go
- Stars
- 327
- Forks
- 106
- PR merge metrics
- No merged PRs in 30d
Description
I'm trying to get my node back up and running, but having an issue. I keep getting this error: The final db checksum doesn't match the checksum received for the peer. It is likely that HyperSync encountered some unexpected error earlier. You should report this as a issue on DeSo github https://github.com/deso-protocol/core. It is also possible the that peer is misbehaving and sent invalid snapshot chucks. In either way, we'll restart the node and attempt to HyperSync from the beginning.
I have tried to run the following docker command and try again: "docker-compose -f docker-compose.dev.yml down --volumes"
Any ideas on how to resolve this one?
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the HyperSync checksum error with docker-compose.dev.yml and inspect the node logs around the failed peer snapshot. Trace the reported checksum mismatch to the relevant HyperSync code and determine whether the failure is caused by the local node or an invalid peer snapshot. Done means the cause and a verified recovery or fix are documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker-compose, go
- Domain
- distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100