UPDATE CARDANO NODE to 1.30.1 - FOR CNTOOLS users

Cardano Node 1.30.1

@github-actions github-actions released this 5 hours ago

This is a minor release to support the hard fork to Alonzo protocol version 6. The purpose of this protocol version is to fix a bug in conversion of time for Plutus scripts.

Additionally, we make a change to the crypto library which should have a positive impact on sync times.

All SPOs and node users must update to this (or a later) version prior to the HF to Alonzo PV 6, or risk not being able to sync to the network.

How to update to 1.30.1

!!! YOU MUST KNOW THAT starting with 1.29.0 version the servers require ~10G RAM !!! (if you have 8G you can add 2-3G of SWAP)

bofore to start it’s better also to update the server

sudo apt-get update
sudo apt-get upgrade
sudo reboot 
  • perform a snapshot for server (if u have this option offered by your provider) before to start the update
  • update the Relays first (one by one)

BUILDING THE NODE

  • stop the node :
sudo systemctl stop cnode
  • build the node
cd ~/git
sudo rm -R cardano-node
git clone https://github.com/input-output-hk/cardano-node 
cd cardano-node

git fetch --tags --all
git checkout 1.30.1


echo -e "package cardano-crypto-praos\n  flags: -external-libsodium-vrf" > cabal.project.local
$CNODE_HOME/scripts/cabal-build-all.sh

at the end you should see:

Copying unit to /home/user/.cabal/bin/
Copying cardano-topology to /home/user/.cabal/bin/
Copying locli to /home/user/.cabal/bin/
Copying cardano-submit-api to /home/user/.cabal/bin/
Copying plutus-example to /home/user/.cabal/bin/
Copying cardano-cli to /home/user/.cabal/bin/
Copying cardano-node to /home/user/.cabal/bin/
Copying cardano-node-chairman to /home/user/.cabal/bin/
Copying tx-generator to /home/user/.cabal/bin/
:~/git/cardano-node$


438734:~/git/cardano-node$ cardano-node --version
cardano-node 1.30.1 - linux-x86_64 - ghc-8.10
git rev 0fb43f4e3da8b225f4f86557aed90a183981a64f
i438734:~/git/cardano-node$ cardano-cli --version
cardano-cli 1.30.1 - linux-x86_64 - ghc-8.10
git rev 0fb43f4e3da8b225f4f86557aed90a183981a64f

It took ~40 minutes :slight_smile:

START THE NODE

sudo systemctl start cnode

check the status and the revision (should be 0fb43f4)

/git/cardano-node$ sudo systemctl status cnode
● cnode.service - Cardano Node
   Loaded: loaded (/etc/systemd/system/cnode.service; enabled; vendor preset: enabled)
   Active: active (running) since Tue 2021-09-28 21:40:56 CEST; 3s ago
  Process: 60393 ExecStop=/bin/bash -l -c exec kill -2 $(ps -ef | grep [c]ardano-node.*./opt/cardano/cnode/ | tr -s ' ' | cut -d ' ' -f2) &>/dev/null (code=exited, status=0/SUCCESS)
 Main PID: 5640 (cnode.sh)
    Tasks: 10 (limit: 9830)

image

Thank you,

24 Likes

Thanks for being on top of this!

1 Like

Unfortunately, my producer has stacked on starting…
I restart it, stop and start it. Restart the server, wait more than 30 min, 1 hour is always on
Status: starting …

Is there anything specific I’m missing? I had this issue with all the relays when I updated from 1.27.0 to 1.29.0 then my pool stoped working. After OS reinstall on the servers and install from scratch they started to work, but this made me lost a lot of time to sync the whole blockchain, etc.
I don’t want to do that with the producer as well.
Currently, I have working relays but not working producer.

type journalctl -e -f -u cnode and show me the output

-- Reboot --
Aug 06 07:44:02 vps.server.com cnode[661]: WARN: A prior running Cardano node was not cleanly shutdown, socket file still exists. Cleaning up.
Aug 06 07:44:09 vps.server.com cnode[835]: Listening on http://127.0.0.1:12798
Sep 02 11:54:04 vps.server.com cnode[835]: Shutting down..
Sep 02 13:27:40 vps.server.com cnode[112762]: WARN: A prior running Cardano node was not cleanly shutdown, socket file still exists. Cleaning up.
Sep 02 13:27:41 vps.server.com cnode[112832]: Listening on http://127.0.0.1:12798
-- Reboot --
Sep 13 01:10:25 vps.server.com cnode[707]: WARN: A prior running Cardano node was not cleanly shutdown, socket file still exists. Cleaning up.
Sep 13 01:10:26 vps.server.com cnode[819]: Listening on http://127.0.0.1:12798
-- Reboot --
Sep 28 10:45:11 vps.server.com cnode[706]: WARN: A prior running Cardano node was not cleanly shutdown, socket file still exists. Cleaning up.
Sep 28 10:45:12 vps.server.com cnode[812]: Listening on http://127.0.0.1:12798
Sep 28 15:38:19 vps.server.com cnode[812]: Shutting down..
-- Reboot --
Sep 28 15:41:16 producer.cardanoswiss.ch cnode[711]: WARN: A prior running Cardano node was not cleanly shutdown, socket file still exists. Cleaning up.
Sep 28 15:41:18 producer.cardanoswiss.ch cnode[825]: Listening on http://127.0.0.1:12798
Sep 28 15:49:17 producer.cardanoswiss.ch cnode[825]: Shutting down..
Sep 29 07:26:00 producer.cardanoswiss.ch cnode[4263]: WARN: A prior running Cardano node was not cleanly shutdown, socket file still exists. Cleaning up.
Sep 29 07:26:01 producer.cardanoswiss.ch cnode[4333]: Listening on http://127.0.0.1:12798
Sep 29 09:24:58 producer.cardanoswiss.ch cnode[82922]: Listening on http://127.0.0.1:12798
Sep 29 09:49:03 producer.cardanoswiss.ch cnode[82922]: Shutting down..
Sep 29 09:49:05 producer.cardanoswiss.ch cnode[87392]: WARN: A prior running Cardano node was not cleanly shutdown, socket file still exists. Cleaning up.
Sep 29 09:49:06 producer.cardanoswiss.ch cnode[87464]: Listening on http://127.0.0.1:12798
Sep 29 09:54:52 producer.cardanoswiss.ch cnode[87464]: Shutting down..
-- Reboot --
Sep 29 09:55:49 producer.cardanoswiss.ch cnode[729]: WARN: A prior running Cardano node was not cleanly shutdown, socket file still exists. Cleaning up.
Sep 29 09:55:50 producer.cardanoswiss.ch cnode[923]: Listening on http://127.0.0.1:12798
-- Reboot --
Sep 29 09:57:23 producer.cardanoswiss.ch cnode[823]: Listening on http://127.0.0.1:12798
Sep 29 10:56:06 producer.cardanoswiss.ch cnode[823]: Shutting down..
-- Reboot --
Sep 29 12:08:58 producer.cardanoswiss.ch cnode[845]: WARN: A prior running Cardano node was not cleanly shutdown, socket file still exists. Cleaning up.
Sep 29 12:08:59 producer.cardanoswiss.ch cnode[1007]: Listening on http://127.0.0.1:12798
-- Reboot --
Sep 29 12:11:24 producer.cardanoswiss.ch cnode[1005]: Listening on http://127.0.0.1:12798
Sep 29 12:18:28 producer.cardanoswiss.ch cnode[1634]: Listening on http://127.0.0.1:12798
Sep 29 12:29:06 producer.cardanoswiss.ch cnode[3047]: Listening on http://127.0.0.1:12798
Sep 29 12:36:34 producer.cardanoswiss.ch cnode[12367]: Listening on http://127.0.0.1:12798

ok, and sudo systemctl status cnode
what is the uptime? what is the server hardware configuration?
I think the server has not enough RAM

Hi Alex,

here is the output:

● cnode.service - Cardano Node
Loaded: loaded (/etc/systemd/system/cnode.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2021-09-29 12:36:32 UTC; 54min ago
Main PID: 12299 (bash)
Tasks: 20 (limit: 9438)
Memory: 6.8G
CGroup: /system.slice/cnode.service
├─12299 bash /opt/cardano/cnode/scripts/cnode.sh
└─12367 cardano-node +RTS -N4 -RTS run --topology /opt/cardano/cnode/files/topology.json --config /opt/cardano/cnode/files/config.json --database-path /opt/cardano/cnode/d>

Sep 29 12:36:32 producer.cardanoswiss.ch systemd[1]: Started Cardano Node.
Sep 29 12:36:34 producer.cardanoswiss.ch cnode[12367]: Listening on http://127.0.0.1:12798

I had a similar issue with the relays and after OS reinstallation now everything works perfectly.

RAM is 8GB + 3GB swap

can u try to upgrade de RAM? just for test?

Unfortunately, it is not possible. I mean the cloud service I use doesn’t give such an option. I need to request a new service which will be a new server.
Probably I need to reinstall everything from scratch.

Try to increase the swap

1 Like

Already did it to 6GB, still not working :frowning:

ok, the uptime is fine? do you see that the server restart? try to delete the db… and check if it’s starting (then you can copy the DB from another synced node)

but how is the CPU? press top… do you see the CPU ~100%?

or first try to add the IOHK nodes inside the topology file and restart the server

not restarting, but now I see something strange, everything is 0 :thinking:

aaa ok, it must be from DB…delete all files from DB folder and restart the node… .let me know the result

here is how htop looks like

can u show me the topology file?

delete all files and subfolders from DB folder?

0 Sep 29 15:56 clean
196608 Sep 25 22:55 immutable/
4096 Sep 28 04:42 ledger/
0 Feb 14 2021 lock*
9 Feb 14 2021 protocolMagicId*
4096 Sep 25 23:01 volatile/

When is Alonzo PV 6 fork? I thought we just did Alonzo fork and I assume PV 6 is yet another one coming, right?

I don’t know exactly when but I believe in October

this is talking forever - are the IOHK server overloaded?

nvm it finished… just never took 3 hours before lol