How to set up a POOL in a few minutes - and register using CNTOOLS

Staking & Delegation Setup a Stake Pool
1159

For step 5 u can use import wallet but I think u need to rebuild the node

type cabal - -version

If u have 3.4.0.0 then u will need 3.2.0.0

ghcup install cabal 3.2.0.0
ghcup set cabal 3.2.0.0
check the version
cabal - -version. (U should see 3.2.0.0)
Now stop the node and rebuild
sudo systemctl stop cnode
cd ~/git
cd cardano-node
$CNODE_HOME/scripts/cabal-build-all.sh -o

1 Like
1160

Thanks but when I try to rebuild the node im getting

cabal: Could not resolve dependencies:
[__0] trying: Win32-network-0.1.0.0 (user goal)
[__1] trying: base-4.12.0.0/installed-4.12.0.0 (dependency of Win32-network)
[__2] next goal: cardano-api (user goal)
[__2] rejecting: cardano-api-1.27.0 (conflict:
base==4.12.0.0/installed-4.12.0.0, cardano-api => base>=4.14 && <4.15)
[__2] fail (backjumping, conflict set: base, cardano-api)
After searching the rest of the dependency tree exhaustively, these were the
goals I've had most trouble fulfilling: cardano-api, base, Win32-network
1161

Try

type cabal - -version

If u have 3.4.0.0 then u will need 3.2.0.0

ghcup install cabal 3.2.0.0
ghcup set cabal 3.2.0.0
check the version
cabal - -version. (U should see 3.2.0.0)
Now stop the node and rebuild
sudo systemctl stop cnode
cd ~/git
cd cardano-node

git fetch --tags --all
git checkout 1.27.0
git pull origin master

echo -e “package cardano-crypto-praos\n flags: -external-libsodium-vrf” > cabal.project.local

$CNODE_HOME/scripts/cabal-build-all.sh -o

1162

thank you but no luck same error messages

1163

Try without pull master command

ghcup install cabal 3.2.0.0
ghcup set cabal 3.2.0.0
check the version
cabal - -version. (U should see 3.2.0.0)
Now stop the node and rebuild
sudo systemctl stop cnode
cd ~/git
cd cardano-node

git fetch --tags --all
git checkout 1.27.0

echo -e “package cardano-crypto-praos\n flags: -external-libsodium-vrf” > cabal.project.local

$CNODE_HOME/scripts/cabal-build-all.sh -o

1164

No luck, here’s the full printout if that helps

Overwriting cabal.project.local to include cardano-addresses and bech32 (previous file, if any, will be saved as cabal.project.local.swp)..
From https://github.com/input-output-hk/cardano-ledger-specs
   dc5a1c217..96e476ee1  jc/address-audits-2021-06 -> origin/jc/address-audits-2021-06
 + 6f8046809...890e70955 lehins/fix-unit-interval-ratio-word64 -> origin/lehins/fix-unit-interval-ratio-word64  (forced update)
   6474f68b2..b590b8cef  master     -> origin/master
   ad2ed48a0..dcf537b27  ts-feeTooSmallAftergenEraTweakBlock -> origin/ts-feeTooSmallAftergenEraTweakBlock
From https://github.com/input-output-hk/ouroboros-network
   be47fbb3d..11f61bffc  bors/staging -> origin/bors/staging
   be47fbb3d..11f61bffc  master       -> origin/master
cabal: Could not resolve dependencies:
[__0] trying: Win32-network-0.1.0.0 (user goal)
[__1] trying: base-4.12.0.0/installed-4.12.0.0 (dependency of Win32-network)
[__2] next goal: cardano-api (user goal)
[__2] rejecting: cardano-api-1.27.0 (conflict:
base==4.12.0.0/installed-4.12.0.0, cardano-api => base>=4.14 && <4.15)
[__2] fail (backjumping, conflict set: base, cardano-api)
After searching the rest of the dependency tree exhaustively, these were the
goals I've had most trouble fulfilling: cardano-api, base, Win32-network

Running cabal update to ensure you're on latest dependencies..
HEAD is now at 94153b6 Fixed title of haddock page
HEAD is now at f730793 Merge pull request #69 from newhoggy/add-ghc-8.6.5-and-8.10.2-to-ci
HEAD is now at e8f19bcc9 Merge #2135
HEAD is now at 8bcd3c9 Downgrade cabal file version to 2.4 because 3.0 is incompatible with stack
HEAD is now at 9b279c754 Merge #3036
Downloading the latest package list from hackage.haskell.org
To revert to previous state run:
    cabal v2-update 'hackage.haskell.org,2021-06-17T10:49:09Z'
