-
Notifications
You must be signed in to change notification settings - Fork 123
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
Improve logs when importing postgres archive #1908
Comments
Hello @radicleart ! Probably you are using a wrong db schema. Or even not connected to the Please do the following, inside
and run the queries again using
Thanks. |
So there is no database but i can now see the blocks with the underscores..
I currently have .env with
should they be the same ? |
Thanks for the pointer. I must have the API misconfigured somehow as the api reports zero blocks from my end point and logs the below - I'll clear the stacks data and restart everything from a clean build - will close this later!
|
Should the following be the same - I dropped and recreated the db before starting ? Am wondering if my postgres is misconfigured (i'm new to postgres db).
|
Closing as user error. |
Reopening to document the route cause of this was not having one or both of the below environment vars. Without them the API creates a blank/unnamed schema reads the first block it receives into this schema and then gets stuck on the error
The archive doc implies to start the stacks node before the api node which seems to cause the missing parent block error. The stacks node data postgres data should both be unpacked / loaded but the API should be started before the node. |
Describe the bug
Database in incorrect state after restoring stacks-blockchain-api event data from postgres dump file.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The restore takes several minutes and finishes without error and the size of the database (testnet) is 15G. However the tables contain no data. (Note I had to create the database for pg_restore to run however the dump file attempts to recreate the db);
Console log
Environment:
** Additional Info **
Possibly related to #1908
The text was updated successfully, but these errors were encountered: