#node stuck after snapshot restore

1 messages ยท Page 1 of 1 (latest)

glossy talon
#

hey guys, i'm trying to restore from snapshot of Polkachu (I need an archive node), but my node is crashing in the crediting part - has anyone had a similar problem after the hard fork?

INFO namada_node:๐Ÿš:init_chain: Crediting 106.880076 nam tokens to tnam1qzzzpksl4lym3wy2gp0j8c7rvgtjrqdhwusruc3s
INFO namada_node:๐Ÿš:init_chain: Crediting 106.880076 nam tokens to tnam1qzzzqjs4kjcpghvsgdz0yjr7f5zmsxww8vl0gjgs
INFO namada_node:๐Ÿš:init_chain: Crediting 106.880076 nam tokens to tnam1qzzzrfwwyv0kz5svprr428t05fwhu7rq5u89sxgm
INFO namada_node:๐Ÿš:init_chain: Crediting 135.922579 nam tokens to tnam1qzzzt8mk8ynxfhyae6rcadtcwshssrkcw5j3a5kt

south rover
#

you have appropriate peers etc?

#

or um. I don't think it should do the crediting part if you properly restored a snapshot

#

you sure you placed everything correctly?

#

would maybe try another snapshot if so

glossy talon
south rover
#

I assume you kept all your original config and replaced only db state and cometbft data directories?

#

is this a validator or full node? what do you use it for? (rpc or other?)

#

or are you wanting to set up an entirely new node that has not ran before?

glossy talon
#

oh, i'm using cosmos-operator and restoring using scripts from a URL (running inside k8s)
it's a full node, we're using to maintain the archive data
this problem occurred after the hard fork, this complete node had been running for over a year

south rover
#

what was the problem you incurred?

south rover
south rover
#

(namada is more customized than most other cosmos chains)

glossy talon