UPDATE CARDANO NODE to 1.31.0 - FOR CNTOOLS users

hmmm, where did u found this info?

Is there a difference, are you sure?

as far as I know should not be, perhaps something for metrics but I am not aware of this

1 Like

diff mainnet-config.json backup/mainnet-config.json
16d15
< “TraceAcceptPolicy”: true,
18c17
< “TraceBlockFetchDecisions”: false,

“TraceBlockFetchDecisions”: true,
27d25
< “TraceConnectionManager”: true,
30d27
< “TraceDiffusionInitialization”: true,
34d30
< “TraceInboundGovernor”: true,
36d31
< “TraceLedgerPeers”: true,
40d34
< “TraceLocalRootPeers”: true,
45,48d38
< “TracePeerSelection”: true,
< “TracePeerSelectionActions”: true,
< “TracePublicRootPeers”: true,
< “TraceServer”: true,

hmmmm… I will check… but should not be a problem if u don’t have it

created an updated version for simplicity:

let me know if anyone needs any help :slight_smile:

Hey there,

i got my relays without any problem up to date but on my BP after the update it still shows version 1.30.1
Update went thru without any errors and the node startet with any errors after that.

jurnalctl shows no errors.

Edit:
Just found out why. and i dont know why is it how it is. It was not a problem before
i needed to uncheck in the env.

CNODEBIN="${HOME}/.cabal/bin/cardano-node"
CCLI="${HOME}/.cabal/bin/cardano-cli"
CNCLI="${HOME}/.cargo/bin/cncli"

that means the automatic detection detects another node there?

cardano-node --version
cardano-node 1.30.1 - linux-x86_64 - ghc-8.10
git rev 0fb43f4e3da8b225f4f86557aed90a183981a64f

in gLiveView it is version 1.31.0

Type which cardano-node

It’s possible to have the old version here

cd /usr/local/bin
ls -l

and the new version here

cd ${HOME}/.cabal/bin/
ls -l

Or viceversa, check the date of the files (cardano-node and cardano-cli)

yes you are right old version is there. Should be no problem because the env use the cabal path or should i delete the old one?

Delete the old files then add back # (comment inside env fie)
restart the node and check again

runs fine now after delete the old one and rebooting.

–version shows the newest with the new revision number

thank you :slight_smile:

1 Like

You are welcome :beers:

After the update, one of the Relays only has Starting status.

What could it be?

image

journalctl -e -f -u cnode

do you see any errors?

also if u check with top do you see the CPU ~100%?

The result brought a lot, I was a little lost… there’s still a lot of log scrolling down

image

hmm from journalctl -e -f -u cnode

try to share the output for today

looking at top output … means the node is working to start, perhaps it will take more time

8GB + 2GB Swap.

It has the same configuration as my Relay3, which is online

share again the output for today

Did you restart after updating or stopped and started the node?