topologyUpdater.sh shows error cardano-cli: Network.Socket.connect: <socket: 11>: does not exist (No such file or directory){ "resultcode": "502", "datetime"":, "clientIp": "", "msg": "invalid blockNo []" }

Hi Community,

I have updated my Stakepool to (Core - Mainnet) : 1.29.0 [4c594429] - Alonzo-Upgrade. Furthermore I have lowered from two Relay-Nodes to just one Node and updated the “mainnet-topology.json” accordingly.

Afterwards I have started ./topologyUpdater.sh which shows the error below:

cardano-cli: Network.Socket.connect: <socket: 11>: does not exist (No such file or directory){ “resultcode”: “502”, “datetime”:“2021-09-19 15:32:29”, “clientIp”: “46.101.127.176”, “msg”: “invalid blockNo ” }

Can some one please help?
Furthermore “gLiveView.sh” remains in the “starting” state.

After starting the Blockproducer via “startBlockProducingNode.sh”
it shows error messages after a while:

block-pr:cardano.node.Forge:Error:88] [2021-09-19 15:58:59.00 UTC] fromList [(“val”,Object (fromList [(“kind”,String “TraceNoLedgerView”),(“slot”,Number 4.0500848e7)])),(“credentials”,String “Cardano”)]

block-pr:cardano.node.IpSubscription:Error:149] [2021-09-19 16:00:07.92 UTC] IPs: 0.0.0.0:0 [46.101.127.176:6000] Connection Attempt Exception, destination RelayNodeIP:6000 exception: Network.Socket.connect: <socket: 54>: does not exist (Connection refused)
[block-pr:cardano.node.ErrorPolicy:Notice:96] [2021-09-19 16:00:07.92 UTC] IP RelayNodeIP:6000 ErrorPolicySuspendConsumer (Just (ConnectionExceptionTrace Network.Socket.connect: <socket: 54>: does not exist (Connection refused))) 20s

block-pr:cardano.node.Forge:Error:88] [2021-09-19 16:04:16.00 UTC] fromList [(“val”,Object (fromList [(“kind”,String “TraceNoLedgerView”),(“slot”,Number 4.0501165e7)])),(“credentials”,String “Cardano”)]
[block-pr:cardano.node.LeadershipCheck:Info:88] [2021-09-19 16:04:17.00 UTC] {“kind”:“TraceStartLeadershipCheck”,“chainDensity”:4.7703218e-2,“slot”:40501166,“delegMapSize”:828660,“utxoSize”:3230910,“credentials”:“Cardano”}

Thank you in advance!

With kind regards.

It seems the nodes not started, how is the relay? Still starting? Did u followed coincashew or cntools guide?

Hi Alexd1985,

the relay node exits after quite some time with this error message:

[relay-no:cardano.node.ChainDB:Notice:1116] [2021-09-19 16:08:08.53 UTC] Chain extended, new tip: b4923103534c861b6d793242d86162619d0bc01e84c9a93873a8f134fbf5c253 at slot 39803072
./startRelayNode1.sh: line 9: 1209 Killed /usr/local/bin/cardano-node run --topology ${TOPOLOGY} --database-path ${DB_PATH} --socket-path ${SOCKET_PATH} --host-addr ${HOSTADDR} --port ${PORT} --config ${CONFIG}

I had a look at the “cntools” tutorial from Coincashew.com
Especially on the “Publishing your Relay Node with topologyUpdater.sh” and on
“How to update a Stakepool” in this case.

RAM issues, u will need more than 8 G; what is the hardware configuration for Relay?

You can test it by set to false the TraceMempool inside the configuration file (and restart the node)

Relay-Node is configured like this:
8 GB / 4 vCPUs

sudo systemctl status cardano-node gives the result below:

Cardano-node.service - Cardano node service
Loaded: loaded (/etc/systemd/system/cardano-node.service; enabled; vendor preset: enabled)
Active: failed (Result: timeout) since Sun 2021-09-19 15:49:54 UTC; 1h 0min ago
Process: 715 ExecStart=/bin/bash -c /home/cardano_ssh/cardano-my-node/startRelayNode1.sh (code=killed, signal=KILL)
Main PID: 715 (code=killed, signal=KILL)

Sep 19 15:49:54 relay-node-1 systemd[1]: cardano-node.service: Killing process 800 (cardano-node:w) with signal SIGKILL.
Sep 19 15:49:54 relay-node-1 systemd[1]: cardano-node.service: Killing process 815 (cardano-node:w) with signal SIGKILL.
Sep 19 15:49:54 relay-node-1 systemd[1]: cardano-node.service: Killing process 816 (cardano-node:w) with signal SIGKILL.
Sep 19 15:49:54 relay-node-1 systemd[1]: cardano-node.service: Killing process 818 (n/a) with signal SIGKILL.
Sep 19 15:49:54 relay-node-1 systemd[1]: cardano-node.service: Killing process 819 (cardano-node:w) with signal SIGKILL.
Sep 19 15:49:54 relay-node-1 systemd[1]: cardano-node.service: Killing process 977 (n/a) with signal SIGKILL.
Sep 19 15:49:54 relay-node-1 systemd[1]: cardano-node.service: Killing process 1010 (n/a) with signal SIGKILL.
Sep 19 15:49:54 relay-node-1 systemd[1]: cardano-node.service: Main process exited, code=killed, status=9/KILL
Sep 19 15:49:54 relay-node-1 systemd[1]: cardano-node.service: Failed with result ‘timeout’.
Sep 19 15:49:54 relay-node-1 systemd[1]: Stopped Cardano node service.

Will the Relay Node and the Block-Producer need an RAM Upgrade, or just the Relay-Node?

1 Like

Hi Alexd1985,

thank you for your help, very much appreciated!

The Pool is working again after I have updated the Relay-Node to 16GB RAM.

image

image

Have a nice Sunday!

With kind regards.

1 Like

You are welcome, glade u fixed :beers:

1 Like

Keep it under monitoring, eventually activate 2-3 G swap MEM; I know my Producer is using more than 8G

1 Like

Thank you very much for answering my question.
I guess the activation of 2 - 3 G swap MEN is needed in this case.

Guild LiveView v1.20.10 has just lost connection to the Blockproducer Node.
image

The Relay-Node is still up and running.

1 Like

Uptime 4 minutes so, u will need to upgrade the RAM or activated SWAP

Hi,

I have created a 3 GB swap file by following this process:

Create the swap file:
sudo fallocate -l 3G /swapfile

Permissions so that only root can write to:
sudo chmod 600 /swapfile
sudo mkswap /swapfile

Setting up swapspace version 1, size = 3 GiB (3221221376 bytes)
no label, UUID=80a9e87c-c78d-4a8b-bd5a-540397f89d70

Activate it with:
sudo swapon /swapfile
sudo echo “/swapfile swap swap defaults 0 0” | sudo tee -a /etc/fstab

cat /proc/swaps

Filename Type Size Used Priority
/swapfile file 3145724 0 -2

I will monitor the stability of the Block-Producer, and update the RAM if required.

Thank you.