Building..
Warning: Requested index-state2021-03-15T00:00:00Z is newer than
'hackage.haskell.org'! Falling back to older state (2021-03-14T23:47:09Z).
Resolving dependencies...
cabal: Could not resolve dependencies:
[__0] trying: Win32-network-0.1.0.0 (user goal)
[__1] trying: base-4.12.0.0/installed-4.12.0.0 (dependency of Win32-network)
[__2] next goal: cardano-api (user goal)
[__2] rejecting: cardano-api-1.27.0 (conflict:
base==4.12.0.0/installed-4.12.0.0, cardano-api => base>=4.14 && <4.15)
[__2] fail (backjumping, conflict set: base, cardano-api)
After searching the rest of the dependency tree exhaustively, these were the
goals I've had most trouble fulfilling: cardano-api, base, Win32-network
1165

Did u used my guide? Also do u have ubuntu OS?

1166

@Alexd1985 or anybody who are knowledgable, I wonder if you know what’s going on that gLiveview on BP show status starting frequently, after a while it will show fine. I check everything is OK.
image

After several minutes the OK condition is shown:
image

Then I leave it for the day, the next day I come back it will show ‘starting’ status again. Not sure when and why. I tried to reinstall cabal update and build the node again, but that didn’t fix it.
This happens to the new server for BP as I want to upgrade and migrate it.
Thanks in advance.

1167

I just finished posting the OK status, now it’s ‘starting’ again. So annoying.

1168

i am having a similar issue

1169

What is the hw configuration of the node?

1170

Intel(R) Xeon(R) Gold 5120 CPU @ 2.20GHz
CPU: 4 vCore
RAM: 8 GB
SSD: 160 GB
Data transfer rate up to: 400 Mbps

On ubuntu 20.04

1171

And if u type journalctl -e -f -u cnode do u see any kill command?

1172

Memory might not be enough for your BP. I tested my relays with 4GB and they were restarting like 3-4 times a day. I added more memory, and they turned stable

1 Like
1173

Yes there are, and the latest:

un 19 15:40:11 localhost cnode[1322746]: /opt/cardano/cnode/scripts/cnode.sh: line 57: 1323172 Killed cardano-node “${CPU_RUNTIME[@]}” run --topology “${TOPOLOGY}” --config “${CONFIG}” --database-path “${DB_DIR}” --socket-path “${CARDANO_NODE_SOCKET_PATH}” --shelley-kes-key “${POOL_DIR}/${POOL_HOTKEY_SK_FILENAME}” --shelley-vrf-key “${POOL_DIR}/${POOL_VRF_SK_FILENAME}” --shelley-operational-certificate “${POOL_DIR}/${POOL_OPCERT_FILENAME}” --port ${CNODE_PORT} “${host_addr[@]}”
Jun 19 15:40:17 localhost cnode[1338975]: WARN: A prior running Cardano node was not cleanly shutdown, socket file still exists. Cleaning up.
Jun 19 15:40:19 localhost cnode[1339449]: Listening on http://127.0.0.1:12798

I think @ALoop is correct, the MEM is not enough. I answer ‘yes’ to all questions for BP’s deploy-as-systemd.sh.
Thanks @Alexd1985 & @ALoop !

1174

run again and press N for topology updater, u don’t need it on BP

and edit again the topology file (add only the relays) + restart the node;

And upgrade the servers

if u will want a cheap VPS solution with ~17€ u will have a good setup for alonzo era:

image
image

1 Like
1175

Will do, the VPS pricing is attractive, too!
Thanks Alex!

2 Likes
1176

I see on your last screenshot that the ‘BLOCKS’ section of gLiveView under “Ideal” and “Luck” states nothing.
Has it always been like this, or did this just happen to you? I have the same “issue”.

1177

It will be updated when u will have blocks assigned

1178

My BP node runs no issues in 8gb ram with 2gb swap file on ubuntu 18. However, When I run cntools detail pool query it will crash and not cleanly shutdown

I saw your error “not cleanly shut down” this will cause node to try to restart over and over

my workaround below

ps -aux
(find the PID for cardano-node)
kill -9 PID
sudo systemctl stop cnode
sudo systemctl start cnode
sudo systemctl status cnode
(should be no errors, just listening)

1 Like