-
Notifications
You must be signed in to change notification settings - Fork 58
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
[documentation] Restoring api node #637
Comments
UPDATE Just noticed the api 7.9 releases tagged with nakamoto - after dropping back to 7.8.2.
|
Found some new instructions - closing this for now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hey!
Running into difficulties following this guide on restoring from archived data
Ubuntu: 23.10
Stacks-node: stacks-core-2.4.0.1.0 (my node reports
stacks-node 0.0.1 (:, debug build, linux [x86_64])
?)Stacks-blockchain-api: 7.9.0
Postgres: 15
I running stacks-node and postgres as services on the host and the api in docker (have tried several combinations).
Restore using pg_restore
Couple of issues;
stacks_blockchain_api
db but noticed a line in the restore log that errors when it also tries to create the databasepg_restore
runs to completion and on spinning up the node I see correct tip height here: http://leibniz.brightblock.org:3999/v2/info BUT do not see the contract info e.g. http://leibniz.brightblock.org:3999/extended/v1/contract/ST1R1061ZT6KPJXQ7PAXPFB6ZAZ6ZWW28G8HXK9G5.asset-3Restore using tsv import
I tried importing the tsv file using;
node ./lib/index.js import-events --file /mnt/stacks-testnet/archives/testnet-stacks-blockchain-api-7.8.2-20240322.tsv --wipe-db --force
but get;
any help would be great - I've tried syncing from genesis using docker containers but never managed to catch up wth the (mainnet) tip height.
The text was updated successfully, but these errors were encountered: