-
Notifications
You must be signed in to change notification settings - Fork 103
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
Relations public.Withdrawal and public.Epoch does not exist #897
Comments
Hi @mkocur-ledger I think the issue for the Epoch and withdrawal table missing could be issue with the hasura migration and not the db-sync-snapshot. Can you try to see if there are errors on the graphql-background & hasura while applying the migrations? For the token metadata registry server, are you running the default container as it is from the repo? Table missing seems improbable. |
Hi @Kartiiyer12, thanks for your interest in my bugreport. About the migration, I didn't create any of my own. These are related log messages:
|
These are migration folder that should be applied - https://github.com/cardano-foundation/cardano-graphql/tree/16ed6d71dbe95ff9e7d959ea51a8476da668684c/packages/api-cardano-db-hasura/hasura/project/migrations/default/1589369664961_init. |
I have made a fresh installation and after applying this: https://github.com/cardano-foundation/cf-token-metadata-registry/blob/47f6cf08515f45c3dc11968a7e15a791875cf59c/api/src/main/resources/db/migration/postgresql/V0__metadata_server_db_init.sql I see no errors. Created an issue that it is not applied automatically: About your question, there are customizations, yes, but I can see messages in background pod that it is actually inserting assets and the assets were synced in graphql to 100%, so I assume it works. |
Summary
Hello!
I have restored a snapshot with db-sync:
(https://update-cardano-mainnet.iohk.io/cardano-db-sync/13.5/db-sync-snapshot-schema-13.5-block-10823207-x86_64.tgz)
hasura/graphql-engine:v2.43.0.cli-migrations-v2 is reporting public.Withdrawal and public.Epoch relations missing:
The sync status:
I have restarted graphql, tmr, hasura, background components after the sync was completed to face the same issue.
db-sync: "13.5.0.2"
node: "9.1.1"
ogmios-server: "6.6.2"
graphql-engine: "v2.43.0.cli-migrations-v2"
graphql-server: "8.2.2"
graphql-background: "8.2.2-mainnet"
cf-token-metadata-registry-api: "1.0.2"
postgres: 15.6
Steps to reproduce the bug
No response
Actual Result
Some db data missing after snapshot restore.
Expected Result
No errors
Environment
Kubernetes
{
os: {
arch: 'x64',
cpus: { count: 48, model: 'Intel(R) Xeon(R) Gold 6312U CPU @ 2.40GHz' },
release: '5.15.0-117-generic',
totalMem: 269877899264,
type: 'Linux'
},
version: '8.0.0'
}
Platform
Platform version
Ubuntu 22.04.4 LTS
Runtime
Runtime version
No response
The text was updated successfully, but these errors were encountered: