I have decided to switch my relay node with a cloud based node but after registration, the old relay node still showing and the new is not up yet.
What am i missing?
Did i need to shut down the old one? the block node is re-figured with the new relay node pub ip and port
Have patience… perhaps it needs time to update… check on pool.vet
pool.vet is still showing that old relay is not reachable but the block node is pointed now to the new relay.
Do you think i need to shut down the old one.
I got an error when trying to add second relay with this code:
cardano-cli stake-pool registration-certificate
–cold-verification-key-file $HOME/cold-keys/node.vkey
–vrf-verification-key-file vrf.vkey
–pool-pledge 100000000
–pool-cost 345000000
–pool-margin 0.15
–pool-reward-account-verification-key-file stake.vkey
–pool-owner-stake-verification-key-file stake.vkey
–mainnet
–single-host-pool-relay “pub ip”
–pool-relay-port 7000
–single-host-pool-relay “pub ip”
–pool-relay-port 5000
–metadata-url
–metadata-hash $(cat poolMetaDataHash.txt)
–out-file pool.cert
Delete the old node from pool certificate…keep only the new one
After running this command cardano-cli stake-pool registration-certificate , i created a new pool.cert with the new the relay information and that was the one i have used to signed the pool.
When I checked my pool info on cardanoscan, it said that the update did not take place. I was showing the one i did last months but not the recent one… Here is my issue…
I will register again and what will happen.
Follow the step 18.4
This is what im using to build all my node… I will do it when i get home.
Thanks
Big: my pool was scheduled for 2 block in this epoch but im having issue, will i loose them?
If u are processing tx on producer it should be fine
Okay,
Sorry for bothering you. The un-register relay node means that I just need to add 2nd relay info into block producer mainnet-topology file and no need to re-create pool.cert with the new relay…If i understand right?
Yes, set the new relay like the okd one, run topology updater, connect to the producer and it should be fine… just check the producer if started, if has peers IN/OUT and if it is processing tx