join-network config

[toxic girder]

You know we don't have any tickets

did you forget to set the config server variable before running join-network?

[harsh abyss]

the default config server URL is out of date

https://github.com/namada-net/namada/blob/b3e1baeef43fd6035c7cfd27abd19da400c6bbd6/crates/apps_lib/src/client/utils.rs#L51

[toxic girder]

we never used default config server url, always had to be set manually afaik, and this is reflected in manuals I believe

join-network config

[harsh abyss]

@vague nexus try:

export CHAIN_ID="namada.5f5de2dd1b88cba30586420"
export NAMADA_NETWORK_CONFIGS_SERVER="https://github.com/namada-net/namada-mainnet-genesis/releases/download/mainnet-genesis"
namada client utils join-network --chain-id $CHAIN_ID --add-persistent-peers

edit: fixed broken download URL

[vague nexus]

root@Ubuntu-2404-noble-amd64-base ~ # export CHAIN_ID="namada.5f5de2dd1b88cba30586420"
root@Ubuntu-2404-noble-amd64-base ~ # export NAMADA_NETWORK_CONFIGS_SERVER="https://github.com/namada-net/namada-mainnet-genesis/releases/tag/mainnet-genesis"
root@Ubuntu-2404-noble-amd64-base ~ # namada client utils join-network --chain-id $CHAIN_ID --add-persistent-peers
Downloading config release from https://github.com/namada-net/namada-mainnet-genesis/releases/tag/mainnet-genesis/namada.5f5de2dd1b88cba30586420.tar.gz ...
The application panicked (crashed).
Message: called Result::unwrap() on an Err value: Custom { kind: InvalidInput, error: TarError { desc: "failed to iterate over archive", io: Custom { kind: InvalidInput, error: "invalid gzip header" } } }
Location: /home/runner/work/namada/namada/crates/apps_lib/src/client/utils.rs:163

Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.

[harsh abyss]

apologies, I used a bad URL prefix, (hey github ever heard of REST principles?) try replacing second export with:
export NAMADA_NETWORK_CONFIGS_SERVER="https://github.com/namada-net/namada-mainnet-genesis/releases/download/mainnet-genesis"

[vague nexus]

Hello, how fix this problem

[harsh abyss]

hard to be sure from your image due to cometbft backtrace filling most of it, please post log output text going back further than what's in that screenshot

[harsh abyss]

looks like you're getting an apphash error, if you're at height 4514501 then likely you need to rollback state to 4514500

also make sure you're running the latest stable version: v201.0.7

[toxic girder]

see this thread for context: https://discord.com/channels/833618405537218590/1447511491220602950

thanks, @harsh abyss

[vague nexus]

/home/runner/work/cometbft/cometbft/cmd/cometbft/commands/run_node.go:108 +0x4f
github.com/spf13/cobra.(*Command).execute(0xc000432608, {0xc000157940, 0x4, 0x4})
/home/runner/go/pkg/mod/github.com/spf13/cobra@v1.8.1/command.go:985 +0xaca
github.com/spf13/cobra.(*Command).ExecuteC(0x1af9f20)
/home/runner/go/pkg/mod/github.com/spf13/cobra@v1.8.1/command.go:1117 +0x3ff
github.com/spf13/cobra.(*Command).Execute(...)
/home/runner/go/pkg/mod/github.com/spf13/cobra@v1.8.1/command.go:1041
github.com/cometbft/cometbft/libs/cli.Executor.Execute({0x1af9f20?, 0x11fd738?})
/home/runner/work/cometbft/cometbft/libs/cli/setup.go:89 +0x45
main.main()
/home/runner/work/cometbft/cometbft/cmd/cometbft/main.go:50 +0x20c
2025-12-17T13:34:34.244230Z INFO namada_node: Tendermint node is no longer running.
2025-12-17T13:34:34.244240Z ERROR namada_node: Err(Tendermint(Runtime("exit status: 2")))
2025-12-17T13:34:34.244255Z INFO namada_node::abortable: Tendermint has exited, shutting down...
2025-12-17T13:34:34.244273Z INFO namada_node: Namada ledger node has shut down.
2025-12-17T13:34:34.244310Z INFO namada_node: Shutting down ABCI server...
2025-12-17T13:34:34.244327Z ERROR namada_node::abortable: Tendermint error: exit status: 2
namadad.service: Deactivated successfully.
namadad.service: Consumed 4.207s CPU time.

