-
Notifications
You must be signed in to change notification settings - Fork 286
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
ark snapshot:restore fails #3467
Comments
Thanks for opening this issue! A maintainer will review this in the next few days and explicitly select labels so you know what's going on. If no reviewer appears after a week, a reminder will be sent out. |
For reference, here is the snapshot... https://send.firefox.com/download/7f7673d48264b387/#OaHMsSA6flbJSuU7gcIbYA (it expires in 6 days or after 100 downloads) |
If needed I can supply the other two snapshots as well, but I suspect them to be nearly identical (except for block height). |
Most likely related to #3048. |
@espresso-time at around which height does the restoration fail? I am using your snapshot and currently at 2.2 million blocks. |
@faustbrian I did not restore the snapshot myself, but @Lemii reported that it fails with the transaction import. |
@Lemii does the restoration always die at the same block/transaction? |
@faustbrian I can not say for sure because I have not written down the block height. However, I can confirm it happens very early on the transactions import (less than 30 seconds). |
Will try to reproduce it but the snapshot above restored just fine. Was the snapshot created pre or post 2.6? |
@faustbrian post 2.6 |
Any progress on this? I can't restore snapshots either, even ones made using a fresh installation of the latest version of Core on a brand new server. |
Closing, will be addressed in 3.0. Won't fix this in 2.0. |
This issue has been closed. If you wish to re-open it please provide additional information. |
When trying to restore a snapshot with the ARK cli, it consistently fails with the following:
Step one, block import, seems to work OK. After that, when it tries to import the transactions table, the error shown above is thrown.
I have attempted restores with a combination of 3 different snapshots (from different sources) and 5 different VPS'.
Your Environment
The text was updated successfully, but these errors were encountered: