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

Hey @Alexd1985 I’m having problems getting my gLiveView working, I’m getting this error

" Guild LiveView version check…

Looks like cardano-node is running with socket-path as /opt/cardano/cnode/sockets/node0.socket, but the actual socket file does not exist.

This could occur if the node hasnt completed startup or if a second instance of node startup was attempted!

If this does not resolve automatically in a few minutes, you might want to restart your node and try again.

ERROR: CNTools failed to load common env file

Please verify set values in ‘User Variables’ section in env file or log an issue on GitHub"

My node was working well and even completed 2 blocks before going offline and just falling behind. I tried a couple of things that you recommended to other people but it’s still not working. what should I do?

sudo systemctl status cnode
Or

sudo systemctl status cardano-node

Thanks alex, I moved on because the rebuild didnt help thos missing files in my cabal folder. I am getting ready to bring a second BP server online in the coming weeks so hopefully a fresh build from scratch works a bit smoother. Is there a way to set up wallet recovery without using cntools?

Should be, the script is the same just that cntools has a friendly gui

Hi Alex,

I managed to link my BP and relay. In BP however it is still showing relay. Is this something I need to worry at the moment prior moving to step 5 for creating wallet ?

image

The node will start as coremainet after u will create the certificates later

1 Like

Thanks Alex for prompt reply.

1 Like

Alex,

This helped tremendously. Many thanks.

I have my Producer and relay working and I’m able to verify they are communicating now.
I’m at 97.3% sync. Yay.

B.Rgds,
Scott H

1 Like

super helpful. I was just wondering about this. thanks.

1 Like

Hi man, I hope u are fine… I tested and I found the issue… is the cabal version now u have 3.4.0.0 and u will need 3.2.0.0

cabal - -version

U will need to do:

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

cd ~/git
cd cardano-node

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

Cheers,

wow! thanks so much for looking into that for me. I’m not sure how i ended up with a newer version of cabal but i will give you an update after it is rebuilt! thanks!

1 Like

I tested with another PO which had the same issues and last night I figured out that the cabal version is not ok… with 3.2.0.0 the binari files are added (cardano-address and bech32)

1 Like

hi alex when i setting up the node to start as systemd and run ./deploy-as-systemd.sh in bp and relay ask me to set the topologyupdater process as systemd i select no for produser and yes for relay and other than that ask for
Deploy Blocklog as systemd services
Deploy PoolTool SendSlots as systemd services
Deploy Log Monitor as systemd services?
Deploy PoolTool SendTip as systemd services
please tell me which one should i answer yes or no for bp and relay
thanks

you can start all, but I started only SendTip because I want to see in pooltool if my Producer is synced (green) or not; if u are not using this option then you can choose N for all, because u can run them manually when u will need it; and ofcourse on future u can activate as a systemd if u needed… so it’s not so important this step right now
you can run again anytime in future the ./deploy-as-systemd.sh script

more details here:

1 Like

thank you for answer reason was i see 5 peers IN relay i thought its because of this options

nope, the reason is the topology updater which announce your IP to the public network

so its healthy ?

yes, on Relay u need to have public IN/OUT peers
only on Producer u need to have only your Relay as IN/OUT peer

I appreciate your help so much

1 Like

Hello,

I am having issues about using cncli.sh

  1. I installed cncli using prereqs.sh -c

  2. I deployed it as systemd Deploy Blocklog as systemd services? = Y, Deploy Log Monitor as systemd services? = Y only.

  3. Thereafter i used the init command: $CNODE_HOME/scripts/cncli.sh init
    I got the following message:
    Looking for blocks made by pool…
    No blocks found :frowning:

  4. Thereafter i tried to run ./cncli.sh leaderlog. I got the following error message:

Error message: Remote API Error: error sending request for url (https://api.crypto2099.io/v1/sigma/MY-POOL-ID-WAS-HERE-REMOVED/265): operation timed out

I am really concerned about this api.crypto2099.io - What is this? Why is this needed? Does this expose my BP IP now?