[harsh abyss]

that snippet contains even less than the screenshot

[harsh abyss]

you've got an apphash error at height 944, I think your databases are all out of whack, best bet is to backup your validator key, delete db folders and download a new snapshot

[vague nexus]

okay, thanks

[harsh abyss]

this probably a side-effect of running out of space previously

[toxic girder]

@vague nexus please make sure you have enough disk space for both snapshot archive and space to unpack. if you get any out of space errors while unpacking the snapshot, you can not expect the node to work.

you check disk space with df -H

for future reference, it will be a lot easier if you upgrade your node when upgrades happen.

[vague nexus]

Thanks, but everything with disk is good

I installed snapshot, new blocks have showed but I have problems with unjailing my validator

[toxic girder]

show the relevant log snip please, I don't want to open your attachment

[vague nexus]

root@Ubuntu-2404-noble-amd64-base ~ # sudo journalctl -u namadad -f -o cat
I[2025-12-22|07:09:51.271] received complete proposal block module=consensus height=4753593 hash=397B11B0669795B41ACBB0FCEFF985B82D872F1E70DE25E9B6BE35A31433931C
2025-12-22T06:09:51.277382Z INFO namada_node:🐚:process_proposal: Received block proposal proposer="8FBB9279A4CBF529F7DCA00C7684C523F8693A90" height=4753593 hash="397B11B0669795B41ACBB0FCEFF985B82D872F1E70DE25E9B6BE35A31433931C" n_txs=0
I[2025-12-22|07:09:51.936] finalizing commit of block module=consensus height=4753593 hash=397B11B0669795B41ACBB0FCEFF985B82D872F1E70DE25E9B6BE35A31433931C root=36E765AB8D4B38189401A65299746F095C438C01BF0350D7AF5C5C9155840133 num_txs=0
2025-12-22T06:09:51.965122Z INFO namada_node:🐚:finalize_block: Block height: 4753593, epoch: 1533, is new epoch: false, is masp new epoch: false.
2025-12-22T06:09:52.102276Z INFO namada_node:🐚:finalize_block: Applied 0 transactions. Wrappers: 0, successful inner txs: 0, rejected inner txs: 0, errored inner txs: 0, unrun txs: 0, valid txs discarded by failing atomic batch: 0, vp cache size: 2 - 2, tx cache size 14 - 14
2025-12-22T06:09:52.102283Z INFO namada_node:🐚:finalize_block: txs executed: 0

root@Ubuntu-2404-noble-amd64-base ~ # namadac unjail-validator --validator tnam1q9n3ncfxevwgs8f2vna2lnw7kz567jrutgw57xqs
Looking-up public key of tnam1q9n3ncfxevwgs8f2vna2lnw7kz567jrutgw57xqs from the ledger...
Error:
0: unable to sign transaction with tpknam1qpyy0efy77qh5cl4027ewswrktwq4yqmlj0y0wmwjdsz7kmkj5q7gtqg8kr

Location:
/home/runner/work/namada/namada/crates/apps_lib/src/cli/client.rs:474

Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.

[toxic girder]

namadac --version

show output

[vague nexus]

root@Ubuntu-2404-noble-amd64-base ~ # namadac --version
Namada v201.0.7

[harsh abyss]

It seems namadac can't find relevant entries in your wallet.toml, do you have entries for you validator in [secret_keys] and [public_keys] sections of your wallet.toml? (DO NOT POST KEYS HERE!!!)

normally you'd have an alias, for example 'my_validator' that corresponds to validator key entries in your wallet.toml file, then you'd give this alias as the argument to the --validator option in your unjailing command