Skip to content
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

Open
1 task done
tmeinlschmidt opened this issue Aug 21, 2024 · 6 comments
Open
1 task done

[Bug]: chain (mainnet) stuck after upgrade to 19.1.0 #3286

tmeinlschmidt opened this issue Aug 21, 2024 · 6 comments
Assignees
Labels
status: waiting-triage This issue/PR has not yet been triaged by the team. type: bug Issues that need priority attention -- something isn't working

Comments

@tmeinlschmidt
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

What happened?

Upgraded to 19.1.0 (used Dockerfile provided in the repo) and after restart chain is stuck with

3:07PM INF packet sent dst_channel=channel-0 dst_port=consumer module=x/ibc/channel sequence=2059900 src_channel=channel-568 src_port=provider
3:07PM INF packet sent dst_channel=channel-146 dst_port=consumer module=x/ibc/channel sequence=1738960 src_channel=channel-635 src_port=provider

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

@tmeinlschmidt tmeinlschmidt added status: waiting-triage This issue/PR has not yet been triaged by the team. type: bug Issues that need priority attention -- something isn't working labels Aug 21, 2024
@tmeinlschmidt tmeinlschmidt changed the title [Bug]: chain stuck after upgrade to 19.1.0 [Bug]: chain (mainnet) stuck after upgrade to 19.1.0 Aug 21, 2024
@MSalopek
Copy link
Contributor

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.

@tmeinlschmidt
Copy link
Author

Hey, almost 16TB. Okay, will wait. Thanks!

@MSalopek
Copy link
Contributor

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.

@tmeinlschmidt
Copy link
Author

looks like migrated, took almost 1.5 hours. Ports are up except rosetta, even it's specified in app.toml, something changed?

[rosetta]

# Enable defines if the Rosetta API server should be enabled.
enable = true

# Address defines the Rosetta API server to listen on.
address = "127.0.0.1:8545"

# Network defines the name of the blockchain that will be returned by Rosetta.
blockchain = "cosmos"

# Network defines the name of the network that will be returned by Rosetta.
network = "mainnet"

@tmeinlschmidt
Copy link
Author

So, I had to run separate gaiad rosetta to enable rosetta then, even it has the configuration entry in app.toml. Is that expected? It did work in 18.1.0

@MSalopek
Copy link
Contributor

So, I had to run separate gaiad rosetta to enable rosetta then, even it has the configuration entry in app.toml. Is that expected? It did work in 18.1.0

Judging by the docs, it's no longer supported in the same way:

Additionally, the config option from app.toml is not available if you do gaiad init <moniker>, you probably have it left over from your old config.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: waiting-triage This issue/PR has not yet been triaged by the team. type: bug Issues that need priority attention -- something isn't working
Projects
Status: 🏗 F3: InProgress
Development

No branches or pull requests

2 participants