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.

Sign up for GitHub

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

Jump to bottom

Fix an issue with nodes failing to keep in sync #4777

Open
SaiProServ opened this issue Jul 1, 2024 · 2 comments
Open

Fix an issue with nodes failing to keep in sync #4777

SaiProServ opened this issue Jul 1, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@SaiProServ
Copy link

An issue has been discovered where nodes fail to keep in sync to tip and fail with a storage error: duplicate entries for blocks for transaction transaction-v1-hash(c3ec..b97f): block-hash(166a..3432) / block-hash(33ec..ba52). This error indicates that we are finding a pre-existing block already containing one of the transactions from a block or execution results that we're writing to LMDB. Initially raised here: https://casper-labs-team.slack.com/archives/C01ULKL8G8J/p1718878384870639.
@devendran-m
Copy link
Contributor

Extract the content from the Slack message - @devendran-m

@devendran-m devendran-m added the bug Something isn't working label Sep 19, 2024
@devendran-m
Copy link
Contributor

Dev to check with Joe S - https://casper-labs-team.slack.com/archives/C01ULKL8G8J/p1718878384870639.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@devendran-m @SaiProServ