If on your validator address page, you see something like this:
Eg: https://aplikigo.regen.aneka.io/validators/regen:valoper1d4f009htfy94s5rwxx0cz2sw3eufsr75cazkmz
This means you are not producing blocks !
This needs to be fixed !
Go To https://aplikigo.regen.aneka.io/validators?page=jailed and check if you are jailed. If yes try running the command:
regen tx slashing unjail — fees=5000utree — chain-id aplikigo-1 — from <your_delegator_address>You should start producing blocks now, go to https://aplikigo.regen.aneka.io/validators/<your_validator_address> to check.
The below steps only needs to be followed if you still not see something like this:
If all the blocks are still red continue, if you see even a one blue block, you are good.
There might be a case that you may be out of sync and the unjail commands gives error like this:
{“height”:”0",”txhash”:”FAA9E354C9DD2DB4F864E0A0C57EDF106288820A38E22B535FB6D15FA4BDC5CE”,”codespace”:”sdk”,”code”:4,”data”:””,”raw_log”:”signature verification failed; please verify account number (0) and chain-id (): unauthorized”,”logs”:[],”info”:””,”gas_wanted”:”0",”gas_used”:”41675",”tx”:null,”timestamp”:””}Run this command:
curl -s localhost:26657/status | jq .result | jq .sync_info— — — — — — — — — — — — — — — — — — — — — — — — — — -
“sync_info”: {
“latest_block_hash”: “732E4461E9AD062E48E5AAD7C99ED2AE28688BDDD1670ECCF83F8FA81B112C05”,
“latest_app_hash”: “1391A06E9D7EFDD61ACA104F4F8216C596EC06CF23E8DC232E9A3BB6FD7344F3”,
“latest_block_height”: “35088”,
“latest_block_time”: “2021–02–11T04:01:35.769527969Z”,
“earliest_block_hash”: “7A38C7B2CC66D9C90C7D0FE43710E2769B023AA1E7F3D407C13E0DB60CD61F53”,
“earliest_app_hash”: “E3B0C44298FC1C149AFBF4C8996FB92427AE41E4649B934CA495991B7852B855”,
“earliest_block_height”: “1”,
“earliest_block_time”: “2021–02–08T15:00:00Z”,
“catching_up”: false
}Check if the latest block height is actually the latest and is increasing. If not you are not syncing up with the network.
Run these commands to fix it:
sudo systemctl stop regen rm .regen/config/addrbook.json sudo systemctl start regen
And Check Again using
curl -s localhost:26657/status | jq .result | jq .sync_info— — — — — — — — — — — — — — — — — — — — — — — — — — — —
“sync_info”: {
“latest_block_hash”: “732E4461E9AD062E48E5AAD7C99ED2AE28688BDDD1670ECCF83F8FA81B112C05”,
“latest_app_hash”: “1391A06E9D7EFDD61ACA104F4F8216C596EC06CF23E8DC232E9A3BB6FD7344F3”,
“latest_block_height”: “35090”, <-- This should be increasing
“latest_block_time”: “2021–02–11T04:01:35.769527969Z”,
“earliest_block_hash”: “7A38C7B2CC66D9C90C7D0FE43710E2769B023AA1E7F3D407C13E0DB60CD61F53”,
“earliest_app_hash”: “E3B0C44298FC1C149AFBF4C8996FB92427AE41E4649B934CA495991B7852B855”,
“earliest_block_height”: “1”,
“earliest_block_time”: “2021–02–08T15:00:00Z”,
“catching_up”: true
}Once catching_up becomes false try the unjail commands again:
regen tx slashing unjail — fees=5000utree — chain-id aplikigo-1 — from <your_delegator_address>This should bring your node back up and you should start producing blocks :)
You Should start seeing blue blocks appearing :)
Why this works ?!
In your config file present in ~/.regen/config/config.toml you will find this:
# Maximum number of inbound peers
max_num_inbound_peers = xx# Maximum number of outbound peers to connect to, excluding persistent peers
max_num_outbound_peers = xx
This specifies how many peers you can connect to. By default this number is pretty low and has to be manually increased which most people don’t do. Your addrbook is limited by this number. If inbound peer is set at 10 your addrbook will only have 10 entries in it. so if the seeds give you all 10 dead peers you can’t connect to the network. Once you stopped and removed yours it got filled up with newer peers who are synced with the network.
Credit Goes To k_kappa#0309 and anilcse#5181
