Hi there! Thanks for the reply. I didn’t explicitly do an update, but when I ran cncli.sh leaderlog recently it asked me if I wanted to update and I said yes… Does that bring me current to 5.0.2? Or do I need to manually update?
Not sure what script you are running, but error what you are getting is implying that CNCLI doesn’t expect –consensus argument. That argument is available from 5.0.0 version. So my guess is that your script expects latest version of CNCLI binary.
If you will update your CNCLI binary, everything should work.
Whoops… Spoke to soon… The update ran, but it looks like it only tried to update to 4.0.4? Afterwards, I received the same error when attempting to run leaderlog…
Installing CNCLI
previous CNCLI installation found, pulling latest version from GitHub…
CNCLI already latest version [v4.0.4], skipping!
cncli.sh and the CNCLI binary are two different things. The cncli.sh script calls the binary, however. When the cncli.sh script prompts you to update, the script is updated.
You also need to update the binary manually as a separate procedure. The current version of the binary is v5.0.2 GitHub - cardano-community/cncli