Atom Upgrade to v15.0.0 from v14.1.0 not working about gaia HOT 7 CLOSED

Hi @MSalopek and @mpoke node is up and running i guess it is taking too long but got started thanks

from gaia.

I am trying to upgrade my mainnet archival atom node from v14.1.0 to v15.0.0.

@mayank-daga Please note that v15.0.0 is deprecated and you should use v15.1.0 instead. Also, you should upgrade from v14.2.0. For more details, please check out the upgrading instructions.

from gaia.

Hi @mpoke thanks for the info i will try that also one more question do we need to download latest archive snapshot as my node was synced to latest?

from gaia.

Hi @mpoke I upgraded to first v14.2.0 and then tried to upgrade to v15.1.0. I am getting the same issue

from gaia.

The upgrade is taking a long time, the software is performing a large upgrade.

The upgrade can take a long time, and unfortunately there's nothing in the log output (that's outside of cosmos-hub scope).

For me, upgrading a 1TB node (custom pruning) took almost 2 hours. If you're upgrading an archive it will take longer - please don't shut down the node an let it complete the upgrade. If you have heartbeats/healthchecks please turn them off.

To create the .gaia folder inside ran below command:
sudo docker run -it -p 26657:26657 -p 26656:26656 -v //node-atom/gaia/.gaia:/gaia/.gaia gaia:latest gaiad init tenatom > --chain-id cosmoshub-4
Was getting one error here:

Error: unknown flag: --chain-id

Checked locally, there does not seem to be an issue with chain-id on either gaiad v15.1.0 or v14.2.0.
I was able to run gaiad init testing --home .gaiad-test --chain-id cosmoshub-4

Were you able to resolve your issue?

from gaia.

No @MSalopek I was not able to resolve the issue also the docker container was up till 2 days but still no logs was produced

from gaia.

Do you have any metrics or insight into the process? Can you check that the process is doing something and it hasn't died on startup?

from gaia.