Coincashew install & CNCLI - Are they compatible?

Staking & Delegation Operate a Stake Pool
21

Yeah cncli version 2.1.0

1 Like
22

Ok, and what is the error?

1 Like
23

Was a connection timed out error. figured with the way I was using iptables

1 Like
24

Have you updated to cncli 2.1.0, did it take long?

1 Like
25

mind if I ask what was wrong with your iptables? I’m still having issues with cncli

1 Like
26

Yes, I think I have the latest version

1 Like
27

hey jeremy, fyi I got the cncli leaderlog working with help from the forums. Let me know if you still need help

1 Like
28

Yeah, sorry I should have replied too. Coincashew updated their page to include leaderlog via cncli and I got it working for the first time this morning. The old method still works at the moment.

1 Like
29

No problem. Glad you got it working too

1 Like
30

Hi @jeremyisme
Can you share the link or which section coincashew guide that include the leaderlog CNCLI ?

Thank you.

1 Like
31

section 18.12

3 Likes
32

Hi Guys,

I’ve been following the discussion and, like the above posters, was reluctant to mess too much with my env files. But I did get it working with the help of the new coincashew section.

For a while… It produced good leaderlogs for 3 epochs, however last epoch it exited with a leaderlog.json file containing only an error message after about 2 seconds when running for “next” epoch. Now it exits with the same error for “current” epoch too:

command:
sudo bash ${NODE_HOME}/scripts/cncli-leaderlog.sh current America/Toronto

output:
{
“status”: “error”
“errorMessage”: “EOF while parsing a value at line 1 column 0”
}

In an attempt to fix, I reran the ledger-dump.sh download script manually, restarted the cncli-sync service and restarted the node… No luck.

I suspect I have managed to damage the installation (or env file) as I had opened up the /opt/cardano/cnode/scripts/cntools.sh script and looked around the menus in the interface. (Which cannot see the running node, nor wallet, using those list menu items, btw). I think it may have tried to install itself and altered the needed env file entries?

My coincashew node still processes transactions and appears normal, but no more leaderlogs. (No blocks yet!).

Has anyone else ever come across the error I have in my leaderlog.json output?

Thanks for reading!

1 Like
33

I get that error when the api hasn’t been updated yet. Try it again now. Mine only worked once the epoch boundary has ticked over.

1 Like
34

You’re right! Mine is ok now! Phew… Thanks.

Not sure what is happening to have this result.

I am sure I did a “next” leaderlog about 12 hours before the epoch boundary when I first set it up a few epochs ago…

1 Like
35

My “next” one hasn’t worked for a few epochs. I’ve been getting results once the epoch boundary has been reached then used “current”. I assume it is just delays in the API update. The other way is to do a full ledger dump, rather than rely on the API but that is resource hungry, so I figure I just need to accept any delays in the API given it is being provided free, otherwise I need to suck it up and deal with the ledger dump route.

1 Like