I am trying to run below command in testnet, however i have some doubts :
Right now below command is not passing --db parameter because I am not sure what will the correct value. FYI, no file like /opt/cardano/cnode/scripts/cncli.db exists for me. However when i earlier ran command ./cncli.sh sync its displayed below info line :
SQLite blocklog DB created: /opt/cardano/cnode/guild-db/blocklog/blocklog.db
Now after Alonzo HFC, will not below command also expect a new parameter e.g. --alonzo-genesis similar to byron and shelly reason being a the file /opt/cardano/cnode/files/alonzo-genesis.json now also exists ?
what about parameter --ledger-state “$config_path/ledger-state.json” ? where will i find this json file ?
this is the way how you are running cncli?
why not just simple ./cncli.sh leaderlog because you have all above informations inside the script
nano cncli.sh
Yeah, because i was facing some error with original way.
Anyways, now i once again tried with ./cncli.sh leaderlog and Voila it worked !
However it displayed below output. What to understand from it ? Any issues with my Pool setup ?
By the way, i registered two different Pools from same BP, so wondering this command output correspond to which Pool ?
Checking for script updates…
~ CNCLI Leaderlog started ~
Node in sync, sleeping for 60s before running leaderlogs for current epoch
Leaderlogs already calculated for epoch 156, skipping!
Running leaderlogs for next epoch[157]
Leaderlog calculation for next epoch[157] completed and saved to blocklog DB
Leaderslots: 0 - Ideal slots for epoch based on active stake: 0 - Luck factor 0%
But out of 2 Pools on this BP which are currently registered with testnet, one has ~1M tADA so i was thinking it must get a leader chance at least. Can any other factor influence the same ?
Still wondering which Pool out of two, above commands used for checking the leaderlog ?
seems cncli.sh picks Pool Name from /opt/cardano/cnode/scripts/env file.
I had earlier set an older pool name there which has been de-registered some time back. I had forgot about this config.
POOL_NAME=“SWEETPOOL”
Now, I just changed it to another Pool name which is still registered and have ~1M tADA staked.
POOL_NAME=“SWEETPOOL1”
However now leaderlog showed below output
Checking for script updates…
~ CNCLI Leaderlog started ~
Node in sync, sleeping for 60s before running leaderlogs for current epoch
Leaderlogs already calculated for epoch 156, skipping!
Leaderlogs already calculated for epoch 157, skipping!
Checking for script updates…
~ CNCLI Leaderlog started ~
Running leaderlogs for epoch 156 and adding leader slots not already in DB
Leaderlog calculation for epoch[156] completed and saved to blocklog DB
Leaderslots: 0 - Ideal slots for epoch based on active stake: 1.51 - Luck factor 0%
Running leaderlogs for next epoch[157]
LEADER: slot[37534033] slotInEpoch[79633] at[2021-09-17T18:27:29+00:00]
Leaderlog calculation for next epoch[157] completed and saved to blocklog DB
Leaderslots: 1 - Ideal slots for epoch based on active stake: 1.2 - Luck factor 83.33%
running “sudo systemctl restart cnode” just on BP node is fine or Relay also needed ?
Yeah , that’s why i played around with 3 wallets and 3 pools (registered, de-registered). Had i created it all clean (just 1 wallet, 1 Pool) i would not had known about it.
This also means, Its not possible for a single BP node to simultaneously work with two Pools in parallel ?
nope, you must have one node service per pool, i think you can create more users… like user 1 to be used for pool 1 and user 2 to be used for pool2
or perhaps you will need to use tmux sessions and start the node manually (./cnode.sh but inside the cnode.sh you will need to edit the path for pool folder)
On same BP, i have 2 Pools registered with testnet. However now my BP is connected to testnet through 1st Pool.
What is the overall status of my 2nd Pool. What does it mean for a Pool to be registered with testnet but not actually working as a Pool through a Node ?
I think you already know the answer