-
Notifications
You must be signed in to change notification settings - Fork 690
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
[Bug]: chain (mainnet) stuck after upgrade to 19.1.0 #3286
Comments
Hi! Thanks for opening an issue. How big is your node instance in TB? The app is likely performing the upgrade. If you have a large node, it will take some time because the database is getting migrated. |
Hey, almost 16TB. Okay, will wait. Thanks! |
It might take quite a while, the entire database is being migrated. Please let us know if there are any issues, we'll keep the issue open. |
looks like migrated, took almost 1.5 hours. Ports are up except rosetta, even it's specified in app.toml, something changed?
|
So, I had to run separate |
Judging by the docs, it's no longer supported in the same way:
Additionally, the config option from |
Is there an existing issue for this?
What happened?
Upgraded to 19.1.0 (used Dockerfile provided in the repo) and after restart chain is stuck with
and I only see more disk consuption, rosetta nor any other service is not started (from /data/config/app.toml)
Gaia Version
19.1.0
How to reproduce?
No response
The text was updated successfully, but these errors were encountered: