Pool minting blocks fine, but gLiveView not updating blocks adopted or confirmed

Using CNCLI leaderlog script we can see blocks allocated in the next epoch and the node successfully processes the blocks on schedule.

After running the cncli leaderlog, gLiveView “BLOCKS” section successfully updates to show Leader 1 and displays the countdown. The block is minted correctly as confirmed on pooltool and adapools, but gLiveView never updates the “adopted” or “confirmed” fields.
This has happened for 3 successive blocks.

This occurred both on node v1.26.2 and on the current node v1.27. CNCLI has been kept up to date throughout. Likewise gLiveView has been kept up to date.

CNCLI was installed using the command below.
cd “$HOME/tmp”
curl -sS -o prereqs.sh https://raw.githubusercontent.com/cardano-community/guild-operators/master/scripts/cnode-helper-scripts/prereqs.sh
chmod 755 prereqs.sh
./prereqs.sh -c
. “${HOME}/.bashrc”

I’m guessing the gLiveView script, or an env file somewhere needs configuring.

1 Like

How did you manager to get the countdown until slotleader into guild liveview?

Cncli is installed

After running the cncli leaderlog, this countdown timer automatically appears in gLiveView.

U are not running cncli as systemd

If u want u can add the blocks manually

./cncli.sh sync
./cncli.sh init after each time u created a block

If u will want to see them auto then run

./deploy-as-systemd.sh
Choose N for topology updater and also N for Ptsendtip and leaderlog (are for pooltool.io)
Y for the rest

In my terminal I can see that we are scheduled for a block, but after running the cncli leaderlog gLiveView does not update the scheduled block.

Sorry by the way for interupting your forum post, but I was just curious.

It could be the timing of running the leaderlog. It was run prior to the epoch starting. Perhaps if running during an epoch it changes the visibility in gLiveView?

Thanks for the reply. I ran ./deploy-as-systemd.sh
It prompted for topology updater, Ptsendtip and leaderlog as you mentioned. I selected N.
It then automatically installed everything from that point without further prompts.

I rebooted the computer and gLiveView wouldn’t work. I found the reason was systemd had started two cardano-node services.
I killed the node service relating to cnode (cncli presumably) and deleted the 2x systemd files that had been created in /etc/systemd/system/

So back to normal at the moment.
Is there any way I can start cncli with systemd without it starting up a duplicate node instance? Or would I have to delete my existing coincashew systemd service and just use the cncli one?

oo u are using coincash guide… wait

try step 18.12 from the guide
18.12 Slot Leader Schedule - Find out when your pool will mint blocks

and check how to add as systemd the cncli.sync.service to work as systemd

to deactivate the cnode from previously attempt

sudo systemctl disable cnode
sudo systemctl stop cnode

Will do. I purposefully avoided the coincashew cncli section originally, as I like a simple, paired back approach.

So I installed using prereqs and ran the scripts manually which works well, except for the gLiveView not updating to confirm.

To confirm, if I set up cncli.sync as a systemd service, this will cause gLiveView to update blocks correctly? I have tried leaving cncli.sync running in a terminal perpetually, during the moment a block was minted, and gLiveView still didn’t update to confirm the block. The block was successfully minted per pooltool and adapools.

hmm I don’t know if only the sync process will update the glive
try to add also cncli-validate.service

you have a block minted right?
try
./cncli.sh sync
./cncli.sh init

then check the glive

Yes I think you’re on to something with the cncli-validate service + cncli sync
“validate Continously monitor and confirm that the blocks made actually was accepted and adopted by chain (deployed as service)”

I’m fairly confident cncli init will work to one-off update, each time it is manually run. I’ll have to get back to you on that later.

If I want to stop gLiveView looking at cncli info, reverting it to EKG? instead, how would I do that?

ok, I have another WA for you

run again the ./deploy-as-systemd.sh with N and Y like I said before…
and stop only the cnode service

sudo systemctl disable cnode
sudo systemctl stop cnode

then check if the cncli services are still running

sudo systemctl status cnode-cncli-sync.service
sudo systemctl status cnode-cncli-leaderlog.service
sudo systemctl status cnode-cncli-validate.service
sudo systemctl status cnode-logmonitor.service

So redoing ./deploy-as-systemd.sh
No cnode or related processes appear until computer restart.

Upon restart there are two cardano-node processes and one cnode process. There are none of the below processes.
sudo systemctl status cnode-cncli-sync.service
sudo systemctl status cnode-cncli-leaderlog.service
sudo systemctl status cnode-cncli-validate.service
sudo systemctl status cnode-logmonitor.service

Perhaps they require the node to be fully started which is problematic when two instances exist?

hmm two instances not ok… then perhaps this variant is not compatible… u installed the nodes using coincashew guide or guide for cntools?
I mean the nodes

The node was installed using coincashew guide.
cncli installed using prereqs command, but no sysemd configs. Only running sync and leaderlog manually.

I notice in the coincashew guide they only enable cncli sync as systemd (and sendtip). Unless sendtip is somehow read by gLiveView, it seems neither would cause gLiveView to update adopted/confirmed blocks.

indeed, for auto update you will need another services to run, like validate, etc… or perhaps you will need to change the paths in env … for example
#BLOCKLOG_DIR="${CNODE_HOME}/guild-db/blocklog"

1 Like

The block countdown timer is a nice feature, but how would I point gLiveView away from cncli and back to looking at standard EKG metrics?

I’ll have a look at blocklog.

1 Like

I runned the leaderlog again, and restarted gLiveView. But nothing is appearing yet.
Maybe I am going to make a new forumpost for it, because I really like the helpfull interface.

1 Like

If you are using the coincashew binary install of cncli, seems you won’t get this feature.

If you install CNCLI compiling from source using the command below
cd “$HOME/tmp”
curl -sS -o prereqs.sh https://raw.githubusercontent.com/cardano-community/guild-operators/master/scripts/cnode-helper-scripts/prereqs.sh
chmod 755 prereqs.sh
./prereqs.sh -c
. “${HOME}/.bashrc”

A series of cncli scripts will appear in /opt/cardano/cnode/scripts
Navigating to this directory in terminal you can run ./cncli.sh sync
followed by ./cncli.sh leaderlog (after 1.5 days remain in the epoch)
gLiveView will then show the countdown timer to the block. Pooltool and adapools will confirm the block if your block producer processes it successfully.

1 Like

Thanks, this worked out!

Cheers,

1 Like