-
Notifications
You must be signed in to change notification settings - Fork 118
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
nft_custody table index crashes #1881
Comments
@bestmike007 It looks like there are some special considerations to take into account when performing a pg backup directly from a data dir as you're doing here that can cause problems in restorations, such as certain files and directories to omit from the backup. Are you able to try restoring your data using one of Hiro's archives via |
What's wrong with the cold backup? https://www.postgresql.org/docs/current/backup-file.html#BACKUP-FILE |
update: after applying those 2 PRs and redo the steps, there were still those similar errors but it went through. Let me redo it again with the official image. |
I understand that this is an issue with setup rather than the API. Closing for now. Please reach out on Discord if this is still an issue. |
Describe the bug
api process crashes with error:
duplicate key value violates unique constraint nft_custody_unique
ortable tid from new index tuple (13373,41) overlaps with invalid duplicate tuple at offset 4 of block 6211 in index nft_custody_recipient_asset_identifier_index
@rafaelcr @CharlieC3
To Reproduce
Steps to reproduce the behavior:
setup.sh
, and restore the backup from https://github.com/alexgo-io/stacks-node-mainnet/releases/tag/block-140976docker-compose up -d stacks-blockchain-postgres
select asset_identifier, value, count(*) from nft_custody group by 1,2 having count(*) > 1;
./start.sh
watch 'curl -s http://127.0.0.1:3999/extended/v1/status'
docker logs -f --tail=100 stacks_api
You might possibly run into another issue described in #1878
Expected behavior
Stacks node sync until it reaches tip.
Screenshots
Screenshot from step 3:
Screenshot from step 7:
Screenshot from step 8:
Console log
N/A
Additional context
The vm I'm using to run the steps: 4vCPU, 16G memory, 320GB disk
The text was updated successfully, but these errors were encountered: