#radomir troubleshooting
silk marsh
How can I do it?
see my answer in general chat. would be good if we keep the discussion in a single place.
west bone
Hello
root@Ubuntu-2204-jammy-amd64-base:~# namadac unjail-validator --validator tnam1q9n3ncfxevwgs8f2vna2lnw7kz567jrutgw57xqs
Looking-up public key of tnam1q9n3ncfxevwgs8f2vna2lnw7kz567jrutgw57xqs from the ledger...
The given validator address tnam1q9n3ncfxevwgs8f2vna2lnw7kz567jrutgw57xqs is not jailed at the pipeline epoch when it would be restored to one of the validator sets.
Error:
0: The validator address tnam1q9n3ncfxevwgs8f2vna2lnw7kz567jrutgw57xqs is not jailed at epoch when it would be restored.
1: The validator address tnam1q9n3ncfxevwgs8f2vna2lnw7kz567jrutgw57xqs is not jailed at epoch when it would be restored.
Location:
/root/namada/crates/apps_lib/src/cli/client.rs:433
Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.
What can I fix this error?
silk marsh
root@Ubuntu-2204-jammy-amd64-base:~# namadac unjail-validator --validator tnam1q...
what does namadac --version give?
if you have the old binary installed, try the new binary.
can I ask why you want to deactivate your validator? if it's about not having upgraded, I'm sure we can help you through that
west bone
Namada v1.1.1
west bone
can I ask why you want to deactivate your validator? if it's about not having up...
No, i want to activate my validator
silk marsh
No, i want to activate my validator
ok so what you need to do is to make sure any services are stopped, upgrade your binaries to latest release (101.00), restore a snapshot, then start your node. after you see your node is running and have no issues catching up with the network, I would do the unjail.
please ask if you have any questions as to the particulars
west bone
Okay, i will try
west bone
Can you please help me?
Where can I find new binaries and how update?
I did not it before
I think I can find snapshot in Polkachu
silk marsh
check the namada github under releases. download the binaries using wget, extract the archive, and replace by copying new binaries into /usr/local/bin (use sudo as a superuser)
check new binaries with --version
if you are unfamiliar with what the above means, I think you need to read up on basic unix system commands, but unsure if it's just the binary files you can't find.
west bone
root@Ubuntu-2204-jammy-amd64-base:~# sudo cp namada-v101.0.0-Linux-x86_64/namada namada-v101.0.0-Linux-x86_64/namadan namada-v101.0.0-Linux-x86_64/namadaw namada-v101.0.0-Linux-x86_64/namadac /usr/local/bin/
root@Ubuntu-2204-jammy-amd64-base:~# namadac --version
Namada v1.1.1
What i did wrong?
silk marsh
root@Ubuntu-2204-jammy-amd64-base:~# sudo cp namada-v101.0.0-Linux-x86_64/namada...
you made like five recursive folders. try removing all the redundant folder-names. also, there are 4 binaries and you need to copy all of them
I have to say, I am a little in doubt if you currently have the technical understanding to run a validator, based on the above. (I am happy to help regardless of course)
silk marsh
root@Ubuntu-2204-jammy-amd64-base:~# sudo cp namada-v101.0.0-Linux-x86_64/namada...
you can also run which namadac to check if it's running a binary from some other location
west bone
root@Ubuntu-2204-jammy-amd64-base:~# sudo cp namada-v101.0.0-Linux-x86_64/namada namada-v101.0.0-Linux-x86_64/namadan namada-v101.0.0-Linux-x86_64/namadaw namada-v101.0.0-Linux-x86_64/namadac /root/.cargo/bin
root@Ubuntu-2204-jammy-amd64-base:~# namadac --version
namadac: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.38' not found (required by namadac)
silk marsh
root@Ubuntu-2204-jammy-amd64-base:~# sudo cp namada-v101.0.0-Linux-x86_64/namada...
yeah ok, you need to upgrade your distro to use the precompiled binaries