Hi, this is my first time posting here. I’ve been looking for a solution to my error on this forum with no luck so I am hoping someone can help me directly.
I followed CoinCashews guide to setup 3 Cardano nodes and am now trying to register my stake address. I am not able to see my TxHash TxIx or amount of ada in my payment address when using
cardano-cli query utxo --address $(cat payment.addr) --mary-era --mainnet
I then used journalctl --unit=cardano-node --follow to see if the blockchain has synced successfully (which it has prior to starting the node as a blockproducing node) and noticed this error:
[relay1-V:cardano.node.DnsSubscription:Warning:95] [2021-03-27 07:46:14.55 UTC] Domain: “<169.239.9.26>” Failed to start all required subscriptions
on my relay node
and this error
[relay1-V:cardano.node.DnsSubscription:Warning:95] [2021-03-27 07:46:14.55 UTC] Domain: “<169.239.9.27>” Failed to start all required subscriptions
on my BP node.
Any help would be appreciated. Please ask for the required files to resolve the error as I am unsure what to include.
What I’ve tried: Failed to start all required subscriptions error - #3 by mdsullivan
using -znv <other_nodeIP> <other_node_port> to see if the nodes connect which they do
successfully
and sudo netstat -lnaopt resulting in :
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name Timer
tcp 0 0 127.0.0.53:53 0.0.0.0:* LISTEN 700/systemd-resolve off (0.00/0/0)
tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 648986/cupsd off (0.00/0/0)
tcp 0 0 127.0.0.1:12798 0.0.0.0:* LISTEN 1294499/cardano-nod off (0.00/0/0)
tcp 0 0 0.0.0.0:6000 0.0.0.0:* LISTEN 1294499/cardano-nod off (0.00/0/0)
tcp 0 0 127.0.0.1:12788 0.0.0.0:* LISTEN 1294499/cardano-nod off (0.00/0/0)
tcp 0 0 169.239.9.26:34651 18.158.188.21:3001 ESTABLISHED 1294499/cardano-nod off (0.00/0/0)
tcp 0 0 169.239.9.26:43631 18.132.127.241:3001 ESTABLISHED 1294499/cardano-nod off (0.00/0/0)
tcp6 0 0 ::1:3350 :::* LISTEN 878/xrdp-sesman off (0.00/0/0)
tcp6 0 0 ::1:631 :::* LISTEN 648986/cupsd off (0.00/0/0)
tcp6 0 0 :::3389 :::* LISTEN 898/xrdp off (0.00/0/0)
tcp6 0 0 169.239.9.26:3389 102.182.98.158:53234 ESTABLISHED 1294478/xrdp keepalive (5250.00/0/0)
1 Like
sudo systemctl status cardano-node
● cardano-node.service - Cardano node service
Loaded: loaded (/etc/systemd/system/cardano-node.service; enabled; vendor preset: enabled)
Active: active (running) since Sat 2021-03-27 09:21:22 SAST; 44min ago
Main PID: 1294498 (bash)
Tasks: 17 (limit: 9417)
Memory: 4.3G
CGroup: /system.slice/cardano-node.service
├─1294498 /bin/bash -c /home/chris/cardano-my-node/startBlockProducingNode.sh
└─1294499 cardano-node run --topology /home/chris/cardano-my-node/mainnet-topology.json --data>
Hi!
Please provide content of both topology files to see what ports you add in it.
Hey, @laplasz thanks for the swift reply!
Relay node:
{
"Producers": [
{
"addr": "169.239.9.26",
"port": 6000,
"valency": 1
},
{
"addr": "relays-new.cardano-mainnet.iohk.io",
"port": 3001,
"valency": 2
}
]
}
Producer node:
{
"Producers": [
{
"addr": "169.239.9.27",
"port": 6000,
"valency": 1
},
]
}
Thanks
so netstat clearly shows that IP of the relay node is 169.239.9.26 since this IP is used which connect to IOHK server:
tcp 0 0 169.239.9.26:34651 18.158.188.21:3001 ESTABLISHED 1294499/cardano-nod off (0.00/0/0)
tcp 0 0 169.239.9.26:43631 18.132.127.241:3001 ESTABLISHED 1294499/cardano-nod off (0.00/0/0)
that means the IPs in the topology files should be replaced by eachother.
so relay topology should contain BPs IP: 169.239.9.27, and BP topology should contain IP of relay: 169.239.9.26
Hope this helps!
(probably when you tried to netcat it just connected to itself, and not to the other)
so I tried swapping the IP and the error still persists, I double-checked the IP for both the producer and the relay.
BP is definitely set to 169.239.9.26 and relay to 169.239.9.27…
I’m guessing I somehow made a mistake when configuring the BP?
[quote=“Chris.AXN, post:1, topic:55233”]
netstat -lnaopt
[/quote] When run on relay node
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name Timer
tcp 0 0 127.0.0.1:12788 0.0.0.0:* LISTEN 3869444/cardano-nod off (0.00/0/0)
tcp 0 0 127.0.0.53:53 0.0.0.0:* LISTEN - off (0.00/0/0)
tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN - off (0.00/0/0)
tcp 0 0 127.0.0.1:12798 0.0.0.0:* LISTEN 3869444/cardano-nod off (0.00/0/0)
tcp 0 0 0.0.0.0:6000 0.0.0.0:* LISTEN 3869444/cardano-nod off (0.00/0/0)
tcp 0 0 169.239.9.27:44667 3.125.149.71:3001 ESTABLISHED 3869444/cardano-nod off (0.00/0/0)
tcp 0 0 169.239.9.27:38373 18.132.159.229:3001 ESTABLISHED 3869444/cardano-nod off (0.00/0/0)
tcp6 0 0 ::1:3350 :::* LISTEN - off (0.00/0/0)
tcp6 0 0 ::1:631 :::* LISTEN - off (0.00/0/0)
tcp6 0 0 :::3389 :::* LISTEN - off (0.00/0/0)
tcp6 0 0 169.239.9.27:3389 102.182.98.158:54015 ESTABLISHED - keepalive (5120.15/0/0)
when run on BP:
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name Timer
tcp 0 0 127.0.0.53:53 0.0.0.0:* LISTEN - off (0.00/0/0)
tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN - off (0.00/0/0)
tcp 0 0 127.0.0.1:12798 0.0.0.0:* LISTEN 1294499/cardano-nod off (0.00/0/0)
tcp 0 0 0.0.0.0:6000 0.0.0.0:* LISTEN 1294499/cardano-nod off (0.00/0/0)
tcp 0 0 127.0.0.1:12788 0.0.0.0:* LISTEN 1294499/cardano-nod off (0.00/0/0)
tcp 0 0 169.239.9.26:38790 34.122.121.32:80 TIME_WAIT - timewait (31.83/0/0)
tcp 0 0 169.239.9.26:34651 18.158.188.21:3001 ESTABLISHED 1294499/cardano-nod off (0.00/0/0)
tcp 0 0 169.239.9.26:33089 18.157.103.148:3001 ESTABLISHED 1294499/cardano-nod off (0.00/0/0)
tcp6 0 0 ::1:3350 :::* LISTEN - off (0.00/0/0)
tcp6 0 0 ::1:631 :::* LISTEN - off (0.00/0/0)
tcp6 0 0 :::3389 :::* LISTEN - off (0.00/0/0)
tcp6 0 0 169.239.9.26:3389 41.113.98.132:62007 ESTABLISHED - keepalive (7173.63/0/0)
tcp6 0 0 ::1:3350 ::1:51512 TIME_WAIT - timewait (35.01/0/0)
so maybe the use of topology files are mixed up - so block producer started with relay node topology…
what is the status of the service to see which topology was used when starting the node
can you please edit your previous post with adding the netstat info about your producer node as well?
1 Like
Im assuming I should post the output of this command on the relay?
So as you can see that both nodes connects to IOHK server:
relay:
tcp 0 0 169.239.9.27:44667 3.125.149.71:3001 ESTABLISHED 3869444/cardano-nod off (0.00/0/0)
tcp 0 0 169.239.9.27:38373 18.132.159.229:3001 ESTABLISHED 3869444/cardano-nod off (0.00/0/0)
bp:
tcp 0 0 169.239.9.26:34651 18.158.188.21:3001 ESTABLISHED 1294499/cardano-nod off (0.00/0/0)
tcp 0 0 169.239.9.26:33089 18.157.103.148:3001 ESTABLISHED 1294499/cardano-nod off (0.00/0/0)
which is suspicious… that means BP using the relays topology file…
give status of both
1 Like
Relay status:
● cardano-node.service - Cardano node service
Loaded: loaded (/etc/systemd/system/cardano-node.service; enabled; vendor preset: enabled)
Active: active (running) since Sat 2021-03-27 09:21:01 SAST; 3h 1min ago
Main PID: 3869441 (bash)
Tasks: 13 (limit: 4636)
Memory: 2.6G
CGroup: /system.slice/cardano-node.service
├─3869441 /bin/bash -c /home/relay1/cardano-my-node/startRelayNode1.sh
└─3869444 /usr/local/bin/cardano-node run --topology /home/relay1/cardano-my-node/mainnet-t>
Mar 27 12:21:45 relay1-Virtual-Machine bash[3869444]: [relay1-V:cardano.node.DnsSubscription:Warning:95]>
Mar 27 12:21:46 relay1-Virtual-Machine bash[3869444]: [relay1-V:cardano.node.BlockFetchDecision:Info:83]>
Mar 27 12:21:46 relay1-Virtual-Machine bash[3869444]: [relay1-V:cardano.node.BlockFetchDecision:Info:83]>
Mar 27 12:21:46 relay1-Virtual-Machine bash[3869444]: [relay1-V:cardano.node.ChainDB:Notice:73] [2021-03>
Mar 27 12:21:55 relay1-Virtual-Machine bash[3869444]: [relay1-V:cardano.node.DnsSubscription:Warning:95]>
Mar 27 12:22:05 relay1-Virtual-Machine bash[3869444]: [relay1-V:cardano.node.DnsSubscription:Warning:95]>
Mar 27 12:22:15 relay1-Virtual-Machine bash[3869444]: [relay1-V:cardano.node.DnsSubscription:Warning:95]>
Mar 27 12:22:25 relay1-Virtual-Machine bash[3869444]: [relay1-V:cardano.node.DnsSubscription:Warning:95]>
Mar 27 12:22:35 relay1-Virtual-Machine bash[3869444]: [relay1-V:cardano.node.DnsSubscription:Warning:95]>
Mar 27 12:22:45 relay1-Virtual-Machine bash[3869444]: [relay1-V:cardano.node.DnsSubscription:Warning:95]
BP status:
● cardano-node.service - Cardano node service
Loaded: loaded (/etc/systemd/system/cardano-node.service; enabled; vendor preset: enabled)
Active: active (running) since Sat 2021-03-27 09:21:22 SAST; 3h 2min ago
Main PID: 1294498 (bash)
Tasks: 17 (limit: 9417)
Memory: 4.7G
CGroup: /system.slice/cardano-node.service
├─1294498 /bin/bash -c /home/chris/cardano-my-node/startBlockProducingNode.sh
└─1294499 cardano-node run --topology /home/chris/cardano-my-node/mainnet-topology.json --database-path /hom>
Mar 27 12:24:16 chris-PowerEdge-R320 bash[1294499]: [chris-Po:cardano.node.ForgeTime:Info:74] [2021-03-27 10:24:16.00 UTC>
Mar 27 12:24:16 chris-PowerEdge-R320 bash[1294499]: [chris-Po:cardano.node.Forge:Info:74] [2021-03-27 10:24:16.00 UTC] fr>
Mar 27 12:24:16 chris-PowerEdge-R320 bash[1294499]: [chris-Po:cardano.node.ForgeTime:Info:74] [2021-03-27 10:24:16.00 UTC>
Mar 27 12:24:17 chris-PowerEdge-R320 bash[1294499]: [chris-Po:cardano.node.LeadershipCheck:Info:74] [2021-03-27 10:24:17.>
Mar 27 12:24:17 chris-PowerEdge-R320 bash[1294499]: [chris-Po:cardano.node.ForgeTime:Info:74] [2021-03-27 10:24:17.00 UTC>
Mar 27 12:24:17 chris-PowerEdge-R320 bash[1294499]: [chris-Po:cardano.node.ForgeTime:Info:74] [2021-03-27 10:24:17.00 UTC>
Mar 27 12:24:17 chris-PowerEdge-R320 bash[1294499]: [chris-Po:cardano.node.ForgeTime:Info:74] [2021-03-27 10:24:17.00 UTC>
Mar 27 12:24:17 chris-PowerEdge-R320 bash[1294499]: [chris-Po:cardano.node.ForgeTime:Info:74] [2021-03-27 10:24:17.00 UTC>
Mar 27 12:24:17 chris-PowerEdge-R320 bash[1294499]: [chris-Po:cardano.node.Forge:Info:74] [2021-03-27 10:24:17.00 UTC] fr>
Mar 27 12:24:17 chris-PowerEdge-R320 bash[1294499]: [chris-Po:cardano.node.ForgeTime:Info:74] [2021-03-27 10:24:17.00 UTC
relay: /home/relay1/cardano-my-node/mainnet-topology.json
bp: /home/chris/cardano-my-node/mainnet-topology.json
so these nodes are on the same machine with different virtual interfaces?
They are running on 2 different servers, I have another relay node setup on the same server as relay 1 but I’ve haven’t connected it to the bp as of yet since I’m trying to get relay 1 to work. The bp is on a dedicated Linux Ubuntu server
1 Like
can you just start bp, so kill the relay…
and then see what netstat gives back for bp - there should not be any ESTABLISHED connection
also when you start the node - you can find the remote addresses where the node will attempt to connect at the beginning of the node logs… can you please share the logs content?
I killed both relays this is the result on the BP
Its clearly still connected…
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name Timer
tcp 0 0 127.0.0.53:53 0.0.0.0:* LISTEN - off (0.00/0/0)
tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN - off (0.00/0/0)
tcp 0 0 127.0.0.1:12798 0.0.0.0:* LISTEN 1294499/cardano-nod off (0.00/0/0)
tcp 0 0 0.0.0.0:6000 0.0.0.0:* LISTEN 1294499/cardano-nod off (0.00/0/0)
tcp 0 0 127.0.0.1:12788 0.0.0.0:* LISTEN 1294499/cardano-nod off (0.00/0/0)
tcp 0 12 169.239.9.26:46449 18.159.27.23:3001 ESTABLISHED 1294499/cardano-nod on (0.38/0/0)
tcp 0 0 169.239.9.26:36143 35.179.8.173:3001 ESTABLISHED 1294499/cardano-nod off (0.00/0/0)
tcp 1 0 169.239.9.26:38440 151.101.194.49:443 CLOSE_WAIT 18486/snap-store off (0.00/0/0)
tcp6 0 0 ::1:3350 :::* LISTEN - off (0.00/0/0)
tcp6 0 0 ::1:631 :::* LISTEN - off (0.00/0/0)
tcp6 0 0 :::3389 :::* LISTEN - off (0.00/0/0)
tcp6 0 67 169.239.9.26:3389 102.182.98.158:54936 ESTABLISHED - on (0.23/0/0)
I dont see any connect info in the logs when using journalctl --unit=cardano-node --follow
the node generates logs which can be found under logs/ in the node folder… do you have such?
also list all the processes which is running:
ps -ef | grep cardano
I’m not sure, may be 169.239.9.27 is not public ip. it is under your proxy.