I’m not a great fan of the topology updater. I would suggest to simply use the IOHK servers per the default. You will be get a good spread of peers which will dynamically optimise over time.
1 Like
On BP you don’t have to use topology updater!
On Relay you must set your BP ip and port.
Relays should not be connected together ( waist of bandwith)
1 Like
Thanks - sorry I am almost there but just want to check. In one of my relays which is now configured using the Guild Operators guide I have set my BP node in the CUSTOM_PEERS section of the TopologyUpdate.sh file. I can now see my BP node in the list of peers when I run gLiveView in the relay node. Have I done this correctly? Thanks again.
Yes, also on BP you should see your relays and only your relays… info about keys and blocks…
If these are visible and tx incrementinc… you are in business
Ah - something is wrong then as I can see a lot of peers on my BP node - does that mean I edit my topologyUpdater.sh file on my BP and remove the
CNODE_TOPOLOGY="${CNODE_HOME}/files/topology.json"
and replace if with the CUSTOM PEERS line which has both my relays?
You must not run the topologyupdater on BP. Edit your topology file on BP with only your relays IP and will be fine
Ok - got that - so that is the topology.json file in the /opt/cardano/cnode/files path
Yes … on cnode/files/ and delete topologyupdater script from BP. Everytime topologyuodater will run … your topology file will be overwritten
1 Like
Hi there again. Just as I thought everything was going to be fine it has gone weird. I removed the topologyUpdater.sh file from the BP node and update my topology.json file to reflect only my relay nodes but now when I restart my BP node it is showing as a relay - mainnet in gLiveView and also the status just freezes on …starting.
However if I run the system status it looks like it is running ok
● cnode.service - Cardano Node
Loaded: loaded (/etc/systemd/system/cnode.service; enabled; vendor preset:>
Active: active (running) since Sun 2020-12-13 14:11:02 GMT; 5s ago
Main PID: 3447 (cnode.sh)
Tasks: 9 (limit: 9487)
Memory: 93.1M
CGroup: /system.slice/cnode.service
├─3447 /bin/bash /opt/cardano/cnode/scripts/cnode.sh
└─3533 cardano-node run --topology /opt/cardano/cnode/files/topolo>
Dec 13 14:11:02 GNP1-BP systemd[1]: Started Cardano Node.
Dec 13 14:11:07 GNP1-BP cnode[3533]: Listening on http://127.0.0.1:1279
I am kind of confused as to what to do now
Try:
sudo systemctl stop cnode.service
an start it manually with cnode.sh
Before start check env file, cnode file,
Hi there - I just tried what you say and I get this error
$ ./cnode.sh
Listening on http://127.0.0.1:12798
Shutting down…
cardano-node: FatalError {fatalErrorMessage = “Cardano.Node.Run.handleSimpleNode.readTopologyFile: Is your topology file formatted correctly? The port and valency fields should be numerical. Error in $: Failed reading: not a valid json value at ‘cat>NODE_HOME{NODE_CONFIG}-topology.json<<EOF’”}
Here is my topology.json file
cat > NODE_HOME/{NODE_CONFIG}-topology.json << EOF
{
“Producers”: [
{
“addr”: “192.168.0.77”,
“port”: 6001,
“valency”: 1
},
{
“addr”: “138.128.242.105”,
“port”: 6000,
“valency”: 1
}
]
}
EOF
The port and valancy values are numerical so I don’t know what is wrong?
Should look like this:
{
“Producers”: [
{
“addr”: “192.168.0.77”,
“port”: 6001,
“valency”: 1
},
{
“addr”: “138.128.242.105”,
“port”: 6000,
“valency”: 1
}
]
}
nano topology.json file delete all and paste this… be carefull at “
Do you have another topology file like mainnet-topology.json?
And there is a / missmatch in these 2 lines after NODE_HOME… are u sure the path configured is correct?
$: Failed reading: not a valid json value at ‘cat>NODE_HOME{NODE_CONFIG}-topology.json<<EOF’”}
Here is my topology.json file
cat > NODE_HOME/{NODE_CONFIG}-topology.json
Thanks - OK - I pasted the above like you said and I typed over all the " marks with the one on my keyboard and it appears to have started OK now. I can see that there are only 2 peers which are my relays on the OUT box but there are still 20 peers on the IN box - I take it that this is OK then. It is showing Core - Mainnet and it has the key current/remaining showing 125/25 with the key expiration date on the 18 Jan 2021. I take it that now everything appears to be configured OK?
Many thanks once again and hopefully I have it right now??
Yes, you are fine now… you should stop topologyupdater script if you have for BP (if you had it after 3 hours you should see only 2 to IN peers).
Check if your BP IP is present here (it shouldn’t be)
https://explorer.mainnet.cardano.org/relays/topology.json
If is here wait few hours and will disapear if you are not announcing anymore BP IP via topologyupdater.
I believe you checked the topology files and only the relays are configured…
I have renamed the topologyupdater script before starting the node so that should not do anything now and I can confirm my BP node is not on the explorer - thanks
Yeah but it was… wait and you will see they will leave… anyway … be safe and set your fw to accept incoming connections only from your relays on CNODE PORT
If you do this… they will be disconnected imediately
Thanks - I have only allowed incoming connections from my internet facing firewall (router) on ports 6000 for the BP and on port 6001 for my first relay. I have allowed access from the ubuntu end through sudo ufw allow 6000/tcp on the BP and sudo ufw allow 6001/tcp on the first relay. Is that sufficient?
Type netstat -n | grep ESTAB and you will see all connections established on BP with IP and port info
I seted the ufw for accepting only the relays like that
sudo ufw allow proto tcp from x.x.x.x to CNODE_port
so it’s specific per IP… your is general… accept tcp from anybody on port 6000
I get this on the BP
tcp 0 0 192.168.0.80:6000 86.133.14.21:45863 ESTABLISHED
tcp 0 12 192.168.0.80:6000 111.220.83.171:39743 ESTABLISHED
tcp 0 0 192.168.0.80:6000 76.255.14.154:41045 ESTABLISHED
tcp 0 0 192.168.0.80:42283 192.168.0.77:6001 ESTABLISHED
tcp 0 0 192.168.0.80:6000 161.35.91.11:42475 ESTABLISHED
tcp 0 0 192.168.0.80:6000 195.201.112.148:33269 ESTABLISHED
tcp 0 0 192.168.0.80:6000 164.90.227.46:37629 ESTABLISHED
tcp 0 0 192.168.0.80:6000 86.0.242.62:37977 ESTABLISHED
tcp 0 0 192.168.0.80:6000 138.128.242.105:45653 ESTABLISHED
tcp 0 0 192.168.0.80:6000 167.86.72.182:38403 ESTABLISHED
tcp 0 0 192.168.0.80:6000 167.86.72.182:38039 ESTABLISHED
tcp 0 0 192.168.0.80:6000 35.203.77.113:36981 ESTABLISHED
tcp 0 0 192.168.0.80:6000 161.35.91.11:41939 ESTABLISHED
tcp 0 0 192.168.0.80:6000 34.66.171.204:40189 ESTABLISHED
tcp 0 0 192.168.0.80:6000 86.127.193.249:39521 ESTABLISHED
tcp 0 0 192.168.0.80:6000 80.241.209.138:38021 ESTABLISHED
tcp 0 0 192.168.0.80:6000 18.130.53.86:33735 ESTABLISHED
tcp 0 0 192.168.0.80:6000 31.7.207.27:42991 ESTABLISHED
tcp 0 100 192.168.0.80:46829 138.128.242.105:6000 ESTABLISHED
tcp 0 0 192.168.0.80:6000 18.133.126.104:43839 ESTABLISHED
tcp 0 0 192.168.0.80:6000 35.177.103.2:46481 ESTABLISHED
tcp 0 0 192.168.0.80:6000 95.217.179.67:35319 ESTABLISHED
udp 0 0 192.168.0.80:68 192.168.0.1:67 ESTABLISHED
OK so I need to set it just for my relays