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

ark snapshot:restore fails #3467

Closed
Lemii opened this issue Feb 12, 2020 · 13 comments
Closed

ark snapshot:restore fails #3467

Lemii opened this issue Feb 12, 2020 · 13 comments

Comments

@Lemii
Copy link
Contributor

Lemii commented Feb 12, 2020

When trying to restore a snapshot with the ARK cli, it consistently fails with the following:

█░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ 1% | ETA: 567s | 52457/3896400 | Duration: 8serror: invalid input syntax for type bytea
    at Connection.parseE (~/.config/yarn/global/node_modules/pg/lib/connection.js:602:11)
    at Connection.parseMessage (~/.config/yarn/global/node_modules/pg/lib/connection.js:399:19)
    at Socket.<anonymous> (~/.config/yarn/global/node_modules/pg/lib/connection.js:121:22)

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

  • Version used: 2.6.1
  • Environment name and version: nodejs 12.15.0
  • Server type and version: linux-x64
  • Operating System and version: Ubuntu 18.04
@ghost
Copy link

ghost commented Feb 12, 2020

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.

@espresso-time
Copy link

For reference, here is the snapshot... https://send.firefox.com/download/7f7673d48264b387/#OaHMsSA6flbJSuU7gcIbYA

(it expires in 6 days or after 100 downloads)

@Lemii
Copy link
Contributor Author

Lemii commented Feb 12, 2020

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).

@faustbrian
Copy link
Contributor

Most likely related to #3048.

@faustbrian
Copy link
Contributor

@espresso-time at around which height does the restoration fail? I am using your snapshot and currently at 2.2 million blocks.

@espresso-time
Copy link

@faustbrian I did not restore the snapshot myself, but @Lemii reported that it fails with the transaction import.

@faustbrian
Copy link
Contributor

@Lemii does the restoration always die at the same block/transaction?

@Lemii
Copy link
Contributor Author

Lemii commented Feb 12, 2020

@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).

@faustbrian
Copy link
Contributor

faustbrian commented Feb 12, 2020

Will try to reproduce it but the snapshot above restored just fine. Was the snapshot created pre or post 2.6?

@espresso-time
Copy link

@faustbrian post 2.6

@alessiodf
Copy link
Contributor

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.

@faustbrian
Copy link
Contributor

Closing, will be addressed in 3.0. Won't fix this in 2.0.

@ghost
Copy link

ghost commented Oct 16, 2020

This issue has been closed. If you wish to re-open it please provide additional information.

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

5 participants