-
Notifications
You must be signed in to change notification settings - Fork 71
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
Starting node from a snapshot fails if the node has no blocks #1228
Closed
Milestone
Comments
@RalfWeinand can you share the command and |
heifner
added a commit
that referenced
this issue
Jun 14, 2023
heifner
added a commit
that referenced
this issue
Jun 14, 2023
heifner
added a commit
that referenced
this issue
Jun 14, 2023
heifner
added a commit
that referenced
this issue
Jun 14, 2023
heifner
added a commit
that referenced
this issue
Jun 14, 2023
[4.0] Fix for loading snapshot with empty block log
heifner
added a commit
that referenced
this issue
Jun 14, 2023
heifner
added a commit
that referenced
this issue
Jun 14, 2023
heifner
added a commit
that referenced
this issue
Jun 14, 2023
heifner
added a commit
that referenced
this issue
Jun 14, 2023
[4.0 -> main] Fix for loading snapshot with empty block log
heifner
added a commit
that referenced
this issue
Jun 14, 2023
heifner
added a commit
that referenced
this issue
Jun 15, 2023
heifner
added a commit
that referenced
this issue
Jun 15, 2023
heifner
added a commit
that referenced
this issue
Jun 15, 2023
heifner
added a commit
that referenced
this issue
Jun 15, 2023
[4.0] Fix for loading a snapshot with an empty block log but an existing fork database
heifner
added a commit
that referenced
this issue
Jun 15, 2023
heifner
added a commit
that referenced
this issue
Jun 15, 2023
[4.0 -> main] Fix for loading a snapshot with an empty block log but an existing fork database
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We just noticed an issue with Leap v4.0.1 when we created a new Telos Testnet BP node. Starting it from a snapshot (without any blocks in the blocks folder) resulted in this error.
We tried different snapshots, and different config.ini settings & start parameters (e.g. --delete-all-blocks) but nothing helped.
We then downgraded to Leap v3.2.3 and nodeos started from the same snapshot without blocks without this error.
The text was updated successfully, but these errors were encountered: